[German]Users of Microsoft Outlook 365 (version 2407 build 17830.20138 and higher) occasionally report that the application crashes. This is caused by corrupted, server-based rules for the Microsoft 365 email account. Microsoft has now published a workaround to temporarily fix this problem.
Advertising
User report about Outlook 365 crashes
For example, I am aware of the Microsoft Answers forum post I very recently started having Outlook crash due to ucrtbase DLL dying. Outlook even crashes in SAFE mode from August 5, 2024. A user complains that Outlook has been crashing "recently" because the ucrtbase.dll has a problem. He provided the following excerpt from the event viewer in the forum post.
Faulting application name: OUTLOOK.EXE, version: 16.0.17830.20138, time stamp: 0x66aaad8c
Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71
Exception code: 0xc0000005
Fault offset: 0x000000000005137c
Faulting process id: 0x0x5A00
Faulting application start time: 0x0x1DAE741D3515015
Faulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE
He uses Windows 11 23H2, on which Office 365 with classic Outlook is installed. These crashes would also occur in safe mode (SAFE mode). A Microsoft forum moderator replied that an error was documented internally that was caused by faulty rules and that the whole thing was most likely server-based and most likely came from the service.
The Microsoft forum moderator suggests to clean up and delete the rules using Outlook Web Access. Alternatively, the rules should be deleted using the following command:
Outlook.exe /cleanrules
Workaround from Microsoft
On August 16, Microsoft published the support article Classic Outlook unexpectedly closes at start up on faulting module ucrtbase.dll, which confirms the above error. It states that after updating Outlook for Microsoft 365 Version 2407, Build 17830.20138, unexpected crashes may occur at startup. Outlook is then closed, which also applies to SAFE mode. The support article also shows an excerpt from the event display, as above.
Advertising
Microsoft confirms there that this problem occurs when the server-based rules for the M365 email account are corrupted or cannot be processed by Outlook. The Microsoft support article also suggests removing all rules via Outlook.exe /cleanrules and creating a new profile if necessary. Alternatively, you can use Outlook Web Access to clean up the rules. Microsoft has not revealed when this error will be fixed. I currently have no overview of how often this error actually occurs. (via)
Advertising
