How to Fix Outlook Error 0x8007000E in Windows 2026

Outlook error 0x8007000E usually shows up when Outlook runs out of memory or system resources while trying to open, send, or sync mail. It often appears alongside a message about insufficient memory, and it tends to strike right when a large attachment or a busy inbox is involved. This guide walks through the exact steps needed to clear it and get Outlook running smoothly again.

Key Takeaways

  • Error 0x8007000E is typically caused by low system memory, a bloated PST/OST file, or a corrupted add-in.
  • Restarting Outlook and closing background apps often resolves the issue immediately.
  • Running the built-in Inbox Repair Tool (SCANPST.EXE) fixes most cases tied to data file corruption.
  • Disabling unnecessary add-ins prevents memory conflicts that trigger this error.
  • Keeping Outlook and Windows updated closes off many of the bugs that cause this code to appear.

How to Fix Outlook Error 0x8007000E

Work through these steps in order. Most users find the problem resolved within the first three or four steps, so there is no need to jump straight to the more advanced fixes.

Step-by-Step Guide

  • Step 1: Close Outlook completely, along with any other memory-heavy programs running in the background, such as browsers with dozens of tabs open. Reopen Outlook and check whether the error returns.
  • Step 2: Restart the computer. This clears temporary memory allocations that can build up over a long session and often resolves the error on its own.
  • Step 3: Check available disk space on the drive where Outlook data files are stored. Right-click the drive in File Explorer, select ‘Properties’, and confirm there is at least a few gigabytes free. Low disk space can trigger the same memory-related error.
  • Step 4: Run Outlook in Safe Mode to rule out a problematic add-in. Press the Windows key and R, type ‘outlook.exe /safe’, and press Enter. If Outlook works fine here, an add-in is likely the culprit.
  • Step 5: Disable unnecessary add-ins. In Outlook, go to ‘File’, then ‘Options’, then ‘Add-ins’. At the bottom, select ‘COM Add-ins’ next to Manage, click ‘Go’, and uncheck any add-ins not essential for daily work. Restart Outlook afterward.
  • Step 6: Repair the Outlook data file using the Inbox Repair Tool. Search for ‘SCANPST.EXE’ in Windows search (it is usually located in a path like C:\Program Files\Microsoft Office\root\Office16), open it, browse to the PST or OST file, and click ‘Start’ to scan and repair.
  • Step 7: Repair the Office installation. Open ‘Control Panel’, go to ‘Programs and Features’, find Microsoft Office in the list, select it, and choose ‘Change’. Pick ‘Quick Repair’ first, and if the error persists, run ‘Online Repair’.
  • Step 8: Update Windows and Outlook to the latest versions. In Outlook, go to ‘File’, then ‘Office Account’, then ‘Update Options’, and select ‘Update Now’. For Windows updates, go to ‘Settings’, then ‘Windows Update’, and check for updates.

How to Fix Outlook Error 0x8007000E

Tip: If the error keeps appearing after every attachment or large email, the mailbox itself may just be too large for smooth performance. Archiving older emails into a separate PST file often clears up enough memory overhead to stop the error for good.

Common Problems and Fixes

The error reappears right after a repair

This usually means the repair only fixed part of the data file. Run SCANPST.EXE a second time on the same file. Repeated scans catch corruption that a single pass sometimes misses.

Safe Mode still shows the error

If the error happens even with add-ins disabled, focus on the data file itself rather than add-ins. Move directly to the Inbox Repair Tool step and confirm the file path is correct before scanning.

Outlook freezes during the repair process

Large PST files can take a long time to scan, sometimes 20 minutes or more depending on size. Avoid closing the tool during this process, since interrupting a scan can cause further corruption. Let it finish fully before reopening Outlook.

Online Repair does not fix the issue

In rare cases, the Office installation itself needs to be removed and reinstalled. Uninstall Office through ‘Control Panel’, restart the computer, then reinstall using the original installer or the Microsoft 365 account portal.

Frequently Asked Questions

What causes Outlook error 0x8007000E?

It is most often caused by low available memory, a large or corrupted PST or OST file, or a conflicting add-in competing for system resources.

Is Outlook error 0x8007000E related to a virus or malware?

No. This error is tied to memory and data file issues, not malware. Antivirus scans are not part of the standard fix for this code.

Will running SCANPST.EXE delete any emails?

No, the Inbox Repair Tool repairs corrupted sections of the data file without deleting existing emails. A backup copy is still worth keeping before running any repair.

How long does the Inbox Repair Tool take to run?

It depends on file size. Smaller PST files finish in a few minutes, while files over several gigabytes can take much longer.

Does closing background programs really help?

Yes. Since the error is memory-related, freeing up RAM by closing unused programs directly reduces the chance of Outlook running out of resources.

Can this error happen with Outlook on the web?

No, error 0x8007000E is specific to the desktop Outlook application on Windows and does not occur in the web version.

Should the data file be split if it keeps causing this error?

Yes, splitting or archiving a large mailbox into a secondary PST file reduces the load on the active data file and often prevents the error from recurring.

Does reinstalling Office guarantee the error will not return?

It resolves most installation-level causes, but if the underlying issue is a consistently oversized data file, the same symptoms can return unless the mailbox is also archived or trimmed down.

Picture of Roberto Gregoire
Roberto Gregoire

Roberto Gregoire is a Desktop Support Technician with over 7 years of experience fixing Windows and Microsoft Office problems for real users. He writes the way he troubleshoots: step by step, in order, with every instruction tested first. More about Roberto