Microsoft removed three patches for Outlook which were causing problems with the email client. We are expecting a fix sometime in the future.

KB4011042, KB3191849 and KB3213654 caused crashes to Outlook 2010, 2013 and 2016

The three variants of Outlook began crashing after the installation of the updates. The patches were supposed to address issues with attachments that had ellipsis or exclamation marks in their file names. Unfortunately, instead of doing that, the updates caused unexpected crashes when an email with an attachment was clicked on.

You can currently see on the KB page of each update a little notice that informs you about Microsoft’s decision to pull them.

Manually remove the update until further notice and a safe fix for the issue is released

The company offered more information on the subject in a Reddit discussion and confirmed that the updates caused crashes that had a nasty impact on the three versions of Outlook.

According to Microsoft, a new update for 32-bit Outlook 2010 is now being developed and will be posted as soon as it becomes available and safe for use.

The crashes have been experienced on all versions of Windows.

Microsoft recommends that if you already have the 32-bit update installed, you remove it until a new enhanced and safer version becomes available.

Users are advised to remove the update as soon as possible and do so manually because Microsoft doesn’t provide an automatic patch removal tool.

RELATED STORIES TO CHECK OUT:

  • Windows 10 Autumn Creators Update could arrive in certain countries
  • Fix: Outlook will not open on Windows 10
  • Windows 7 KB4022719 causes printing issues, breaks Outlook search, and more

If the advices above haven’t solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on TrustPilot.com) to easily address them. After installation, simply click the Start Scan button and then press on Repair All.

Still having issues? Fix them with this tool:

SPONSORED

Email *

Commenting as . Not you?

Comment