Microsoft has pulled the first two patches entirely but doesn’t recommend users uninstall KB4461529, as it remedies four remote code execution flaws. Instead, it says users should use Outlook Web Access to perform tasks. Obviously, all of this marks a huge inconvenience for users, with the bugs first noticed shortly after their release on November 6. Currently, Microsoft is still investigating the issues and is yet to give an ETA on when users can expect normal functionality.

Persistent Quality Issues

It’s worth noting that the Outlook 2010 crashes only happen in 64-bit versions, so if you’re using 32-bit there’s no need to do anything. “After updating Outlook 2010 to the November 2018 Public Update KB 4461529 Outlook crashes or closes suddenly on startup,” says the support page. “The issue only affects 64-bit installations of Outlook 2010. Microsoft is investigating the issue and we will update this page when further details become available. As a workaround, you could try using Outlook Web Access.” The bug follows a rough couple of months for Microsoft after issues with the Windows 10 October 2018 Update. The next major Windows version is only rolling out now after a file deletion and zipping bug. The company has now admitted to another, mapped drive bug, and promised higher quality in future releases. Obviously, the Outlook 2010 bugs are in no way related and will affect a smaller userbase. However, it’s hard to see how these ones were missed, given their prevalence and very obvious nature.

Microsoft Pulls Crash Causing Outlook 2010 Patches - 65Microsoft Pulls Crash Causing Outlook 2010 Patches - 24Microsoft Pulls Crash Causing Outlook 2010 Patches - 27Microsoft Pulls Crash Causing Outlook 2010 Patches - 55Microsoft Pulls Crash Causing Outlook 2010 Patches - 61