{"id":34832,"date":"2024-08-19T22:39:25","date_gmt":"2024-08-19T20:39:25","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=34832"},"modified":"2024-08-19T22:39:25","modified_gmt":"2024-08-19T20:39:25","slug":"workaround-for-outlook-365-crash-aug-2024-published-by-microsoft","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2024\/08\/19\/workaround-for-outlook-365-crash-aug-2024-published-by-microsoft\/","title":{"rendered":"Workaround for Outlook 365 crash (Aug. 2024) published by Microsoft"},"content":{"rendered":"

[German<\/a>]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.<\/p>\n

<\/p>\n

User report about Outlook 365 crashes<\/h2>\n

\"\"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<\/a>\u00a0 from August 5, 2024. A user complains that Outlook has been crashing \"recently\" because the ucrtbase.dll<\/em> has a problem. He provided the following excerpt from the event viewer in the forum post.<\/p>\n

Faulting application name: OUTLOOK.EXE, version: 16.0.17830.20138, time stamp: 0x66aaad8c<\/p>\n

Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71<\/p>\n

Exception code: 0xc0000005<\/p>\n

Fault offset: 0x000000000005137c<\/p>\n

Faulting process id: 0x0x5A00<\/p>\n

Faulting application start time: 0x0x1DAE741D3515015<\/p>\n

Faulting application path: C:\\Program Files\\Microsoft Office\\root\\Office16\\OUTLOOK.EXE<\/p><\/blockquote>\n

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.<\/p>\n

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:<\/p>\n

Outlook.exe \/cleanrules<\/p>\n

Workaround from Microsoft<\/h2>\n

On August 16, Microsoft published the support article Classic Outlook unexpectedly closes at start up on faulting module ucrtbase.dll<\/a>,\u00a0which 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.<\/p>\n

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<\/em> 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<\/a>)<\/p>\n","protected":false},"excerpt":{"rendered":"

[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 … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,11,22],"tags":[47,125,195],"class_list":["post-34832","post","type-post","status-publish","format-standard","hentry","category-issue","category-office","category-update","tag-issue","tag-office","tag-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34832","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=34832"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34832\/revisions"}],"predecessor-version":[{"id":34833,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/34832\/revisions\/34833"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=34832"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=34832"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=34832"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}