Fix Error 0x800700b7 0x2000a: Windows Update

Error 0x800700b7 0x2000a occurs when Windows Update or a component store operation fails because another process is already using the required files or services. The fix is to stop the Windows Update service, clear the SoftwareDistribution folder, and restart the service—this resolves the majority of cases in a few minutes.

What This Error Means

The hexadecimal code 0x800700b7 translates to “ERROR_ALREADY_EXISTS” in the Windows error table. When combined with 0x2000a, it typically appears during Windows Update, Microsoft Store app installations, or when using the DISM (Deployment Imaging Service and Management) tool. The system is telling you that a file, registry key, or service it needs to modify is currently locked by another process. This is often a leftover from a previous update attempt, a third-party antivirus scanning the update files, or a corrupted update cache.

Why It Happens

The most common trigger is a stalled Windows Update session. When an update is interrupted—by a forced shutdown, a network drop, or a system crash—the update service may leave behind temporary files in the C:\Windows\SoftwareDistribution folder. On the next attempt, Windows tries to create new files in that folder but finds the old ones still locked. The same error can appear if you run multiple update tools simultaneously, such as starting DISM while Windows Update is already working, or if a third-party security suite holds the update files open for scanning.

How to Fix It (Step-by-Step)

Follow these steps in order. You will need an administrator account. If a step fails, continue to the next one—the error is often resolved by a combination of actions.

Stop the Windows Update service. Press Win + R, type services.msc, and press Enter. Find “Windows Update” in the list, right-click it, and select Stop. Leave the Services window open.
Clear the update cache. Open File Explorer and navigate to C:\Windows\SoftwareDistribution. Delete everything inside this folder. If a file is in use, you may need to restart in Safe Mode or use the command line method below.
Restart the service. Go back to Services, right-click “Windows Update” again, and select Start.
Run the Windows Update troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters, and run “Windows Update”. This automates several checks and repairs common issues.
Use DISM and SFC. If the error persists, open Command Prompt as administrator and run:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

These commands repair corrupted system files that might be causing the lock. Restart your PC after they finish.

Command Line Alternative

If the Services window method fails because the service won’t stop, use an elevated Command Prompt (Run as administrator) and enter these commands one by one:

net stop wuauserv
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start bits

The ren command renames the entire folder instead of deleting it, which works even if some files are locked. Windows will create a fresh SoftwareDistribution folder on the next update attempt. You can delete the .old folder later once you confirm everything works.

What to Do If the Error Persists

If you still see 0x800700b7 0x2000a after clearing the cache and running DISM, the cause is likely a third-party antivirus or a corrupted Windows Update component. Temporarily disable your antivirus real-time protection (not just the firewall) and try the update again. If that works, add an exception for the C:\Windows\SoftwareDistribution folder in your antivirus settings. Another possibility is a pending reboot—Windows may have installed a partial update that requires a restart to release file locks. Restart your PC twice if needed.

Common Mistakes to Avoid

Deleting the SoftwareDistribution folder while the service is running. This almost always fails or causes new errors. Always stop the service first.
Skipping the DISM step. Many users jump straight to SFC, but DISM repairs the component store that SFC relies on. Run DISM first.
Ignoring disk space. A full system drive (especially the C: drive) can cause update failures with this error. Ensure you have at least 20 GB free for major updates.
Using third-party “cleaner” tools. These often remove update files incorrectly and can make the problem worse. Stick to built-in Windows tools.

Frequently Asked Questions

Will this error damage my computer?

No. Error 0x800700b7 is a temporary file-lock issue, not a hardware or data failure. Your files are safe. It simply prevents updates from installing until the lock is cleared.

Can I ignore this error and keep using my PC?

You can, but your system will not receive security updates, leaving you vulnerable to known exploits. It is best to resolve the error promptly, especially if it appears during a critical security patch.

Why does this happen after a forced shutdown?

A forced shutdown interrupts the update process mid-write. Windows leaves behind partially written files and marks them as “in use” to prevent corruption. On the next boot, the update service tries to reuse those files and fails because the handles are stale.

Do I need to reinstall Windows to fix this?

Almost never. The steps above resolve the issue in the vast majority of cases. Reinstalling Windows is a last resort if the component store is severely corrupted and DISM cannot repair it, but that is rare.

Is this error related to error 0x800700b7 alone?

Yes. The 0x2000a suffix is a sub-code that Windows Update adds to indicate the specific component that failed. The underlying cause—a file or service already in use—is the same, so the fixes are identical.

How do I prevent this from happening again?

Always allow updates to finish before shutting down, keep at least 20 GB of free space on your system drive, and avoid running multiple update tools at the same time. If you use third-party antivirus, configure it to exclude the Windows Update folders.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →