[German]Microsoft has released a new build of Microsoft 365 that should fix the crashes of Microsoft Outlook and other Office 365 applications on Windows Server 2016 that I reported in January 2025.
Advertising
Outlook/Excel crashes
Blog reader Robert informed me by email in January 2025 that he was experiencing problems with Outlook under Microsoft 365 on Windows Server 2016 (as well as Windows Server 2019) Terminal Server. Microsoft Outlook in one of the builds 16.0.18324.20168 crashed when called up by his customers.
Microsoft Outlook crashes with the above build on Windows Terminal Server under Windows Server 2016 with the following error message.
The file react-native-win32.dll was reported as not found in the specified path, even though the file exists. Robert suspected that it might be related to an Edge update, and replacing the .dll with an older version or downgrading Microsoft 365 to an older build fixed the problem. I had picked up on this in the blog post Microsoft Outlook 365 or other MS 365 apps are dropping suddenly errors. Microsoft had confirmed the issue for Windows Server 2016 and 2019 and recommended a downgrade.
Advertising
New build should fix the error
On January 16, 2025, an update for Microsoft 365 Apps will be released in the Current Channel, as can be seen from the entry MC981666 in the Microsoft 365 Message Center.
The update for Microsoft 365 Apps will be rolled out gradually to users of this update channel from January 16, 2025 (PST). The update will take place automatically.
According to the release notes, version 2412 (build 18324.20194) fixes a problem that causes apps to exit unexpectedly when running on Windows Server 2016. However, this is exactly the error that I addressed in the section above and in the blog post Microsoft Outlook 365 or other MS 365 apps are dropping suddenly errors.
The colleagues at Bleeping Computer noticed this update and addressed it in this post. This post also mentions the downgrade to an earlier Microsoft 365 build, which was previously described as a workaround.
Anyone who has performed this downgrade and then deactivated the update installation in Office 365 under File, Office account, Update options must undo this in order to receive the new build.
Question for those affected: Can you confirm that the problem has been resolved and are you rolling out the build mentioned?
Advertising
