Microsoft New Bug Disrupts Windows Outlook Without Fix

Microsoft New Bug Disrupts Windows Outlook Without Fix

Microsoft Phases Out Outlook Lite and Faces Classic Outlook Issues

In a significant shift, Microsoft recently announced the discontinuation of Outlook Lite, the streamlined version of its popular email application. This decision aligns with the company’s broader strategy to direct users towards adopting the New Outlook for Windows, recommending alternatives to those affected by the change.

Transitioning from Classic Outlook

Microsoft is actively phasing out Classic Outlook in its quest to promote the New Outlook. The company aims to simplify the transition process by ensuring that users’ existing Classic Outlook accounts and settings are automatically configured in the New Outlook, thereby avoiding any forced migration. This strategy was recently clarified by Microsoft as a user-friendly approach to encourage the switch.

A Growing Number of Issues in Classic Outlook

As Microsoft invests more in the New Outlook, concerns have arisen regarding the lack of development and quality assurance in Classic Outlook. Reports indicate a sharp increase in user-reported bugs, signaling that Classic Outlook may no longer be a priority for the tech giant. In recent months, notable issues have plagued users, including:

  • April: Problems arose during app downloads.
  • June: Following a significant calendar feature update, users encountered multiple bugs, with fixes taking considerable time.
  • Also in June: Basic email functionality was compromised, severely impacting user experience.

Current Bug Affecting Classic Outlook Users

Recently, another significant issue emerged for Classic Outlook users, marked by an error message stating:

Cannot 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.

Microsoft has provided additional context regarding this error, indicating that users can utilize Fiddler trace to verify the issue. For those unfamiliar, Fiddler trace is a tool designed to inspect traffic and assist in debugging web-related problems. Microsoft elaborates:

This error message can occur for different reasons. Not every instance of this error is the same issue but recent support cases around this have been for user mailboxes.

To confirm if this issue applies, capture a Fiddler trace when you reproduce the problem and then search the trace for this error:

Microsoft. Exchange. RpcClientAccess. ServerTooBusyException: Client is being backed off ---> Microsoft. Exchange. RpcClientAccess. ClientBackoffException: ErrorCode: ClientBackoff, LID: 49586 - Authentication concurrency limit is reached. --- End of inner exception stack trace ---

Next Steps and Possible Workarounds

Microsoft acknowledges the existence of this bug and is currently investigating its root causes. However, the company advises that users currently have no direct fix and suggests opening a support case via the Microsoft 365 Admin portal in order to mitigate the issue.

Fortunately, a straightforward workaround is available. Users experiencing difficulties can switch to the New Outlook for Windows or utilize Outlook Web Access (OWA) as alternate solutions. For more details about this issue, interested individuals can refer to the official support article here.

Source & Images

Related Articles:

Microsoft: Intelligent Windows Upgrade Powered by NPUs on the Horizon
Nightingale Survival Game Giveaway on Epic Games Store This Week

Leave a Reply

Your email address will not be published. Required fields are marked *