0x800700b7 Error Downloading Windows Subsystem for Android

Error code 0x800700b7 during a Windows Subsystem for Android (WSA) download means Windows Update or the Microsoft Store blocked the installation because a required file is already in use or a previous update is still pending. The fix is to clear the SoftwareDistribution cache, restart the Windows Update service, and then retry the download; if that fails, a clean reinstall of the WSA package usually resolves it.

What This Error Actually Means

The 0x800700b7 code translates to ERROR_ALREADY_EXISTS — Windows is telling you that the file or folder it needs to write already exists and cannot be overwritten. In the context of WSA, this almost always happens when:

A previous WSA download or update was interrupted, leaving a partial file locked.
Another Windows Update process is running in the background and holding the same cache files.
Antivirus or security software is scanning the download folder at the same time.
The Windows Update service (wuauserv) is stuck in a bad state.

This is not a hardware problem or a sign that your PC is incompatible. It is a file-locking conflict that can be cleared with a few administrative commands.

Why WSA Downloads Are Prone to This Error

Windows Subsystem for Android is not a typical app. It is a virtual machine package that installs through the Microsoft Store and Windows Update pipeline. The download is split into multiple large files (often over 1 GB), and each file must be written to a specific location under C:\Program Files\WindowsApps. Because that folder is heavily protected and shared with other system components, any lingering lock from a previous attempt will trigger 0x800700b7.

Additionally, WSA requires the Windows Hypervisor Platform and Virtual Machine Platform features to be enabled. If you enabled those features after starting the download, Windows may try to reinitialize the virtual machine while the old files are still present, causing the same error.

Step-by-Step Fix for 0x800700b7

Work through these steps in order. Stop after each one and try the download again — you may not need all of them.

Restart your PC. This releases any temporary file locks held by background processes. It is the simplest fix and works more often than you would expect.
Stop the Windows Update service. Open Command Prompt as Administrator and run:
```
net stop wuauserv
net stop bits
```
(BITS is the Background Intelligent Transfer Service, which handles large downloads.)
Clear the SoftwareDistribution cache. In the same Command Prompt, run:
```
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
```
This renames the folders where Windows stores update files. The system will recreate them fresh on the next start.
Restart the services. Run:
```
net start wuauserv
net start bits
```
Then close the Command Prompt and retry the WSA download from the Microsoft Store.
If it still fails, reinstall WSA manually. Open PowerShell as Administrator and run:
```
Get-AppxPackage *WindowsSubsystemForAndroid* | Remove-AppxPackage
```
Then restart your PC and download WSA again from its Microsoft Store page.

What to Try If the Basic Fix Fails

If the error persists after clearing the cache, the problem may be deeper. Try these additional steps:

Run the Windows Update troubleshooter. Go to Settings → System → Troubleshoot → Other troubleshooters → Windows Update. This will automatically detect and fix common service issues.
Check disk space. WSA needs about 8 GB of free space. If your drive is nearly full, the download may fail with this error because the temporary file cannot be expanded. Free up space and retry.
Temporarily disable third-party antivirus. Some security suites lock newly downloaded executables for scanning. Disable real-time protection for a few minutes, then retry. Re-enable it immediately after.
Reset the Microsoft Store cache. Press Win + R, type wsreset.exe, and press Enter. This clears the Store’s own cache without affecting your installed apps.
Check for pending Windows updates. If a regular Windows update is stuck at “pending restart,� it can block WSA. Install all pending updates, restart, then try WSA again.

Preventing the Error in Future Downloads

Once you have WSA installed, you can reduce the chance of seeing 0x800700b7 again when updates arrive:

Do not interrupt downloads. Let the Microsoft Store and Windows Update finish completely. If you must pause, wait at least a minute before resuming.
Keep Windows Update healthy. Run the Windows Update troubleshooter monthly or whenever updates seem slow.
Leave the Windows Update service set to Automatic. If you or a tool disabled it to speed up boot times, re-enable it.
Do not manually delete files from the SoftwareDistribution folder. Always use the rename method shown above, and only when the service is stopped.

Common Misconception: It Means Your PC Is Too Old

Many users assume 0x800700b7 is a hardware compatibility error. It is not. WSA requires a 64-bit CPU, 8 GB RAM, and SSD storage, but the error code itself is purely a file-locking issue. If your PC meets the minimum requirements for Windows 11, it can run WSA. The error appears just as often on high-end gaming PCs as on budget laptops — it is a software conflict, not a hardware limitation.

Frequently Asked Questions

Will uninstalling and reinstalling WSA delete my Android apps?

Yes. Removing the WSA package removes all Android apps you installed through it, along with their data. If you have apps with important data, back them up first. The reinstall itself will not affect your Windows files or other programs.

Can I download WSA from a third-party website to avoid this error?

It is not recommended. WSA is distributed through the Microsoft Store, and sideloading it from unofficial sources can expose you to modified or malicious packages. The error is fixable, so there is no reason to risk your system’s security.

Why does the error appear even after I cleared the cache?

Clearing the SoftwareDistribution cache only fixes the download cache. If the error persists, the lock is likely coming from a different source — a running antivirus, a pending restart, or a corrupted Windows Update component. Try the additional steps in the section above, especially the Windows Update troubleshooter.

Does this error affect other Microsoft Store apps?

It can. The same file-locking mechanism applies to any large download that uses the Windows Update pipeline. If you see 0x800700b7 for another app, the same cache-clearing steps will usually fix it.

Is there a way to download WSA without the Microsoft Store?

For current versions of Windows 11, the official method is the Microsoft Store. Microsoft has not provided an official standalone installer. If you are on Windows 10, WSA is not officially supported at all, so the Store page may not even appear.

How long should I wait after restarting before retrying?

Wait until Windows fully loads and the disk activity settles — usually 2 to 3 minutes after the desktop appears. If you have startup programs, give them a moment to finish. Then open the Store and retry. Do not immediately retry while background processes are still starting.

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 →