How to Fix Error 0x8007000e

Quick Fix

Try this first (under a minute):

1. Restart your PC to clear out memory and reset background services.
2. Free up disk space (aim for at least a few GB free on your system drive) by emptying the Recycle Bin or running Disk Cleanup.
3. Try the action again (install the update, sign in, or install the app).

If it still fails, run the built-in Windows Update Troubleshooter or Store troubleshooter before moving to deeper fixes below.

Step-by-Step Guide

What Error 0x8007000e Means

0x8007000e is a Windows HRESULT code that maps to ERROR_OUTOFMEMORY / E_OUTOFMEMORY. The symbol ERROR_OUTOFMEMORY or E_OUTOFMEMORY means “Not enough storage is available to complete this operation” or “Ran out of memory.” Despite the name, it rarely means your RAM is literally full — this error is one of the most misleading Windows errors, and it gets thrown when services can’t allocate resources, which often means a dependency failed rather than actual memory exhaustion.

You’ll typically see this code in three different situations, and the fix differs slightly for each:

1. Windows Update / Feature Update fails with a message like “Installer encountered an error 0x8007000e.” Not enough memory resources available to complete this operation.
2. Microsoft Store, Xbox app, or Xbox Game Bar sign-in fails — often tied to account/authentication issues rather than memory.
3. An Xbox console shows it while installing a disc-based or downloaded game.

Below is a complete, ordered troubleshooting path — from quick to advanced.

Step-by-Step Fixes

1. Restart and free up resources

Close unnecessary programs and browser tabs, then restart your PC. Close unused applications and background tasks, then restart the system and try the update again. This clears any temporary memory pressure or stuck processes causing the error.

2. Check and free disk space

Launch the built-in Disk Cleanup utility to get rid of accrued temporary files — this is commonly triggered when the usable memory on the system has been exhausted or the available disk space is insufficient. Open the Start menu, type “Disk Cleanup,” select your system drive (usually C:), and remove temporary files, system error memory dumps, and other unneeded files. Also uninstall apps you no longer use via Settings > Apps.

3. Run the Windows Update Troubleshooter (Windows-specific)

Open the Settings app and navigate to Update & Security > Troubleshooter, select Windows Update from the panel, and click Run Troubleshooter. On newer Windows 11 builds this lives under Settings > System > Troubleshoot > Other troubleshooters. Let it apply any automatic fixes, then retry the update.

4. Rename the SoftwareDistribution and Catroot2 folders (for update errors)

These folders can become corrupted and block updates. To reset the catroot2 folder, first stop related Windows services: in an elevated Command Prompt, run net stop cryptsvc, net stop bits, net stop wuauserv, and net stop msiserver. Then rename the folders — type the following command and press Enter to execute it: ren %systemroot%SoftwareDistribution softwaredistribution.old — and similarly rename the Catroot2 folder in C:WindowsSystem32catroot2. Restart the renamed services with net start bits, net start wuauserv, net start cryptsvc, and net start msiserver, then restart your PC and check for updates again. Windows will automatically recreate fresh versions of these folders.

5. Run System File Checker and DISM

Corrupted system files are a common cause. Right-click Start and open Command Prompt (Admin), type sfc /scannow and press Enter, then wait for the procedure to end and reboot your PC. If SFC reports it couldn’t fix everything, follow up with DISM /Online /Cleanup-Image /CheckHealth, DISM /Online /Cleanup-Image /ScanHealth, and DISM /Online /Cleanup-Image /RestoreHealth, then try updating again.

6. Check the Windows Update service itself

This error is possible to happen if your Windows Update service is disabled, in which case you need to enable it. Press Win + R, type services.msc, find Windows Update, double-click it, set Startup type to Automatic, and click Start if it’s stopped.

7. If it happens signing into Microsoft Store, Xbox app, or Xbox Game Bar (account-related)

This variant is usually not a memory problem at all. According to information from other users, this error code seems to be related to account authentication, and changing the account to a local account seems to help. Try these in order:

1. Reset the Store cache: press Win + R, type wsreset.exe, and press Enter, then try signing in again.
2. Re-register Store apps via PowerShell (Admin): Get-AppxPackage -allusers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”}
3. Uninstall and reinstall the Xbox app from Settings > Apps.
4. As a last resort, create a new local Windows account and migrate your files/settings, then sign back in with your Microsoft account under that new profile — this has resolved persistent sign-in versions of this error for many users, especially after hardware changes like a motherboard swap.

8. If it happens on an Xbox console (console-specific)

On an Xbox console, this error might occur while installing pending updates, installing new apps from the Microsoft Store, or playing games. Try: cancel and restart the download/install from My games & apps > Queue; power-cycle the console; if using a disc, eject it, power-cycle, and reinsert it; and check Xbox Live service status in case servers are down. As a last resort, use Settings > System > Console info > Reset console with “Keep my games & apps” enabled.

9. Advanced: DISM/CBS log analysis for IT admins

If you manage a fleet of PCs or a server, check the CBS.log for registry size issues. If the CBS log indicates the issue involved registry resources, the RegistrySizeLimit registry entry may be set to a value other than 0, which restricts the registry’s maximum size and can prevent Windows from performing update servicing. A clean boot can also help: a clean boot starts Windows without background applications and services that could interfere with the update process.

10. When to seek different help

If none of the above resolves it, escalate as follows:

1. Persistent Windows Update failures: if the issue persists after trying again, contact Microsoft Support for more assistance and attach copies of any relevant CBS.log data to your support request. As a fallback, use the Media Creation Tool or Windows Update Assistant to perform an in-place upgrade without losing files.
2. Account/sign-in loops that survive a local-account switch: this may indicate account corruption on Microsoft’s end — contact Xbox/Microsoft Account support directly rather than continuing to troubleshoot locally.
3. Repeated failures after a hardware change (e.g., new motherboard/CPU) tied to Store or Xbox sign-in: this is often a licensing/activation quirk on Microsoft’s servers tied to your device ID — Microsoft support can manually reset the device association.
4. Genuine low-RAM systems (very old or resource-constrained PCs) repeatedly hitting true out-of-memory conditions: consider a RAM upgrade or increasing your page file size, since if your device consistently runs low on memory, upgrading physical RAM or using ReadyBoost with a USB drive can help.

Platform notes: Steps 3, 4, and 6 are Windows-only (Settings paths differ slightly between Windows 10 and 11). Step 7 applies to Microsoft Store/Xbox app on Windows. Step 8 is Xbox console-specific and does not apply to PC. This error code is not native to macOS, though third-party apps that emulate Windows error handling (rare) could theoretically surface it.