Interactive Troubleshooter

Published: Oct 25, 2026

How to Fix Windows Update Error 0x8007000E Not Enough Memory

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Comprehensive troubleshooting guide addressing Windows Update Error 0x8007000E (ERROR_OUTOFMEMORY). This diagnostic tree covers memory allocation exhaustion, corrupt SoftwareDistribution caches, damaged system component stores, and registry heap constraints.

Full Diagnostic Tree & Step-by-Step Overview

When does Windows Update error 0x8007000E occur on your system?

Immediately upon checking for updates or downloading large feature updates.
During the final installation or percentage-based staging phase of the update.
When running Windows Update troubleshooter or applying servicing stack updates.
Accompanied by high RAM usage, low virtual memory warnings, or custom pagefile setups.

Select the specific symptom profile for errors during the update check or download phase:

The SoftwareDistribution or catroot2 folders are severely bloated or corrupted.
BITS (Background Intelligent Transfer Service) or Cryptographic services are hanging.
Network proxy, VPN interference, or TLS handshake memory allocation faults occur.
Corrupted XML metadata manifests block catalog file parsing.

Select the specific symptom profile for errors during the installation phase:

Component Store (WinSxS) integrity corruption or missing manifest files.
Insufficient disk space on the system drive causing pagefile expansion failure.
Locked system files or registry hives held by third-party background applications.
Outdated Servicing Stack Update (SSU) failing to parse newer package payloads.

Select the specific symptom profile for troubleshooter or servicing stack errors:

Corrupted Windows Installer database or locked security descriptor heaps.
Group Policy restrictions overriding memory allocation parameters for updates.
Corrupted Windows Update database file (DataStore.edb) exceeding buffer bounds.
WMI repository corruption impacting system diagnostic event tracing.

Select the specific symptom profile for physical/virtual memory constraints:

Pagefile is disabled or set to fixed size, restricting dynamic memory allocation.
Non-paged pool memory leak caused by malfunctioning third-party drivers.
Physical RAM hardware instability or faulty memory address mapping.
Registry size limit exhaustion restricting system heap allocations.

Reset Windows Update Cache and Catroot2 Directories

Solution:

Root Cause: SoftwareDistribution Cache Corruption

Error 0x8007000E translates to ERROR_OUTOFMEMORY. During download operations, the Windows Update agent (wuaueng.dll) caches incoming cabinet (.cab) and catalog (.cat) files inside the SoftwareDistribution directory. If metadata files become fragmented or corrupted, the update agent enters an infinite memory allocation loop trying to parse the malformed data structures, eventually exhausting available process heap memory and throwing an out-of-memory exception.

Diagnostic Verification:

Check the Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational for Event ID 20 or error code 0x8007000E during download tasks.

Inspect C:\Windows\Logs\CBS\CBS.log for memory allocation failure stack traces originating from package manifest parsing.

Step-by-Step Fix:

1Stop Windows Update Services:

Open PowerShell as Administrator and run the commands:

Stop-Service -Name wuauserv, cryptsvc, bits, msiserver -Force

2Rename Update Cache Directories:

Execute the following commands in the administrative PowerShell window to clear corrupted caches:

Rename-Item -Path "C:\Windows\SoftwareDistribution" -NewName "SoftwareDistribution.bak" -Force

Rename-Item -Path "C:\Windows\System32\catroot2" -NewName "catroot2.bak" -Force

3Restart Update Services:

Restart the core services using:

Start-Service -Name wuauserv, cryptsvc, bits, msiserver

4Re-attempt Update:

Open Windows Settings and check for updates to verify successful cache regeneration.

Prevention & Long-Term Monitoring:

Avoid abrupt hard shutdowns during active background updates, as this is the primary cause of SoftwareDistribution database corruption.

Restart BITS and Cryptographic Services with Queue Purge

Solution:

Root Cause: Background Intelligent Transfer Service (BITS) Deadlock

Background Intelligent Transfer Service manages file transfers over HTTP/HTTPS and handles background downloads for Windows Update. When BITS jobs encounter persistent deadlock states or corrupted transfer queues, memory handles remain allocated without release, causing subsequent update queries to fail due to heap exhaustion.

Diagnostic Verification:

Run bitsadmin /list /allusers in an administrative console to check for stalled or zombie transfer jobs blocking system queues.

Step-by-Step Fix:

1Clear Stuck BITS Transfer Queue:

Open an administrative Command Prompt and run:

bitsadmin /reset /allusers

2Reset Cryptographic Service State:

Stop the cryptographic services and clear pending transaction logs using:

net stop cryptsvc

rd /s /q "C:\Windows\System32\catroot2"

net start cryptsvc

3Re-register Update DLL Dependencies:

regsvr32.exe /s wuapi.dll

regsvr32.exe /s wups.dll

regsvr32.exe /s wuaueng.dll

4Reboot System:

Restart your computer to clear lingering memory handles and reinitialize transfer managers.

Prevention & Long-Term Monitoring:

Regularly run built-in maintenance tasks and ensure third-party download accelerators do not hook into BITS system pipes.

Flush Network Stack and Reset Winsock Protocols

Solution:

Root Cause: Network Stack Memory Buffer Exhaustion

When system updates are routed through misconfigured proxies, VPN tunnels, or corrupted TCP/IP stack parameters, Secure Channel (Schannel) negotiations can consume excessive paged pool memory. This buffer buildup leads to allocation failures during large payload handshakes with Microsoft update servers.

Diagnostic Verification:

Execute netsh int ip reset and netsh winsock reset to determine if network configuration resets clear socket allocation errors.

Step-by-Step Fix:

1Reset TCP/IP Stack:

Open an administrative Command Prompt and execute:

netsh int ip reset

2Reset Winsock Catalog:

Reset the Windows socket catalog to clean out rogue LSP hooks:

netsh winsock reset

3Flush DNS Resolver Cache:

Clear cached DNS entries using:

ipconfig /flushdns

4Re-configure Proxy Settings:

Ensure no legacy web proxies are intercepting secure Microsoft endpoints by running netsh winhttp reset proxy.

Prevention & Long-Term Monitoring:

Maintain clean network configurations and verify corporate VPN client versions are fully compatible with current Windows build servicing stacks.

Rebuild Update Metadata Index via PowerShell

Solution:

Root Cause: Corrupted XML Update Metadata Manifests

Windows Update relies on structured XML manifests stored within the datastore to catalog applicable updates. If XML parsing buffers encounter malformed syntax or truncation due to disk write interruptions, the parsing engine throws memory exhaustion exceptions when attempting to load index trees into RAM.

Diagnostic Verification:

Inspect C:\Windows\SoftwareDistribution\DataStore\Logs\edb.log for database page corruption or allocation error codes.

Step-by-Step Fix:

1Stop Windows Update Services:

Open PowerShell as Administrator:

Stop-Service -Name wuauserv

2Delete DataStore Database File:

Remove the corrupted database index file:

Remove-Item -Path "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" -Force

3Restart Update Service to Regenerate Index:

Start-Service -Name wuauserv

4Trigger Manual Update Scan:

Run UsoClient startscan to rebuild the metadata database cleanly.

Prevention & Long-Term Monitoring:

Ensure stable power delivery and regular file system health checks using CHKDSK.

Repair Component Store via DISM and SFC

Solution:

Root Cause: WinSxS Component Store Corruption

During the installation phase, Windows extracts component manifests from the WinSxS store. If system files or component manifests are corrupted or missing, the servicing engine fails to allocate necessary memory buffers for transactional staging, triggering error 0x8007000E.

Diagnostic Verification:

Review CBS log files for component manifest errors or missing file hashes during staging operations.

Step-by-Step Fix:

1Run Deployment Image Servicing and Management (DISM):

Open an administrative PowerShell prompt and execute:

DISM.exe /Online /Cleanup-Image /RestoreHealth

2Run System File Checker (SFC):

Scan and repair corrupted protected system files using:

sfc /scannow

3Restart Computer:

Reboot the system to allow pending file replacements to finalize.

4Re-run Windows Update:

Check for updates through Windows Settings.

Prevention & Long-Term Monitoring:

Perform periodic DISM and SFC health checks following major system driver upgrades.

Configure Dynamic Virtual Memory (Pagefile) Settings

Solution:

Root Cause: Insufficient Virtual Memory Allocation

Windows Update requires adequate virtual memory space (pagefile) to stage large installation packages, even on systems with substantial physical RAM. If the pagefile is disabled, restricted to a tiny fixed size, or located on a drive running out of free space, update installation routines fail with out-of-memory errors.

Diagnostic Verification:

Verify pagefile status by running Get-CimInstance Win32_PageFileSetting in PowerShell.

Step-by-Step Fix:

1Enable Managed System Pagefile:

Open System Properties (sysdm.cpl) > Advanced tab > Performance Settings > Advanced tab > Virtual Memory > Change.

2Configure Automatic Management:

Check the box for "Automatically manage paging file size for all drives" or set a custom initial and maximum size of at least 4096 MB (4 GB).

3Apply and Reboot:

Click Set, OK, and restart your computer to activate the new virtual memory allocation.

4Retry Installation:

Launch Windows Update and proceed with installation.

Prevention & Long-Term Monitoring:

Maintain a minimum of 15% free disk space on the system drive to ensure the Windows pagefile can expand dynamically during heavy workloads.

Clean Boot Troubleshooting to Clear Locked Handles

Solution:

Root Cause: Third-Party Service File Locks and Memory Contention

Third-party background utilities, antivirus software, or optimization suites can hook into Windows Update servicing processes, locking registry hives and memory heaps during installation staging and provoking error 0x8007000E.

Diagnostic Verification:

Use Resource Monitor (resmon.exe) under the Associated Handles tab to identify processes locking update staging directories.

Step-by-Step Fix:

1Open System Configuration:

Press Windows + R, type msconfig, and hit Enter.

2Configure Selective Startup:

Under the General tab, select "Selective startup" and uncheck "Load startup items".

3Hide All Microsoft Services:

Go to the Services tab, check "Hide all Microsoft services", then click "Disable all".

4Reboot and Update:

Restart your PC into Clean Boot mode, apply the Windows update successfully, then re-enable services via msconfig.

Prevention & Long-Term Monitoring:

Exercise caution with aggressive third-party system cleaners that tamper with system service permissions.

Manually Install Latest Servicing Stack Update (SSU)

Solution:

Root Cause: Outdated Servicing Stack Incompatibility

The Servicing Stack Update (SSU) provides the underlying infrastructure for installing Windows updates. An outdated SSU cannot properly parse newer package compression algorithms or memory addressing schemas introduced in recent cumulative updates.

Diagnostic Verification:

Run systeminfo in Command Prompt to verify your current OS build version and check Microsoft's official catalog for missing SSUs.

Step-by-Step Fix:

1Identify Required SSU Package:

Visit the Microsoft Update Catalog and search for the latest Servicing Stack Update corresponding to your Windows architecture (x64/ARM64).

2Download and Extract Standalone Package:

Download the .msu standalone update package.

3Install via Command Line:

Open an administrative Command Prompt and install the package using:

wusa.exe "C:\Path\To\Downloaded\SSU.msu" /quiet /norestart

4Reboot and Update:

Restart your system and proceed with standard Windows Update installation.

Prevention & Long-Term Monitoring:

Keep your servicing stack current by allowing automatic installation of critical baseline updates.

Reset Windows Installer Database and Service Heaps

Solution:

Root Cause: Corrupted Windows Installer Database

When Windows Update invokes bundled MSI installers for system components, a corrupted installer database or exhausted security descriptor heap causes MSIEXEC to throw memory allocation failures.

Diagnostic Verification:

Inspect application event logs for event source MsiInstaller showing memory allocation errors.

Step-by-Step Fix:

1Unregister and Re-register Windows Installer:

Open an administrative Command Prompt and run:

msiexec /unregister

msiexec /regserver

2Restart Installer Service:

net stop msiserver

net start msiserver

3Clear Temp Directories:

Clean out temporary installation caches in C:\Windows\Temp and C:\Users\<Username>\AppData\Local\Temp.

4Retry Troubleshooting:

Re-run the Windows Update troubleshooter or installation package.

Prevention & Long-Term Monitoring:

Periodically clear temporary user and system directories to prevent clutter.

Clear Restrictive Group Policy Memory Limits

Solution:

Root Cause: Restrictive Group Policy or Registry Constraints

Aggressive enterprise Group Policies or registry tweaks that limit background task memory usage or restrict WSUS/Windows Update cache allocations can trigger out-of-memory errors during diagnostic scans.

Diagnostic Verification:

Run gpresult /h C:\gp-report.html to review active computer configuration policies affecting Windows Update.

Step-by-Step Fix:

1Open Local Group Policy Editor:

Press Windows + R, type gpedit.msc, and press Enter.

2Navigate to Windows Update Policies:

Go to Computer Configuration > Administrative Templates > Windows Components > Windows Update.

3Reset Policy Settings:

Ensure policies such as "Specify intranet Microsoft update service location" or memory-limiting throttling rules are set to Not Configured.

4Force Policy Update:

Open an administrative Command Prompt and run gpupdate /force.

Prevention & Long-Term Monitoring:

Document all custom group policy adjustments applied to managed workstations.

Rebuild Corrupted DataStore.edb Database

Solution:

Root Cause: Extensible Storage Engine (ESE) Database Corruption

Windows Update uses an ESE database (DataStore.edb) to track update metadata. Database page corruption causes memory buffer overflows during troubleshooting queries and update scans.

Diagnostic Verification:

Check Event Viewer for ESE database error codes such as -501 or -1808 originating from ESENT.

Step-by-Step Fix:

1Stop Windows Update Service:

Open PowerShell as Administrator and run Stop-Service -Name wuauserv.

2Delete DataStore Directory Contents:

Remove-Item -Path "C:\Windows\SoftwareDistribution\DataStore\*" -Recurse -Force

3Restart Update Service:

Start-Service -Name wuauserv

4Run Update Troubleshooter:

Re-launch the built-in Windows Update troubleshooter.

Prevention & Long-Term Monitoring:

Prevent sudden power loss to safeguard database transaction integrity.

Repair and Re-register WMI Repository

Solution:

Root Cause: Windows Management Instrumentation (WMI) Repository Corruption

Windows Update troubleshooting tools rely heavily on WMI queries to inspect system state. A corrupted WMI repository leads to memory allocation failures and timeouts during diagnostic execution.

Diagnostic Verification:

Run winmgmt /verifyrepository in an administrative Command Prompt to check repository consistency.

Step-by-Step Fix:

1Stop WMI Service:

Open an administrative Command Prompt and run:

net stop winmgmt

2Verify Repository Consistency:

Run winmgmt /verifyrepository. If inconsistency is detected, proceed to step 3.

3Reset Repository:

Reset the repository using:

winmgmt /salvagerepository

4Restart System:

Reboot your computer to reinitialize WMI providers.

Prevention & Long-Term Monitoring:

Avoid force-killing WMI provider host processes (WmiPrvSE.exe) unless unresponsive.

Re-enable and Resize Windows Pagefile

Solution:

Root Cause: Disabled or Misconfigured Pagefile Settings

When users disable the Windows pagefile to save SSD write cycles or manually restrict its allocation size, memory-intensive update operations cannot allocate virtual address space, resulting in direct 0x8007000E out-of-memory exceptions.

Diagnostic Verification:

Run wmic pagefile list /format:list in Command Prompt to verify if allocation size is reported as zero or disabled.

Step-by-Step Fix:

1Open Advanced System Settings:

Press Windows + R, type sysdm.cpl, and navigate to Advanced > Performance Settings > Advanced > Virtual Memory > Change.

2Enable System Managed Size:

Uncheck "No paging file", select your primary system drive, and check System managed size.

3Set Initial and Maximum Size:

Alternatively, set Initial size to 4096 and Maximum size to 8192.

4Click Set and Reboot:

Click Set, then OK, and restart your system.

Prevention & Long-Term Monitoring:

Never completely disable the Windows pagefile, as numerous core OS subsystems depend on virtual memory mapping.

Identify and Update Faulty Non-Paged Pool Drivers

Solution:

Root Cause: Non-Paged Pool Memory Leak

Malfunctioning kernel-mode drivers (such as outdated network interface card or storage controller drivers) can leak non-paged pool memory, leaving insufficient kernel heap space for Windows Update operations.

Diagnostic Verification:

Open Task Manager > Performance tab > Memory, and check if Non-paged pool usage is abnormally high (e.g., several gigabytes).

Use PoolMon (poolmon.exe) from the Windows Driver Kit to isolate leaking pool tags.

Step-by-Step Fix:

1Identify Leaking Driver Tag:

Run PoolMon, sort by memory consumption (B key), and note the top tag.

2Update Network and Storage Drivers:

Open Device Manager (devmgmt.msc), expand Network Adapters and IDE ATA/ATAPI controllers, right-click your drivers, and select Update driver.

3Scan for Malware:

Run Windows Defender offline scan to ensure rootkits are not hooking kernel memory.

4Reboot System:

Restart the machine to clear kernel memory leaks.

Prevention & Long-Term Monitoring:

Regularly update hardware drivers directly from motherboard and component manufacturers.

Run Windows Memory Diagnostic Tool

Solution:

Root Cause: Physical RAM Hardware Instability or Addressing Faults

Faulty physical RAM modules or incorrect XMP/EXPO memory timings can cause memory address mapping errors, leading the operating system to prematurely report memory exhaustion or abort memory-intensive processes.

Diagnostic Verification:

Inspect Windows Event Viewer under System for WHEA-Logger event warnings indicating memory bus errors.

Step-by-Step Fix:

1Launch Memory Diagnostic Tool:

Press Windows + R, type mdsched.exe, and press Enter.

2Restart and Check for Problems:

Select "Restart now and check for problems (recommended)".

3Review Test Results:

After rebooting, check Event Viewer under System logs for source MemoryDiagnostics-Results to verify if hardware errors were detected.

4Reseat or Replace RAM:

If hardware faults are identified, reseat physical RAM sticks or test individual modules.

Prevention & Long-Term Monitoring:

Maintain stable memory voltage and conservative timings unless utilizing validated hardware overclocking profiles.

Increase Registry Size Limit and Clean Hive Bloat

Solution:

Root Cause: Registry Heap Limit Exhaustion

If the system registry grows excessively large due to orphaned installer keys or uncleaned application data, registry heap allocations hit operating system limits, causing update database transactions to fail with out-of-memory errors.

Diagnostic Verification:

Open System Properties > Advanced > Performance Settings > Advanced to check current virtual memory allocation and registry size thresholds.

Step-by-Step Fix:

1Open Registry Editor:

Press Windows + R, type regedit, and press Enter.

2Navigate to Memory Management Key:

Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.

3Verify Registry Size Limit:

Ensure RegistrySizeLimit (if present as a DWORD) is not restricted or set to an artificially low ceiling.

4Perform Registry Cleanup:

Use trusted maintenance tools to remove orphaned registry entries, and reboot your system.

Prevention & Long-Term Monitoring:

Avoid installing untrusted registry cleaner utilities that cause accidental hive corruption.

Related Diagnostic Guides

Windows Update Error 0x80070002 Missing Files Diagnostic Guide

System Restore Failed 0x80070005 Antivirus Conflict Tree

Windows Photo Viewer Not Showing Thumbnails: Codec Diagnostic

Safe Mode Password Not Working With Microsoft Account Fix

Clipboard History Not Working Windows 11: Sync Service Tree

Subscribe to StepDiag

Embed Guide on Your Website