![]() ![]() Microsoft has moved fairly quickly to roll out a fix. Unconfirmed reports said that uninstalling the patch for KB4565463 fixed the Outlook problem. Many people have restored Outlook by rolling back to a pre-July 2020 update state (see below) which strongly suggests there’s a link with the latest patches. ![]() But that doesn’t fit with the timing of the July updates and the Outlook problems. Microsoft is being vague about who is affected and in what exact circumstances.Īt the moment Microsoft is insisting that “This problem is not associated with any of the security patches so there is no need to uninstall them if Outlook will not launch.”. You read that right – using Microsoft Outlook to connect with Microsoft Exchange Server caused the fault. Exchange Server means anyone using Office 365 hosted email and possibly / Hotmail etc. It seems that trying to connect to Exchange Server could make Outlook crash. ![]() These are pushed out by Microsoft and often installed automatically by people and organizations.Īround the same time as the July updates went out Outlook for Windows started showing errors for customers around the planet. The problem appears to have started with one of the July updates for Office. Microsoft hasn’t fully explained what happened and what they’ve said doesn’t fit with the publicly known facts. ” Except that Outlook won’t start even in Safe mode. Safe mode could help you troubleshoot the problem. Retries to start might get a message saying “Outlook couldn’t start last time. Outlook for Windows tries to start but crashes with an exception code 0xc0000005. We’ll explain Microsoft’s blunder, what you can do if affected and how to avoid the buggy patch. An update can crash Outlook for Windows entirely and the reason for the problem makes the bug especially humiliating for Microsoft. Microsoft has made a major blunder with the July patches for Office. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |