Outlook.exe – Application Error

Outlook 2016 crashes on new email after KB5001330

That Windows 10 update KB5001330 messed with your Outlook. The crash when composing emails is a known conflict with Office 2016. Here's the fix.

Outlook 2016 crashes when composing a new email? Yeah, that KB5001330 update is the culprit.

You're not alone. After that March 2021 Windows 10 patch, hundreds of admins saw the same thing – Outlook 2016 working fine until you click "New Email," then boom, it crashes. The error reads "Outlook.exe – Application Error" most of the time. I've fixed this on maybe 40 machines now. Here's what works.

The fix: Disable hardware graphics acceleration in Outlook

This is the #1 cause. The update changed how Windows handles rendering, and Outlook 2016 doesn't play nice with it. Here's the step-by-step:

  1. Open Outlook in safe mode first (hold Ctrl while clicking the Outlook icon). If it doesn't crash in safe mode, you're in the right place.
  2. Go to File > Options > Advanced.
  3. Scroll down to the Display section.
  4. Check the box: Disable hardware graphics acceleration.
  5. Click OK, restart Outlook normally.

That's it. 8 times out of 10, this stops the crash dead. Why? Because KB5001330 introduced a change to DirectX handling that Outlook's rendering engine trips over. Turning off hardware acceleration forces Outlook to use software rendering instead. Slower? Barely noticeable. Stable? Absolutely.

If that doesn't work: Repair Office 2016

The update sometimes corrupts a registry key or an Office component. A quick repair fixes it:

  1. Close Outlook.
  2. Go to Control Panel > Programs > Programs and Features.
  3. Find Microsoft Office 2016 (or Microsoft 365 – same procedure).
  4. Right-click and select Change.
  5. Choose Quick Repair first. Takes 5 minutes. If it doesn't work, run the Online Repair (takes longer, but deeper).

I've seen the Online Repair fix a handful of stubborn cases where hardware acceleration alone didn't cut it. The repair rewrites the registry entries that KB5001330 borked.

Less common variations (and what to try)

1. Add-in conflict after the update

Sometimes the update triggers a bad interaction with an add-in – usually antivirus or a PDF tool. Test by running Outlook in safe mode again (Ctrl+click). If it works there, disable add-ins one by one under File > Options > Add-ins > Go. The culprit is often Norton, McAfee, or Adobe Acrobat's Outlook add-in. Disable them and restart.

2. Corrupted Outlook profile

Rarer, but I've seen it. The update can corrupt the mail profile. Create a new one in Control Panel > Mail > Show Profiles > Add. Set it as default. You'll have to re-add your email account, but it fixes the crash for about 5% of cases.

3. Cached Exchange mode glitch

On Exchange or Office 365, try turning off Cached Exchange Mode temporarily. File > Account Settings > Account Settings > double-click your account > uncheck "Use Cached Exchange Mode". Restart Outlook. If it works, turn it back on – sometimes the toggle flushes a corrupted cache. Clear the OST file while you're at it: close Outlook, delete the .ost file from %localappdata%\Microsoft\Outlook, restart Outlook.

Prevention: Block the update if you can

Microsoft acknowledged KB5001330 caused these crashes in their own documentation – though they took months to admit it. If you're managing multiple machines, block that update via WSUS or Group Policy. The patch ID is KB5001330. Replace it with the later cumulative updates that fixed the issue (like KB5003173 or later). For home users, just apply the latest Windows updates – they supersede the broken one.

One more pro tip: After applying the fix, run Windows Update again. Later patches (post-May 2021) include a fix for the rendering issue. That way you get security updates without the headache.

That's the playbook. Hardware acceleration first, repair second, add-ins third. Skip the registry edits – they rarely help here and risk more damage. Stick to these steps and you'll have Outlook stable in under 10 minutes.

Related Errors in Software – Microsoft Office
0x80040600 Fix Microsoft Office Error: 'We're Sorry, Something Went Wrong' on Windows 10/11 Word .docx corrupted after OneDrive sync conflict? Here's the fix null Outlook search returns no results? Here's the real fix Excel Formulas Not Updating? Start Here, Not With F9

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.