Pre-Installation Issues
This guide covers common errors encountered during the installation process.Extraction Errors
Problem
Cannot extract files from the .7z or .zip archives for WSA Builds.Solution
Install Script Errors
Problem: Install.ps1 not recognized or found
Files appear to be missing from the folder, or PowerShell cannot findInstall.ps1.
Solution
Rename the folder
Rename the extracted folder to a shorter name:
- Before:
WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon - After:
WSA
Open PowerShell as Admin
Press
Win + X and select:- Windows 11: “Windows Terminal (Admin)”
- Windows 10: “PowerShell (Admin)”
Path Too Long
Problem
Error stating “Path is too long” when extracting or installing.Solution
Rename the archive file
Rename the .zip/.7z file to a shorter name:
- Before:
WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon.7z - After:
WSA.7z
Error Codes
Error 0x80073CF0
Cause: File corruption, long folder names, or incorrect file system. Solution:Redownload the build
Download a fresh copy from the releases page.
Rename archive and folder
Use short names for both the archive file and extracted folder (e.g.,
WSA).Error 0x80073CF6
Cause: Package could not be registered - multiple possible causes.This error is common on modified Windows OSes such as ReviOS, Tiny10/11, etc., which have removed features needed for WSA.
Clean previous installation
Delete all folders containing “WindowsSubsystemForAndroid” from:
C:\ProgramData\Microsoft\Windows\AppRepositoryC:\ProgramData\Microsoft\Windows\WindowsApps%localappdata%\Packages
Error 0x800706D9 - No endpoints available
Error 0x800706D9 - No endpoints available
Cause: Firewall issues preventing package registration.Solution:
- Ensure Windows Firewall is enabled with “Recommended Settings”
- Verify Windows Firewall service is running
- Ensure your firewall isn’t blocking new entries
- Restart your PC
Error 0x80073B06 - Initial screen image not recognized
Error 0x80073B06 - Initial screen image not recognized
Solution:
- If building yourself, delete previous builds and rebuild from a fresh git clone
- If using prebuilt releases, redownload the latest build
- Report to Discord if issue persists
Error 0x80073CF9
Cause: Similar to 0x80073CF0 - file corruption or long paths. Solution: Follow the same steps as Error 0x80073CF0.Error 0x80073CFB
Cause: Package is already installed and reinstallation was blocked. Solution:Error 0x80073CFD
Cause: Windows 10 build is too old to run WSA.Error 0x80073D10
Refer to the source documentation for this specific error.Error 0x80073B17
Refer to the NamedResource Not Found guide.Appx Module Cannot Be Loaded
Problem
This issue mainly occurs on LTSC and non-official builds of Windows.
Solution
Open PowerShell as Administrator and run:Need More Help?
Join Discord
Get help from the community
Open Issue
Report bugs on GitHub
