Microsoft has confirmed it is investigating a significant bug in the classic Outlook for Windows desktop client that causes the application to fail upon launch.<\/p>\n
The issue, which appears to be linked to Microsoft Exchange logon<\/a> attempts, prevents users from accessing their mailboxes and displays a critical error message, disrupting daily workflows for affected individuals and organizations.<\/p>\n The problem manifests when a user attempts to open the classic version of Outlook for Windows. Instead of loading the mailbox, the application presents an error message stating, \u201cCannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed.\u201d<\/p>\n While this generic error can stem from various causes, Microsoft has noted that recent support cases point to a specific issue with user mailboxes attempting to connect to the service.<\/p>\n For IT administrators and technical teams looking to confirm if their users are impacted by this specific bug, Microsoft has provided a clear diagnostic method. By capturing a Fiddler trace while reproducing the error, administrators can search for a specific exception.<\/p>\n The presence of the following error in the trace log confirms the issue: This exception indicates that the connection is failing because the user\u2019s client is exceeding the authentication<\/a> concurrency limit set by the server, effectively being \u201cbacked off\u201d or throttled by Microsoft Exchange Online.<\/p>\n This prevents the Outlook client from successfully logging in and opening the user\u2019s mailbox folders.<\/p>\n As of September 26, 2025, Microsoft\u2019s official status for the issue is \u201cINVESTIGATING.\u201d There is currently no direct fix that users or administrators can apply themselves.<\/p>\n To resolve the problem, organizations must open a support case<\/a> through the Microsoft 365 Admin portal. The Exchange Online support team will then need to implement a change on the backend to mitigate the authentication issue for the affected mailboxes.<\/p>\n In the meantime, Microsoft has provided immediate workarounds to ensure users can continue to access their email. Individuals affected by this issue are advised to use Outlook Web Access (OWA), the browser-based version of Outlook, or switch to the new Outlook for Windows client.<\/p>\n These clients are not affected by the bug and provide a reliable alternative while a permanent solution for the classic desktop application is being developed. Organizations are encouraged to communicate these workarounds to their users to minimize disruption.<\/p>\n Follow us on Google News<\/a>, LinkedIn<\/a>, and X<\/a> for daily cybersecurity updates. Contact us<\/a> to feature your stories.<\/strong><\/p>\n The post Microsoft Outlook for Windows Bug Leads to Crash While Opening Email<\/a> appeared first on Cyber Security News<\/a>.<\/p>\n<\/div>\n![\"Microsoft](\"https:\/\/i0.wp.com\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEiKyFXerVFR_pcsuPvSCMuyHrpVKZj9UX2pIBe-c_OIhq3e9uebHpVhbq7KrOj_qNvjczDzYOBs01uKkyMXraQo67rEiMxoXYJkiglg5mUYGyXMWGaQMXVwKzM-7vMxWUH6nM2KwGe7SJUu4xrPJ9ZnRiilmi3TTjG6UP2Fc1YH2Ckmhv6wQuFtzge1Hk7u\/w640-h246\/Microsoft%2520has%2520confirmed%2520it%2520is%2520investigating%2520a%2520significant%2520bug%2520in%2520the%2520classic%2520Outlook%2520for%2520Windows%2520desktop%2520client%2520that%2520causes%2520the%2520application%2520to%2520fail%2520upon%2520launch..webp?ssl=1\")
<\/figure>\n<\/div>\nTechnical Details of the Outlook Bug<\/strong><\/h2>\n
Microsoft.Exchange.RpcClientAccess.ServerTooBusyException: Client is being backed off ---> Microsoft.Exchange.RpcClientAccess.ClientBackoffException: ErrorCode: ClientBackoff, LID: 49586 - Authentication concurrency limit is reached.<\/code><\/p>\n