Root Cause Analysis: Why Windows Update Error 0x8007000E (Out of Memory) Happens
Quick Fix Summary
TL;DRFree up disk space on your system drive (C:) and run the Windows Update Troubleshooter.
Error 0x8007000E is the HRESULT code for E_OUTOFMEMORY, indicating Windows Update failed due to insufficient available memory (RAM) or, more commonly, virtual memory (page file) space. This is often a resource exhaustion issue during the download, extraction, or installation phase of an update.
Diagnosis & Causes
Recovery Steps
Step 1: Free Up Critical Disk Space
The Windows page file requires free space on the system drive to expand. Use Disk Cleanup to remove temporary files, old updates, and system restore points.
cleanmgr /sageset:65535
cleanmgr /sagerun:65535Step 2: Reset Windows Update Components Manually
Stop Windows Update services, rename the SoftwareDistribution and Catroot2 cache folders, then restart services. This clears corrupted data that can cause memory bloat.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserverStep 3: Run the Windows Update Troubleshooter & DISM
Use the built-in troubleshooter, then run Deployment Image Servicing and Management (DISM) to repair the underlying Windows image, which can resolve component corruption leading to resource issues.
msdt.exe /id WindowsUpdateDiagnostic
DISM /Online /Cleanup-Image /RestoreHealthStep 4: Perform a Clean Boot & Install Update
Boot with minimal drivers and startup programs to eliminate software conflicts. Install the update in this clean state, then reboot normally.
msconfigStep 5: Manually Download and Install the Update
If the automated process consistently fails, download the standalone update package (MSU) from the Microsoft Update Catalog and install it manually, which uses a different installer path.
wusa.exe "C:\Path\To\Update.msu" /quiet /norestartArchitect's Pro Tip
"Check `C:\Windows\Logs\CBS\CBS.log` for '0x8007000e' *after* the 'Exec' phase. This often points to the Component-Based Servicing stack failing due to memory pressure during finalization, not the initial download."
Frequently Asked Questions
Is 0x8007000E always about physical RAM?
No. While physical RAM can be a factor, it's more frequently related to virtual memory (page file) exhaustion. The error occurs when a process (like TrustedInstaller.exe) cannot allocate more memory from the system's memory manager, which depends on both RAM and available page file space on disk.
Can this error occur on systems with plenty of free RAM?
Yes. It can be triggered by memory fragmentation, handle exhaustion, or a bug in a specific driver/service causing a localized memory leak during the update process, even if overall system memory appears sufficient.