Search the Community

Microsoft has been trying to get more users onto New Outlook for Windows, and it is doing so not just by enforcing the newer app but also by making improvements along the way. In doing so, though, the company has caused the Classic Outlook app to bug out in the past. The classic app received a major Shared Calendar-related upgrade recently, with many " long-awaited improvements" as well as "small changes in form and function." As the name suggests, the Outlook Shared Calendar essentially allows multiple people to interact with and manage the calendar. With Shared Calendar improvements enabled, users will see the following changes: Instant sync and view of shared calendars Editing series end date does not reset the past Accepting meeting without having to send a response Last Modified By no longer shown in the meeting item Adding same calendar multiple times can't be done Duplicate calendars simultaneously selection Attachments addition not possible when responding to a meeting invitation Event drafts auto-save changes The "Download shared folders" setting is ignored Unfortunately, as with any major feature upgrade, there are bugs, and Microsoft has confirmed this is no different. The tech giant has shared official guidance for it so that users can work around the problems. According to the company, "Shared Calendar improvements are now enabled by default in the most recent versions of Outlook, in all update channels for Microsoft 365 Apps," and thus, the bugs are likely to affect many. Here are some of the bugs Microsoft is investigating, as well as their workarounds: Bug Workaround Meeting cancellation sent unexpectedly to some attendees in classic Outlook In a REST shared calendar, after adding or removing an attendee, or forwarding a meeting, a meeting cancellation may be sent unexpectedly to some attendees. Use the Outlook Web App or new Outlook when adding or removing an attendee or forwarding a meeting. Attendees do not get updates on attachment changes by Delegate When a delegate sends an update on a meeting that requires removing an attachment on an occurrence of a meeting series, the recipients may not get some or all of the attachment changes. In the delegate's Sync Issues folder, you'll see sync errors. Example: 17:23:26 Synchronizer Version 16.0.15313 17:23:26 Synchronizing Mailbox 'Delegate User' 17:23:26 Synchronizing local changes in folder 'Manager User' 17:23:27 Uploading to server 'https://outlook.office365.com/mapi/emsmdb/?xxxxxxxx-xx' 17:23:30 Error synchronizing folder 17:23:30 [0-320] There is no known workaround. It is recommended, whenever possible, to save attachments to SharePoint or to OneDrive and share with a link. After an attachment is deleted from an existing meeting, it may reappear after being deleted Please wait approximately one minute to give the sync time to complete. Additionally, it is advisable to save attachments to SharePoint or OneDrive whenever possible and share them using a link. A meeting created by a delegate with limited calendar access disappears and is unsent when a sensitivity label other than "Normal" is selected Three potential solutions to address this issue, each with their own implications for functionality: Manager can update delegate's permissions to allow viewing of private items. Delegate can change the sensitivity label of the meeting to "Normal". Delegate can disable Shared Calendar Improvements (not recommended). Aside from these, Microsoft has also fixed several other bugs, which you can find in the official support article here on the company's website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of May): 2,377 RIP Matrix | Farewell my friend

Microsoft recently addressed a major bug related to Classic Outlook and Word wherein typing would lead to high CPU usage with spikes of up to 50%. Another Outlook bug has hit this time again on the classic app. Microsoft has confirmed sign-in troubles with error codes "CAA2000B, 4usqa, and 49dvs." This is the third major bug in the last month to affect Classic Outlook while Microsoft tries hard to transition away from it to New Outlook for Windows. Last month, downloads for Classic Outlook were affected. About the new sign-in issue that affects both Outlook for Windows and Outlook for Mac, Microsoft writes: Something went wrong We couldn’t sign you in. If this error persists, contact your system administrator and provide the error code CAA2000B. AADSTS500014: The service principal for the resource is disabled. Some users that open Outlook for Mac get sign in errors like the following: Error Something when wrong. [49dvs] Microsoft has learned that a disabled service principal "40775b29-2688-46b6-a3b5-b256bd04df9f" is causing the issue and thus re-enabling it is a way to fix these troubles. The company has provided a detailed workaround for it. The tech giant writes: You can find the issue in this support article here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

Earlier this month, Microsoft confirmed a problem with Classic Outlook wherein typing would lead to high CPU usage and system resource hogging. The company said that the processor utilization would hit as high as 30-50%. The tech giant had provided a workaround for the problem and that involved switching to the Semi Annual channel. The company earlier today provided an update on the issue. It says that the Word support team has devised a fix for the problem and it would be deployed on the Current channel and beta channel soon. Microsoft writes: Unfortunately, though, the bug now haunts the Semi Annual channel and the way to work around the problem is to go back to version 2405. However it is not recommended and should only be done if an urgent workaround is required. It writes: You can find the support article for the issue here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

The Microsoft 365 support team must have had a busy time this last week, as the company has been faced with multiple outages, with the latest one being Teams failing to share files. Meanwhile, the Classic Outlook app is also suffering from buggy updates as Microsoft recently broke downloads. Another bug has hit the Classic Outlook app now, and this one is causing high CPU usage often as high as "30 to 50%," leading to system hogging and performance issues. This is happening when typing, indicating that it is most certainly a bug, as something like typing should never be that intense unless you are still running a Pentium 4 or an original Athlon or something like that. Microsoft has explained the issue below: Microsoft has also offered a workaround for the bug, and it involves switching to the semi-annual channel, which does not appear to have this issue, although there may be other minor ones. The company has explained how to do so using either the Office Deployment Tool or by Registry edits. It writes: You can find the support article here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Microsoft has fixed a Classic Outlook download and installation bug that would not allow users to download the app in any language other than English. The company says that this became a problem as it pushes New Outlook for Windows on new Microsoft 365 consumer installs at the expense of the classic app. If you have been reading Neowin for a while, you are probably aware of just how badly Microsoft wants everyone to embrace the new mail app, despite many admins seemingly feeling like it's "hot garbage" The company has explained the issue (below) and has deployed a fix for the problem with a new dropdown for installing the Classic Outlook app in other languages. It has also given an estimated timeline for the rollout of the fix: You can download the app in the language of your choice from this dedicated support page, and view the support article here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Microsoft has confirmed a clicking and scrolling bug on Classic Outlook. Aside from that, the Redmond company has also shared a workaround regarding another Outlook issue that started affecting users a few days ago. The problem is with the Server assisted search function in Outlook 2016. It explains: Microsoft notes that it is currently investigating the issue, and it is being tracked under ID MC976059 on the Microsoft 365 (M365) Service health dashboard. If you are an M365 administrator and the ID number seems familiar, that is because Microsoft had recently assigned the same ID for the case overlooking the deployment of New Outlook on Windows 10. A workaround involving the Registry editor has been provided so that Exchange Server-assisted Search can be disabled. You can find the support article here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of January): 487 RIP Matrix | Farewell my friend

Microsoft has confirmed a new issue affecting Classic Outlook. The problem started after updating to some of the recent builds as users reported issues with clicking and scrolling through emails via a message list. The company has, so far, documented four such scenarios and it appears that the Current Channel Outlook Version 2411, Build 16.0.18227.20082, is when it all started. The Message List in Outlook shows the sender, the subject, and a preview of the message by displaying a part of the first line of text. Microsoft has explained the issue and the different scenarios when users may encounter the bug below: The company says it is currently investigating the problem and has also provided a temporary workaround for it: You can find the issue in this support article here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of January): 487 RIP Matrix | Farewell my friend

Microsoft recently fixed a Classic Outlook bug that led it to crash on Windows Server 2016. Following that, the tech giant has confirmed another Classic Outlook APPCRASH. On a support document, it explains how it would crash when trying to start a new email, or when replying or even forwarding. Alongside that, the information related to the crash event log has also been provided such that users can confirm whether that is indeed the bug. Microsoft writes: Microsoft has provided a workaround for the problem for those on the current channel which involves reverting to the previous version: You can find the support document here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ RIP Matrix | Farewell my friend

This week Microsoft closed two major issues with Classic Outlook. First, it has re-resolved a bug where users would be unable to add their Gmail account. I say re-resolved since the company had fixed a similar issue back in September though it seems the problem had resurfaced. Either one of the two error messages would be displayed, Microsoft states: "We couldn't log on to the incoming (POP/IMAP) server. Please check your email address and password and try again", or “We weren’t able to set up your Google account with IMAP. You may need to make changes to your Gmail settings.” As of now, the bug stands as fixed. Microsoft has explained in detail how to apply the "Retry Solution" fix in case you were affected: In case the Retry Solution above does not work, the company has also shared a manual workaround in a step-by-step guide. You can find that here in the support article on Microsoft's website. The other Classic Outlook bug fixed is related to the Windows Copy shortcut (Ctrl + C) that is used very commonly by users. Essentially, Outlook would hang or freeze when copying text using the shortcut. The issue has been resolved in the following versions and builds across the different channels: You can find the support article here on Microsoft's website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ RIP Matrix | Farewell my friend

For many, the Classic Outlook app is a relief after the almost universally despised new Outlook for Windows. However, it is also not perfect. In fact, Microsoft has acknowledged an odd bug where the app would just hang when performing simple tasks such as copying text. In a new support document, Microsoft confirmed that customers with certain Office versions and languages with an Input Method Editor might experience Outlook freezing when using the Ctrl + C shortcut. As of right now, the origin of the bug is unknown, and Microsoft is looking into the problem. Fortunately, two workarounds should bring the email client back to life. One is to revert to a previous version of the Input Method Editor or revert Outlook to an earlier build. Here is how to go back to the previous version of Microsoft IME: Here is how to revert Outlook to one of the earlier versions: You can learn more in the official support document (via BleepingComputer). Last month, Microsoft confirmed a rather funny bug in Word, which would delete a locally stored file when attempting to save recent changes. Fortunately, Microsoft resolved the problem pretty quickly with a new version of Office apps. Hopefully, a fix for Outlook freezing when copying text will also be patched in no time. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. 2023: Over 5,800 news posts | 2024 (till end of October): 4,832 news posts RIP Matrix | Farewell my friend