Debilitating ‘Outlook must close’ bug associated with a negative Windows cumulative update
Internecine conflict appears to be a recurring theme at Microsoft, nonetheless it is taken by that one to new levels. Somehow, someone forgot to test the most recent patched edition of Outlook with the most recent patched version of Home windows. The full total result can be an error message which makes Outlook inoperable.
The official announcement appears on the Microsoft 365 support site:
After updating to Edition 2005 Build 12827.20268 or more and starting Outlook you might start to see the following error prompt:
The Outlook Team will be investigating this presssing issue with the Home windows Team. We are uncertain yet if the principal fix should come from Windows or even Outlook. When we have significantly more info on fix details we will add them here.
If you click on OK, the ScanPST Inbox Repair Device starts. Feel the repair procedure, reboot, and – surprise! – you again obtain the error message. Wash. Rinse. Repeat. On the weekend with this one no telling just how many hours have already been wasted. The good thing, though, is your PST file is okay – and has been always.
Since best I could tell, the show-stopper bug just occurs on devices that:
- Make use of PST, not OST, data files;
- Operate Microsoft 365 version 2005 Current Channel discharge 12827.20268 (from June 2) or Current Channel release 12827.20336 (from June 9);
- And possess installed the June 2020 Win10 cumulative update (KB 4557957 for version 2004, KB 4560960 for versions 1903 or 1909, or KB 4561608 for version 1809).
Microsoft’s remedy – published for the reason that Microsoft 365 assistance article – involves modifying the Registry to create Outlook overlook the bogus &ldquo manually;corrupt” PST document on startup. Actually, the “corrupt” PST document isn’t corrupt from just about all. It’s Windows messin&rsquo just; with Outlook.
If you don’t desire to pummel your Registry, Diane Poremsky at Slipstick provides a straightforward downloadable solution.
in the June cumulative updates The insider report I’ve says that the bug is in fact, but that it’ll end up being easier for Microsoft to repair the issue by working about it in a fresh Microsoft 365 Present Channel release.
You might expect that the working workplace people aren’ t happy concerning this one particularly.
Tell me again&hellip once;, who tests these things?
Solace for muzzled Outlook devs on the AskWoody.com Lounge.