error code 8007000e - then changes to 80860010

The error code 8007000e typically indicates that there is insufficient virtual memory available to complete the operation. Although you have 32GB of RAM, the issue may not be related to the physical memory itself but rather to the virtual memory settings or other applications consuming virtual memory resources.

To troubleshoot this issue, you can try the following steps:

1. Configure Virtual Memory Settings: Ensure that your system is set to automatically manage virtual memory. You can do this by:
   • Pressing Windows + R, typing sysdm.cpl, and hitting Enter.
   • In the System Properties window, go to the Advanced tab and click on Settings under the Performance section.
   • In the Performance Options window, go to the Advanced tab and click on Change under Virtual memory.
   • Make sure that Automatically manage paging file size for all drives is selected, then click OK and restart your computer.
2. Perform a Clean Boot: A clean boot can help eliminate software conflicts that may be causing the issue. To perform a clean boot:
   • Sign in as an administrator.
   • Type msconfig in the Search box and select System Configuration.
   • In the Services tab, check Hide all Microsoft services and then click Disable all.
   • Go to the Startup tab and click Open Task Manager. Disable all startup items.
   • Close Task Manager, go back to System Configuration, click OK, and restart your computer.
3. Check for Third-Party Applications: Sometimes, third-party applications can consume a lot of virtual memory. Try disabling or uninstalling any unnecessary applications to see if that resolves the issue.

If these steps do not resolve the problem, you may want to consider contacting Microsoft Support for further assistance, as they can provide more specific guidance based on your situation.

References:

• Troubleshoot Windows Update error code 0x8007000e or 0x800705aa

Hi Fred,

The codes 8007000E and 80860010 often appear when Windows encounters a corrupted sign-in component or damaged authentication cache, not necessarily a lack of physical memory. Even though the first code points to a “memory error,” in most cases it actually means that Windows can’t properly load the Microsoft Account Sign-in service or one of its background processes has missing or outdated data.

Over time or after major updates or resets the system’s Microsoft AAD Broker Plugin or Sign-in Assistant can fail to refresh stored credentials. This prevents your device from verifying your Microsoft account correctly, which then causes the loop of sign-in failures and alternating error codes.

Try these steps

Reset the Sign-in Cache

Sign out of your Microsoft account on the PC.

Open File Explorer and navigate to:

C:\Users<YourUserName>\AppData\Local\Packages

Find and delete the folder:

Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

Restart the computer and sign back in.

This rebuilds your local Microsoft authentication data.

Repair System Files Open Command Prompt (Admin) and run these commands one by one:

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

Restart your PC after both finish. These commands scan and repair system files that can interfere with account sign-ins.

Ensure Services Are Running Press Win + R, type services.msc, and make sure these are Running and set to Automatic:

Microsoft Account Sign-in Assistant

Windows Update

Cryptographic Services Restart them if they’re stopped.

Test with a New Local Account Create a temporary local user, then link it to your Microsoft account. If this works, the issue lies in your original profile’s registry or cache and you can migrate your files safely afterward.

If the same problem continues even on a new profile, it might be linked to an outdated Windows build or an authentication mismatch with Microsoft’s servers. In that case, I recommend checking for optional updates or reaching out to Microsoft Support so they can refresh the account token from their end.

Let me know how it goes, Happy to help!