Error 0x8007000E and Low-Memory Update Failures

30 Jul 2026

Windows Update downloads normally, begins installing and then stops with:

0x8007000E

You may also see messages such as:

Not enough memory resources are available
Not enough storage is available to complete this operation
The update failed to install
Windows could not complete the requested changes
The installation stopped unexpectedly

The wording is confusing because “memory” and “storage” can refer to several different resources.

The computer may have plenty of free SSD space but insufficient virtual memory. It may have enough physical RAM but a disabled or restricted paging file. Alternatively, the system drive may be so full that Windows cannot expand the paging file or extract the update.

Microsoft’s dedicated guidance for errors 0x8007000E and 0x800705AA says that, in most cases, the computer does not have enough available virtual memory to install the update. Common causes include third-party applications consuming excessive resources and paging-file settings that have been configured manually rather than being managed automatically.

The safest troubleshooting sequence is:

Check disk space, close resource-heavy applications, restore automatic virtual-memory management, restart and retry the update in a controlled environment.

What Does Error 0x8007000E Mean?

The underlying Windows error is associated with an out-of-memory or insufficient-resource condition.

Its traditional system description is:

Not enough storage is available to complete this operation.

In this context, “storage” does not necessarily mean that the SSD is full. It can describe the memory resources Windows needs to complete an operation. Microsoft’s current Windows Update guidance specifically links the code to insufficient virtual memory in many update failures.

The error can therefore involve:

Physical memory, or RAM
Virtual memory
The Windows paging file
Available system-drive space
Excessive memory consumption by applications or services
A manually restricted paging file
A Registry size restriction
A virtual machine with insufficient allocated resources
Windows servicing corruption

Do not assume that installing more RAM is the first or only solution.

RAM, Virtual Memory and Disk Space Are Different

Understanding the distinction prevents the wrong fix from being applied.

Physical memory

RAM is the high-speed working memory installed in the computer.

Windows, applications, drivers and update processes all use it while running.

A computer with 8GB of RAM may experience greater pressure during a large update when several browsers, Microsoft Teams, Outlook, OneDrive and security tools are also running.

Virtual memory

Virtual memory allows Windows to provide applications and system processes with a larger working address space than physical RAM alone.

Windows can move less-active memory data to a paging file on storage, freeing physical RAM for work that needs it immediately.

Paging file

The paging file is normally named:

pagefile.sys

It is usually stored on the Windows system drive and can grow or shrink according to the system’s requirements when Windows manages it automatically.

If the paging file has been:

Disabled
Given an extremely small fixed size
Moved to an unavailable drive
Restricted by an optimisation tool
Prevented from growing because the disk is full

Windows may be unable to obtain enough virtual memory for the update.

Disk space

Windows also needs free drive space to:

Download update packages
Extract compressed files
Create temporary working data
Update the component store
Preserve rollback information
Expand the paging file

Microsoft’s general Windows Update guidance categorises 0x8007000E among errors that can also appear when storage is insufficient. Its guidance recommends checking drive space as part of the investigation.

A low-memory update failure can therefore be caused by low disk space even when the update package itself appears relatively small.

Common Causes of 0x8007000E

Too many applications are open

Browsers with many tabs, Teams meetings, virtual machines, creative applications and large spreadsheets can consume substantial memory.

Windows Update then competes with those applications for available resources.

A background application has a memory leak

A faulty program or service may continually consume memory without releasing it.

Typical warning signs include:

Memory usage rising throughout the day
The PC working normally after restart
Performance deteriorating several hours later
One process growing to several gigabytes
The update succeeding only immediately after a restart

The paging file is disabled

Some performance guides recommend disabling the paging file on computers with large amounts of RAM.

That can reduce the resources available to Windows servicing and may also interfere with crash-dump collection and applications that expect virtual memory to be available.

The paging file is manually restricted

A fixed paging file that was adequate several years ago may no longer suit the current workload.

Microsoft’s specific guidance for 0x8007000E recommends ensuring that Automatically manage paging file size for all drives is selected.

The system drive is nearly full

Even with automatic management enabled, Windows cannot grow the paging file reliably when very little space remains.

The update also needs room for extraction and servicing.

Third-party security or utility software is consuming resources

Potential contributors include:

Third-party antivirus
Backup applications
Disk-management software
System-monitoring tools
Manufacturer utilities
Virtualisation software
Generic “PC optimisation” tools

Microsoft recommends using a clean boot when background applications or services may be consuming resources or interfering with the update.

The virtual machine is undersized

A Windows virtual machine may have been allocated too little:

RAM
Storage
CPU capacity
Paging-file space

Microsoft advises considering an increase to the virtual hardware allocation when the affected Windows installation is running as a VM.

A Registry size limit has been configured

An unusual legacy Registry value named:

RegistrySizeLimit

can restrict the maximum size of the Registry.

If the Registry reaches that limit, Windows may be unable to complete servicing operations. Microsoft says this should be investigated when the CBS log indicates a Registry-resource problem—not as a routine first fix.

Before You Begin

Before changing memory, update or Registry settings:

Back up important files.
Confirm that the backup can be opened.
Save the BitLocker recovery key.
Connect the computer to reliable mains power.
Record the failed update and error code.
Check the current Windows version with winver.
Record any custom paging-file settings before altering them.
Check whether the computer is managed by an employer or IT provider.

Microsoft recommends backing up personal files before working through Windows Update troubleshooting. Its targeted 0x8007000E guidance also advises backing up the operating-system disk before advanced remediation.

Step One: Identify the Failed Update

Open:

Settings > Windows Update > Update history

Find the failed entry and record:

KB number
Installation date
Update type
Error code
Whether a restart occurred
The percentage at which installation stopped

Then press:

Windows key + R

Enter:

winver

Record the Windows version and complete OS build.

A useful support record might look like:

Windows 11 Pro

Version: 25H2

OS build: 26200.xxxxx

Failed update: KB50xxxxx

Error: 0x8007000E

Failure point: 73% before restart

This confirms whether the issue involves one cumulative update, a feature update or several unrelated packages.

Step Two: Restart and Retry With Applications Closed

Select:

Start > Power > Restart

After Windows starts:

Do not reopen your normal applications.
Wait several minutes for startup activity to settle.
Close any programs that launch automatically.
Pause large OneDrive or backup transfers briefly.
Open Windows Update.
Retry the failed update once.

A restart can release memory held by:

Browser processes
Applications
Drivers
Security tools
Update processes
Services with memory leaks

If the update works immediately after restarting but fails later in the day, investigate a process whose memory use increases over time.

Do not repeatedly press Retry without changing the conditions. Each failed attempt can consume additional time, storage and servicing activity without resolving the resource shortage.

Step Three: Check Current Memory Pressure

Press:

Ctrl + Shift + Esc

Open:

Task Manager > Performance > Memory

Review:

Memory in use
Available memory
Committed memory
Cached memory
Paged pool
Non-paged pool

Then open the Processes page and select the Memory heading to sort applications by usage.

Look for:

A browser using several gigabytes
Multiple virtual machines
Teams or another communication application using excessive memory
A backup or security process growing continuously
Very little available memory
Committed memory approaching its displayed limit

Temporary high memory use is not necessarily a fault. The concern is sustained pressure or a process that keeps growing while idle.

Take screenshots before closing the suspected application. That evidence can help identify a leak or software problem later.

Step Four: Check Free Disk Space

Open:

Settings > System > Storage

Check the amount of free space on the Windows drive.

Microsoft’s generic upgrade guidance recommends at least 20GB of free space for a 64-bit operating-system upgrade. The exact requirement varies by update, Windows configuration and temporary servicing needs.

Avoid operating with only a few hundred megabytes or one or two gigabytes free.

Windows needs headroom for:

Temporary update files
Component servicing
Rollback information
Application caches
Virtual-memory growth
Recovery operations

Use Cleanup recommendations

Open:

Settings > System > Storage > Cleanup recommendations

Review the suggested categories and remove only items you understand.

Microsoft recommends Storage Sense and Cleanup recommendations for recovering space required by Windows Update.

Possible categories include:

Temporary files
Recycle Bin
Windows Update Cleanup
Delivery Optimisation files
Large or unused applications
Previous Windows installation files

Be cautious with:

Downloads
Previous Windows installations
Device-driver packages
Files required for troubleshooting

Deleting a previous Windows installation can remove the normal option for returning to the earlier Windows version.

External storage may help—but not with everything

Windows can sometimes use an external drive with at least 10GB of free capacity to complete an update when the internal device lacks enough installation space.

However, this does not necessarily correct an undersized or disabled paging file. Windows still needs adequate local resources to run the servicing process.

Step Five: Restore Automatic Paging-File Management

This is one of the most important checks for 0x8007000E.

Press:

Windows key + R

Enter:

sysdm.cpl

Then:

Open the Advanced tab.
Under Performance, select Settings.
Open the Advanced tab.
Under Virtual memory, select Change.
Select Automatically manage paging file size for all drives.
Select OK on each window.
Restart Windows.

Microsoft recommends this exact configuration for Windows Update errors 0x8007000E and 0x800705AA.

After restarting, return to the Virtual Memory window and confirm that the setting remains selected.

What if the page file was disabled?

Re-enable automatic management and restart.

Do not assume that a PC with 32GB or 64GB of RAM never needs a paging file. The update’s resource requirements and the system’s total committed workload still matter.

What if the page file is on another drive?

Automatic management is normally the safest starting point.

A paging file located only on a secondary drive can become unavailable if that drive:

Is removed
Fails
Starts late
Has insufficient free space
Uses unreliable external storage

Do not place a Windows paging file on a removable USB drive.

What if the setting changes back?

This may indicate:

Organisational policy
A management script
A third-party optimisation tool
Manufacturer software
An unsuccessful startup configuration

On a business computer, ask the IT provider to identify what is enforcing the setting rather than continually changing it locally.

Should You Set a Custom Paging-File Size?

For this specific Windows Update error, Microsoft’s current recommendation is to start with automatic management.

A separate Microsoft troubleshooting article describes a rare situation in which automatic page-file growth is too slow for applications allocating memory rapidly. In that specific case, a manually configured initial size may be used as a workaround. That is a specialised scenario and not a reason to apply arbitrary internet formulas to every PC.

Use a custom size only when:

Monitoring proves automatic growth is the problem.
A specialist workload has documented requirements.
An experienced technician has calculated the appropriate size.
Adequate disk space exists.
The change is recorded and reviewed.

Avoid selecting No paging file.

Step Six: Perform a Clean Boot

A clean boot starts Windows with essential Microsoft services and a restricted set of third-party startup programs.

It helps determine whether background software is consuming resources or interfering with the update.

Press:

Windows key + R

Enter:

msconfig

Then:

Open the Services tab.
Select Hide all Microsoft services.
Select Disable all.
Select Apply.
Open the Startup tab.
Select Open Task Manager.
Disable enabled startup applications.
Close Task Manager.
Select OK.
Restart Windows.
Retry the update.

Always select Hide all Microsoft services before disabling services.

Microsoft’s dedicated 0x8007000E guidance recommends a clean restart because antivirus software, utilities and other background applications can consume resources or interfere with installation.

The update installs successfully

A disabled third-party application or service was probably involved.

Re-enable items in small groups until the cause is identified.

Possible contributors include:

Third-party antivirus
Backup agents
Virtualisation software
Hardware-monitoring utilities
Disk tools
Manufacturer update utilities
Old VPN clients

The update still fails

Restore normal startup and continue with the next steps.

A clean boot is a diagnostic state, not a permanent operating configuration. Microsoft recommends returning Windows to normal startup after the test.

Step Seven: Run the Windows Update Troubleshooter

Open:

Settings > System > Troubleshoot > Other troubleshooters

Find Windows Update and select Run.

On current Windows 11 installations, the troubleshooting process may continue through the Get Help application.

Microsoft recommends starting with the automated Windows Update troubleshooter, which checks common update configuration and servicing issues.

Restart the computer after it completes.

Record anything the troubleshooter reports rather than simply closing the results window.

Step Eight: Repair Windows Components

If memory and storage settings appear correct but the update still fails, damaged Windows servicing components may be contributing.

Open Terminal or Command Prompt as administrator.

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Allow the process to finish.

Then run:

sfc /scannow

Restart Windows afterwards.

Microsoft recommends using DISM and System File Checker to repair missing or damaged Windows components and protected system files.

DISM also reports insufficient resources

Stop and recheck:

Free drive space
Paging-file configuration
Available memory
Background applications
Storage health

DISM itself requires working memory and temporary storage. Running it repeatedly without addressing the resource problem is unlikely to help.

DISM completes successfully

Run SFC, restart and retry Windows Update once.

SFC repairs files

Restart again before attempting the update.

Corruption cannot be repaired

The computer may require:

A matching Windows repair source
A repair reinstall
Storage diagnostics
Professional servicing-log analysis

Step Nine: Check the CBS Log

Windows servicing records update-installation activity in:

C:\Windows\Logs\CBS\CBS.log

Microsoft identifies CBS.log as a key source for understanding the servicing-stack portion of Windows Update installation.

Search the recent entries for:

0x8007000e

and:

0x800705aa

Also look for phrases involving:

Memory
Resources
Registry
DPX
Failed to create file
Failed to allocate
Transaction state

Do not assume every line containing “Error” is the root cause. Windows servicing logs can contain warnings and recovered errors that are not responsible for the final failure.

The most useful entry is normally close to the timestamp at which installation stopped.

CBS.log may contain:

Package names
Windows paths
Computer information
Servicing details

Review it before sharing it publicly.

Step Ten: Check RegistrySizeLimit Only When the Log Supports It

This is an advanced step.

Do not create, delete or modify RegistrySizeLimit merely because the error code appeared.

Microsoft says this value should be investigated when CBS.log indicates that Registry resources are involved. A non-zero value can cap the Registry’s maximum size and prevent Windows from performing required servicing operations after that limit is reached.

The location is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

The value is:

RegistrySizeLimit

Microsoft’s documented correction is to delete the value or set it to 0, followed by a restart. It also warns that incorrect Registry changes can cause serious problems and recommends backing up the Registry first.

For a business PC, server or virtual machine, have an experienced administrator confirm the CBS evidence and make the change.

Do not run generic Registry cleaners. They can remove or alter settings unrelated to the update and make servicing harder to diagnose.

Step Eleven: Check for a Memory Leak

If the update repeatedly fails only after the computer has been running for several hours, monitor memory over time.

Open Task Manager and record the largest processes at intervals.

For example:

9:00am Application A: 600MB

11:00am Application A: 1.8GB

1:00pm Application A: 4.4GB

3:00pm Application A: 7.9GB

That pattern may indicate a leak.

Try:

Updating the application.
Repairing or reinstalling it.
Disabling related extensions.
Restarting the associated service.
Testing the update with the application closed.
Contacting the software vendor.

Adding RAM may delay the failure but will not necessarily correct an application that continues consuming memory indefinitely.

Step Twelve: Consider Whether the PC Needs More RAM

A RAM upgrade may be justified when:

The PC has only 4GB or 8GB.
Normal office use consistently leaves very little available memory.
The machine performs heavy multitasking.
Teams, browsers and business applications must remain open.
Paging is excessive even after software issues are corrected.
The hardware supports an upgrade.
The update succeeds only after almost every application is closed.

Do not upgrade RAM before checking:

Paging-file configuration
Memory leaks
Disk space
Storage health
Unnecessary startup software

A properly configured computer with modest RAM may still update successfully, while a machine with substantial RAM can fail if its paging file has been disabled or restricted.

Virtual Machines Need Separate Resource Checks

For a Windows VM, review:

Assigned RAM
Dynamic-memory minimum and maximum
Available host memory
System-drive capacity
Paging-file settings inside the guest
Snapshot or checkpoint storage
Host storage performance
Concurrent VM workloads

Microsoft advises increasing the virtual hardware resources when an affected VM does not have enough memory available for servicing.

Be cautious with dynamic memory.

A VM may show a high maximum allocation but still receive too little memory at the moment the update runs because the host is under pressure.

Back up or checkpoint the VM using your platform’s approved procedure before changing its resources.

When Low Disk Space Is the Real Cause

The problem is more likely to be storage-related when:

The Windows drive is nearly full.
Temporary files consume several gigabytes.
The paging file cannot grow.
Windows Update displays a storage warning.
CBS.log shows failures creating or extracting files.
Several updates fail with different codes.
Windows becomes unstable during normal file operations.

Use:

Storage Sense
Cleanup recommendations
Disk Cleanup
OneDrive Files On-Demand
Application removal
Moving personal data to appropriate storage

Do not manually delete content from:

C:\Windows\WinSxS

C:\Windows\Installer

C:\Windows\servicing

These are managed Windows servicing locations.

Common Mistakes to Avoid

Assuming the message always means the SSD is full

Microsoft’s targeted guidance identifies insufficient virtual memory as the most common cause of this update error.

Buying RAM immediately

Check the paging file, background applications and memory leaks first.

Disabling the paging file

This reduces the virtual-memory resources available to Windows and can interfere with updates.

Setting an arbitrary page-file value

The correct starting point is automatic management, not a value copied from a general optimisation guide.

Using a “RAM cleaner”

These tools do not create additional physical memory and may simply force useful data out of RAM, increasing paging and storage activity.

Running a Registry cleaner

The RegistrySizeLimit issue requires a specific diagnosis from servicing logs—not a broad Registry cleanup.

Repeatedly retrying the update

A resource shortage will normally return until the cause changes.

Deleting Windows servicing folders

Manual removal can damage future updates and recovery functions.

Leaving Windows in clean-boot mode

Restore normal startup after the conflict test.

Ignoring storage health

Repeated corruption, freezing or write failures can indicate a failing SSD rather than a routine memory problem.

A Practical 0x8007000E Checklist

When Windows Update fails with 0x8007000E:

Record the failed KB number.
Run winver.
Back up important files.
Restart Windows.
Retry with applications closed.
Check Task Manager memory usage.
Identify unusually large or growing processes.
Check free space on the Windows drive.
Use Cleanup recommendations.
Confirm that the paging file has not been disabled.
Select automatic paging-file management.
Restart Windows.
Perform a clean boot.
Retry the update once.
Run the Windows Update troubleshooter.
Run DISM.
Run SFC.
Review CBS.log.
Check RegistrySizeLimit only when the log identifies a Registry-resource issue.
Increase VM resources where applicable.
Investigate memory leaks.
Test storage health if failures continue.
Consider a RAM upgrade only after configuration and software causes are excluded.
Escalate persistent business-device failures to the IT provider.

How Hamilton Group Can Help

Error 0x8007000E can look like a simple low-memory message, but the underlying cause may involve RAM, virtual memory, disk space, Windows servicing or a third-party application.

Hamilton Group’s experienced IT team can identify which resource is actually being exhausted.

Memory and Process Analysis

We can examine:

Physical memory use
Available and committed memory
Paging-file configuration
Memory leaks
Paged and non-paged pools
Resource-heavy applications and services

Windows Update Diagnosis

Hamilton Group can identify:

Failed KB numbers
Installation stages
Servicing errors
CBS.log entries
Repeated update failures
Windows build and component-store problems

Virtual-Memory Repair

We can correct:

Disabled paging files
Unsuitable fixed sizes
Paging files on unavailable drives
Management tools overriding Windows settings
Resource shortages affecting virtual machines

Windows Servicing Repair

Our engineers can run and interpret:

Windows Update diagnostics
DISM
SFC
CBS logs
Component-store checks
Repair reinstalls where appropriate

Hardware and Storage Assessment

Where the computer genuinely lacks capacity, we can:

Check RAM-upgrade compatibility
Supply and install suitable memory
Test the SSD
Upgrade an undersized system drive
Review virtual-machine allocation
Confirm that the update completes successfully

Business-Wide Remediation

When multiple computers fail with the same error, Hamilton Group can determine whether the cause involves:

A shared application
Endpoint-security software
A standardised paging-file policy
An Intune or Group Policy configuration
A particular hardware model
An undersized virtual-desktop template

We aim to make first contact on IT support requests within 15 minutes, helping businesses restore secure Windows updating before failed patches create a wider security gap.

Fix the Resource Shortage, Not Just the Error Message

Error 0x8007000E does not automatically mean that the PC needs more physical RAM.

In many Windows Update cases, the actual problem is insufficient virtual memory caused by a disabled or restricted paging file, excessive background resource use or inadequate free space for that paging file to grow.

Start by:

Restarting Windows

Closing heavy applications

Checking drive space

Restoring automatic paging-file management

Then retry the update in a clean environment.

Call 0330 043 0069, book a meeting with one of our experts or visit hgmssp.com for experienced help with Windows Update failures, virtual memory and computer performance.

Previous Next