File: README.md Copy Chapter

[!IMPORTANT]

IF YOU HAVE BEEN RECENTLY HAVING ISSUES WITH SOME APPS BREAKING OR NOT STARTING OR APPS GETTING SUCK AT LOADING SCREEN OR APPS STUCK ON SPLASHSCREEN ( STUCK ON THE APP ICON SCREEN) OR ANY OTHER SIMILAR CASES AFTER THE `1ST OF SEPTEMBER 2026`.UPDATE TO THE LATEST LTS RELEASE!

CLICK HERE FOR MORE INFORMATION

---

USE THE LINKS BELOW AND UPDATE TO THE LATEST LTS RELEASE: Copy Section

• LTS Releases: Copy Section

  • Windows 11 x64
  • Windows 10 x64

If some apps that worked before, still refuse to work after updating, try clearing the app data and cache or reinstalling the apps. If the issue still occurs, you may need to perform a clean install to fix some apps. Create a backup before proceeding.

LET ME KNOW VIA GITHUB ISSUES AND/OR THE WSA COMMUNITY DISCORD IF THESE RELEASES HAVE SOLVED YOUR ISSUE. THANK YOU.

[!CAUTION]

Hello. Before you proceed to install WSA, it is important to note that WSA has been having some issues for the past year, where GApps builds have begun crashing on all Windows 11 builds after June 2025.

Fixes and upgrades are being worked on to resolve all bugs and crashes (in the form of https://github.com/MustardChef/WSABuilds/issues/700).

If you are affecting by this issue, try these current workarounds in the meantime:

RECOMMENDED FIX FOR BUILDS CONTAINING GAPPS (Google Play Store and Services): https://github.com/MustardChef/WSABuilds/issues/593#issuecomment-3172749449

OR

Switch/Use the builds which do not contain GApps. These are the builds that contain `NoGApps` in their .7z archive names.

Really old builds of WSA (2211/2210) are known to be working.

Visit https://github.com/MustardChef/WSABuilds/issues/593 for updates and discussions regarding the issue.

[!TIP]

To view the bugfixes and improvements that are currently being worked on, and the current state of the WSABuilds project, [refer to the corresponding project page](https://github.com/users/MustardChef/projects/5) Copy Chapter

Downloads

Requirements

[!TIP]

WSA End Of Support (EoS) Information (Click Here)

"Microsoft is ending support for the Windows Subsystem for Android™️ (WSA). As a result, the Amazon Appstore on Windows and all applications and games dependent on WSA will no longer be supported beginning March 5, 2025." Copy Chapter

(Source: [GitHub](https://github.com/microsoft/WSA/discussions/536) and [Microsoft Learn](https://learn.microsoft.com/en-us/windows/android/wsa/))

---

WSABuilds has entered LTS (Long Term Support) for WSA versions ≥ 2311.40000.5.0, where the Magisk version, KernelSU version and GApps version will be kept up to date via new releases. Copy Section

This repo will not be archived and support will still be given to any users installing WSA Builds from this repo. Thank you all for using this repository and supporting my work, its been a pleasure serving this community. Copy Section

Do make sure that you keep a look out for any updates to this repo to be notified of any futher changes to WSA and WSABuilds Copy Section

---

Next LTS and Non-LTS Release Date: (Click Here)

WSABuilds LTS 8 Hotfix (v2407.40000.4.0) Copy Section

Friday 4th September 2026 Available Now (via the both Stable and Pre-release buttons in Downloads)

WSABuilds LTS 7 Hotfix (v2407.40000.4.0) Copy Section

Sunday 4th January 2026 Available Now (via the both Stable and Pre-release buttons in Downloads)

Non-LTS Build Update (v2407.40000.4.0_v2): Copy Section

Monday 2nd June 2025 Available Now (via the Stable release buttons in Downloads)

WSABuilds LTS 7 (v2407.40000.4.0) Copy Section

Monday 2nd June 2025 Available Now (via the Pre-release buttons in Downloads)

Non-LTS Build Update (v2407.40000.4.0): Copy Section

Monday 9th December 2024 Available Now (via the Stable release buttons in Downloads)

WSABuilds LTS 6 (v2407.40000.4.0) Copy Section

Monday 9th December 2024 Available Now (via the Pre-release buttons in Downloads)

Non-LTS Build Update (v2407.40000.0.0): Copy Section

Thursday 5th December 2024 Available Now (via the Stable release buttons in Downloads)

WSABuilds LTS 5 (v2407.40000.0.0) Copy Section

Thursday 5th December 2024 Available Now (via the Pre-release buttons in Downloads)

WSABuilds LTS 4 (v2407.40000.0.0): Copy Section

Monday 15th July 2024 Available Now (via the Pre-release buttons in Downloads)

WSABuilds LTS 3 (v2311.40000.5.0): Copy Section

Monday 03rd June 2024 Available Now (via the Pre-release buttons in Downloads)

WSABuilds LTS 2 (v2311.40000.5.0): Copy Section

Friday 03rd May 2024 Available Now (via the Pre-release buttons in Downloads)

WSABuilds LTS 1 (v2311.40000.5.0): Copy Section

Wednesday 03rd April 2024 Available Now (via the Pre-release buttons in Downloads)

  Installation

  Updating

  Uninstallation

  Backup and Restore Userdata

  FAQ

  App Compatibility

  Usage Guides

  Having Issues?

  Credits

File: Documentation/Fix Guides/Troubleshooting.md Copy Chapter

Troubleshooting Your Issue

• Check if your issue is listed in the list of "Common Issues" below: Copy Section

  Common Issues (Click Here)

• Still having the same issue after following a fixes guide in list of "Common Issues"? Copy Section

  • (For Windows 11 Users) Download WSA from the Microsoft Store or from [WSAPackages](https://github.com/MustardChef/WSAPackages) and test whether or not WSA is working.

  • If the official version of WSA (from the Microsoft Store or [WSAPackages](https://github.com/MustardChef/WSAPackages)) does not work, please file a Feedback Hub report using the instructions below (click on the button to view instructions)

    Filing a Feedback Hub Report (click here):

  Filing a Feedback Hub Report Copy Section

  I would very much recommend you to file a Feedback Hub report. Make sure you are logged into a Microsoft Account when filing a report. (You can only file a report using the official version)

  Instructions: (As shown by one of devs in WSA Development team at Microsoft)

  After Filing a Feedback Hub Report: Copy Section

  Also. After completing the report I would highly recommend you to open an issue on the WSA Github Repo (https://github.com/microsoft/WSA) with a link to your Feedback Hub report + full repro of the issue. This will help the dev team see the issue quicker.

  I know that its a hassle, but it ensures that it gets some eyes on the issue in the quickest possible way.

• Fix to your issue is not listed in the list of "Common Issues" or any of the above troubleshooting steps do not apply? Copy Section

  Open a Github Issue!

  or

  Join the Discord and seek assistance there!

File: Documentation/Fix Guides/Post-Install Issues/FixInternet.md Copy Chapter

WSABuilds      

Issues: Copy Chapter

No Internet Copy Section

Solution: Copy Chapter

These will be split into multiple solutions due to the different causes of the problem of no internet on Windows Subsystem for Android (WSA) and Windows Subsytem for Linux (WSL)

Fix #1: Uninstalling Hyper-V Network Adapters

Some Hyper-V Network Drivers may be interferring with WSA or WSL
 

⚠️ Carry these instructions out with caution. ⚠️

⚠️ I do not take responsibility for any damage caused ⚠️

 

**Step 1: Open Device Manager**

1. Using Search or Win + X, open Device manager

**Step 2: Show Hidden Device**

3. Press on "View"
4. Select "Show hidden devices"

**Step 3: Uninstalling All Hyper-V Network Adapter**

5. Select each driver that has "Hyper-V" in its name
6. Right-Click and select "Uninstall Driver" for each of these drivers

**Step 4: Restart Windows**

**Step 5: Restart your PC**

Fix #2: Checking Firewall Settings

Sometimes Windows Firewall and other Firewall tools and software may be the cause of internet issues. It is therefore important that we check them if we are facing issues with internet on WSA.

Users with Windows Firewall

1. Open Windows Firewall by pressing the Windows Key and "R" key, Open Run

2. Type WF.msc, and then select OK. See also Open Windows Firewall

3. Go to the "Inbound Connection" tab

4. Find the entries in the list that state: "Windows Subsystem for Android™"

5. Confirm that these entries are Enabled and "Action" is set to "Allow" for both UDP and TCP for all entries (as shown above)

6. Now, go to the "Outbound Connection" tab

7. Find the entries in the list that state: "Windows Subsystem for Android™"

5. Confirm that these entries are Enabled and "Action" is set to "Allow" for both UDP and TCP for all entries (as shown above)

You may not have as many entries for "Windows Subsystem for Android™", as shown in the screenshots provded. These are just for illustration purposes and Firewall entries may look different on your device.

Antivirus Users

It is a known issue that some antivirus firewall such as those built-in to ESET, Bitdefender, AVG and many others, can prevent the internet for Windows Susbsystem for Android (WSA) from working.
It is highly recommended to disable the firewall provided by these Antivirus/Antimalware tools and fallback to Windows Firewall (default), to see if the internet starts working.

Source: From my own experience and reports from others in the Discord community linked at the end. If disabling a certain antivirus/antimalware's built-in firewall works, please join the Discord server (invite at the end of this guide) and inform us.

---

Fix #3: Changing Android DNS Settings

1. By pressing the Windows Key and "R" key, Open Run

2. Type wsa://com.android.settings, and then select OK.

3. Wait for Android Settings to load and open.

4. In Android Settings, click on the "Network and Internet" Section.

5. In the "Network and Internet" Section, select "Private DNS" .

6. In the "Select Private DNS mode", click on "Private DNS provider hostname".

7. In the entry box below, type "dns.google" and click save.

8. Now click on the "Internet" section and click on VirtWifi.

9. Click on "Disconnect".

10. Then click on "Connect".

Your Internet should now be fixed!

---

Fix #4: Enabling and Disabling Advanced Networking from WSA Settings

1. Go to the Start Menu and search for Windows Subsystem for Android™

2. Depending on your WSA version, the Advanced Networking setting is located in different places witin the WSA Settings app

   • For 2305 and newer builds, you must go to "Advanced settings" and then to "Experimental features"
   • For 2304 and older builds, this setting is located in the "System" tab/ main screen when you open the Settings app
3. • If Advanced Networking is ENABLED, disable it as this may be causing issues with the internet and restart WSA and check if the interet is working now
   • If Advanced Networking is DISABLED, enable it as this may be causing issues with the internet and restart WSA and check if the interet is working now

This may fix the internet on WSA.

---

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

Startup Apps before proceeding**_

• _**2. Disable Hyper-V (if it is enabled) using the command**_

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

• **3. Reboot your PC**

• _**4. Reserve port 58526 so Hyper-V doesn't reserve it back using the command**_

netsh int ipv4 add excludedportrange protocol=tcp startport=58526 numberofports=1

• _**5. Re-enable Hyper-V (if it was previously enabled) using the command `dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All` and reboot your PC**_

Hope this works for you!

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Post-Install Issues/WSA Does Not Load After Install + No Splashscreen.md Copy Chapter

WSABuilds      

Issue: Windows Subystem for Android (WSA) is unable to run any apps and there is no splashscreen (when opening the Files app from the settings) and no icons for Android apps. Copy Chapter

Preface: Copy Section

Why this occurs is unknown. However, after multiple attempts trying to fix this issue, a solution was found.

https://github.com/MustardChef/WSABuilds/assets/68516357/a9690842-5159-470a-b472-5990faabeac8

Solution Copy Chapter

Rename the extracted folder to a shorter name, which can be anything to your choosing.

• Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

• After: WSAArchive2XXX

https://github.com/MustardChef/WSABuilds/assets/68516357/626ec699-6f74-40ff-94fb-26fbe1c4f182

Hope this works for you!

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Post-Install Issues/WSA Settings App Crashes + Android Apps Do Not Load After Installation.md Copy Chapter

WSABuilds      

Issue: Windows Subystem for Android (WSA) Settings app crashes after installation, when opened, and you are unable to run any apps. Copy Chapter

Preface: Copy Section

Why this occurs is unknown. However, after multiple attempts trying to fix this issue, a solution was found.

https://github.com/MustardChef/WSABuilds/assets/68516357/7333e8b4-7c09-4032-b816-47fc0d83767b

Solution Copy Chapter

Rename the extracted folder to a shorter name, which can be anything to your choosing.

• Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

• After: WSAArchive2XXX

https://github.com/MustardChef/WSABuilds/assets/68516357/7a33df5b-e68b-43b1-9365-9c4d7ff5c2db

Hope this works for you!

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Post-Install Issues/WSA Stopped Working!.md Copy Chapter

WSABuilds      

Issues: WSA Stopped Working! Copy Chapter

***You may encounter this problem. WSA has been working fine for you, but all of a sudden, it breaks/ stops working. You are distraught. What do you do, when WSA beloved had been borked.***

Solution: Copy Chapter

1. Go to "Turn Windows features on and off" and if any of these features below are enabled, DISABLE THEM.

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Subsystem for Linux

2. Restart your PC

3. Boot into your BIOS, and DISABLE Virtualization.

• Click here for a guide for Windows 11
• Click here for a guide for Windows 10

4. Ensure that you have Control Flow Guard enabled in Windows Security > Apps & browser control > Exploit protection. This is a known issue that can prevent WSA from starting

5. In registry editor (regedit), go to “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends"

   Change the value of “Start” from “3” to “0”

[!NOTE]
You can change it back to 3, if it makes no difference

6. Then in CMD (Run as Adminstrator), paste:

bcdedit /set hypervisorlaunchtype auto

7. ENABLE the features that you disabled in Step 1 and restart a second time.

8. Boot into your BIOS, and ENABLE Virtualization.

• Click here for a guide for Windows 11
• Click here for a guide for Windows 10

9. Restart the Computer

10. Try re-running WSA by running Run.bat or via the Windows Subsystem for Android Settings app

Hope this works for you!

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/Appx Module Cannot Be Loaded.md Copy Chapter

WSABuilds      

Error: Copy Chapter

The 'Get-AppxPackage' command was found in the module 'Appx', but the module could not be loaded due to the following error: [Operation is not supported on this platform. (0x80131539)] For more information, run 'Import-Module Appx'

Preface: Copy Chapter

This issue mainly occurs on the LTSC and non official builds of Windows.

Solution: Copy Chapter

1. Open PowerShell as Administrator

2. Run the following command:

cd <lLocation of the folder with the WSA files>
Import-Module -Name Appx -UseWindowsPowerShell
PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/Extraction Errors.md Copy Chapter

WSABuilds      

Error: Cannot Extract Files from the .7z archives for the WSA Builds Copy Chapter

• *7-zip* Copy Section

• *WinRAR* Copy Section

• *Windows Archive Extractor* Copy Section

Solution Copy Chapter

DO NOT USE THE BUILT IN WINDOWS ARCHIVE EXTRACTOR Copy Section

Ensure that WinRAR/ 7-Zip is up to date Copy Section

or

If you still encounter issues, reinstall WinRAR/ 7-Zip Copy Section

File: Documentation/Fix Guides/Pre-Install Issues/Fix Error 0x80073CF0.md Copy Chapter

WSABuilds      

Issue: Error 0x80073CF0 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to many factors such as corruption of files when downloading the .zip/.7z files or extracting from the .zip/.7z files. This can be also caused if the folder name is too long (This is the case as MagiskOnWSA tends to generate a long string for the .zip/.7z file and the folder within the archive.)

Solution Copy Chapter

1. Ensure the partition/drive you are installing from is NTFS

2. Redownload WSA Build .zip/.7z file from the Releases page (sometime the files can be corrupted during download and extraction)

3. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing (For example: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon ----> WSAArchive2XXX)

4. Extract the .zip or .7z archive (depends on the release) using 7-zip or a proper archive tool and not the built in Windows archive extractor

5. Rename the extracted folder(s) to a shorter name, which can be anything to your choosing

For example:

• Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon
• After: WSAExtracted2XXX

6. Ensure that 'Run.bat' is run as Administrator

Hope this works for you!

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/Fix Error 0x80073CF6.md Copy Chapter

WSABuilds      

Issue: Error 0x80073CF6 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to many factors that is preventing the app from being registered. Although there is no definite solution, we can try these steps to try to fix the problem

This installation issue may also arise in systems that are using Modified Windows OSes such as ReviOS, Tiny10/11, etc. This is due to the fact that these OSes have been modified to remove certain features that are deemed unnecessary. This may cause issues with the installation of WSA.

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered
In E:\WSA\Install.ps1:102 Character:1
+ Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion

   + CategoryInfo          : WriteError: (E:\WSA\AppxManifest.xml:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Prequisite Steps: Copy Chapter

1. Ensure the partition/drive you are installing from is NTFS

2. Redownload WSA Build .zip/.7z artifact (sometime the files can be corrupted during download and extraction)

3. If you have installed WSA prior, make sure that it has been uninstalled and delete all folders containing "WindowsSubsystemForAndroid" from the following directories/paths and the subdirectories within:

• C:\ProgramData\Microsoft\Windows\AppRepository

• C:\ProgramData\Microsoft\Windows\WindowsApps

• %localappdata\ProgramData\Packages

4. Restart your Computer

If the issue has been fixed, then there is no need to follow through the rest of the guide.
However, if you have the same issue, it is vital that you obtain the logs and try to decipher what is causing the error

To obtain the logs (admin privilege required):

1. Open a PowerShell window and change working directory to your Windows Subsystem For Android™ directory.

2. Run the command below in PowerShell. This should fail with an ActivityID, which is a UUID required for the next step.

   powershell Copy

   Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml

3. Run the command below in PowerShell. This should print the log of the failed operation.

   powershell Copy

   Get-AppPackageLog -ActivityID <UUID>

There are various causes that lead to error 0x80073CF6 Find the fix that matches the error presented in the logs obtained from the instructions above Copy Section

Issue 1: 0x800706D9 "There are no more endpoints avaliable from endpoint mapper" Copy Chapter

**Windows Firewall** Copy Section

1. Ensure that Windows Firewall is on and is working with "Recommended Settings" being enabled

2. Ensure that Windows Firewall service is running. If not, enable it.

3. Restart your PC

Other Firewalls Copy Section

1. Ensure that your Firewall is on and is working with "Recommended Settings" being enabled

2. Ensure that your Firewall is not blocking or preventing new entries

3. Restart your PC

Issue 2: 0x80073B06 "Initial screen image for the current application context cannot be recognized" Copy Chapter

Installing MagiskOnWSA...
Add AppxPackage: Deployment failed due to HRESULT: 0x80073CF6, unable to register the package.
AppxManifest.xml (24,27): Error 0x80073B06: Unable to install or update package MicrosoftCorporateII.WindowsSubsystemForAndroid_ 8wekyb 3d8bbwe because the initial screen image for the current application context cannot be recognized. The application context may include specific language, DPI, contrast, or other special conditions. If you cannot recognize a context specific splash screen image, add a splash screen image to use as the default setting. Note: For additional information, look for [ActivityId] 94c065bb-5a2a-0004-129b-c1942a5ad901 in the event log, or use the command line Get AppPackageLo g - ActivityID 94c065bb-5a2a-0004-129b-c1942a5ad901 in the location D:  WSA  WSA  Install.ps1:106 Character: 1
+ Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion  ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : WriteError: (D:\WSA\WSA\AppxManifest.xml:String) [Add-AppxPackage], IOException
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Solution: Copy Section

1. If you encounter this problem when installing from a build built using MagiskOnWSALocal or WSA-Script, try deleting the previously built builds and rebuild. Make sure to delete and reclone the git repo if you are building using MagiskOnWSALocal.

Or

2. If you encounter this problem when installing using prebuilt builds from Releases from this repo, try redownloading the latest build. If the issue persists, report to the Discord and I will be happy to assist you

Hope these fixes work for you!

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/Fix Error 0x80073CF9.md Copy Chapter

WSABuilds      

Issue: Error 0x80073CF9 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to many factors such as corruption of files when downloading the .zip files or extracting from the .zip files. This can be also caused if the folder name is too long (This is the case as MagiskOnWSA tends to generate a long string for the .zip file and the folder within the archive.)

Solution Copy Chapter

1. Ensure the partition/drive you are installing from is NTFS

2. Redownload WSA Build .zip/.7z file from the Releases page (sometime the files can be corrupted during download and extraction)

3. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing (For example: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon ----> WSAArchive2XXX)

4. Extract the .zip or .7z archive (depends on the release) using 7-zip or a proper archive tool and not the built in Windows archive extractor

5. Rename the extracted folder(s) to a shorter name, which can be anything to your choosing

For example:

• Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon
• After: WSAExtracted2XXX

6. Ensure that 'Run.bat' is run as Administrator

Hope this works for you!

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/Fix Error 0x80073CFB.md Copy Chapter

WSABuilds      

Issue: Error 0x80073CFB when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to the fact that "the provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details."

Solution Copy Chapter

1. Go to %LOCALAPPDATA%/Packages/, and make sure that the folder MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe is deleted. (If it does not exist, move on to Step 2.)

2. Open Powershell (as Admin) and run the following command:

Get-AppxPackage -Name "MicrosoftCorporationII.WindowsSubsystemForAndroid" -AllUsers | Remove-AppxPackage -AllUsers

3. Delete all folders related to WSA (except the .zip or .7z files (depends on the release ) for WSA Builds), which include folders extracted for WSA installation.

4. Rextract and re-run Run.bat

The issue should now be fixed

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/Fix Error 0x80073CFD.md Copy Chapter

WSABuilds      

Issue: Error 0x80073CFD when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused by having a Windows 10 Build that is too old to run WSA and hence the installer halts and presents the error, as shown below

Registering AppxManifest.xml... 
Add-AppxPackage : Deployment failed with HRESULT: 0x80073CFD, 
Prerequisite for an install could not be satisfied. Windows cannot install package MicrosoftCorporationII.WindowsSubsystemForAndroid_2301.40000.7.0_x64__8wekyb3d8bbwe because this package is not compatible with the device. 
The package requires OS version 10.0.19044.2604 or higher on the Windows.Desktop device family. 
The device is currently running OS version 10.0.19043.2364. 
NOTE: For additional information, look for [ActivityId] 8b8599fb-55c1-0002-338b-868bc155d901 in the Event Log or use the command line 
Get-AppPackageLog -ActivityID 8b8599fb-55c1-0002-338b-868bc155d901

Solution: Copy Chapter

The Solution is simple: Copy Section

Using the Microsoft Guide, update Windows 10 to the latest version

Or

Using the Windows 10 Update Assistant, update Windows 10 to the latest version

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/Fix Error 0x80073D10.md Copy Chapter

WSABuilds      

Issue: Error 0x80073D10 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused when your are trying to install the incorrect WSA package for your CPU Archetecture. For example, you are mistakenly trying to install the arm64 package on your x64 system.

Solution Copy Chapter

1. To ensure that you download the correct package for your CPU archtecture, go to the Downloads Section in the Readme.md

2. Click on the badge/button matching your Operating System (OS) and CPU Archetecture, which should lead you to the corresponding release

3. Download the package and then install it, by following the Installation guide in README.md

4. Enjoy

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/FixInstallps1.md Copy Chapter

WSABuilds      

Issues: Copy Chapter

• Install.ps1 is not recognized/found Copy Chapter

• Some files are missing in the folder Copy Chapter

Solution Copy Chapter

If the popup windows disappear without asking administrative permission and Windows Subsystem For Android™ is not installed successfully, you should manually run Install.ps1 as administrator:

1. Redownload the WSA Build and rename the extracted folder to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

2. Copy the path of the folder by right clicking on the folder and select "Show More Options" and click on "Copy as path"

3. Press Win + X on your keyboard and select Windows™ Terminal (Admin) or Powershell (Admin) depending on the version of Windows™ you are running

4. Input the command below and press enter, replacing {X:\path\to\your\extracted\folder} including the {} with the path of the extracted folder

cd "{X:\path\to\your\extracted\folder}"

5. Input the command below and press enter

PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1

6. The script will run and Windows Subsystem For Android™ will be installed

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/FixPathTooLong.md Copy Chapter

WSABuilds      

Issue: Error stating that "Path is too long" when extracting files from .zip archive, needed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused if the folder name is too long. This is the typically the case as MagiskOnWSALocal script tends to generate a long string for the .zip file and the folder within the archive.

Solution Copy Chapter

The solution is simple, all you have to do is:

1. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

2. Rename the extracted folder to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/InstallPs1FailedToUpdate.md Copy Chapter

WSABuilds      

Issues: Install.ps1 Failed To Update Copy Chapter

Solution: Copy Chapter

1. Execute:

PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1

Hope this works for you!

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/InternetSecuritySettingsBlock.md Copy Chapter

WSABuilds      

Issue: Error stating that "Your Internet security settings prevented one or more files from opening" when trying to run `Install.ps1` or `Run.bat` to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused if the folder name is too long. This is the typically the case as MagiskOnWSALocal script tends to generate a long string for the .zip file and the folder within the archive.

Solution Copy Chapter

The solution is simple, all you have to do is:

1. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

2. Rename the extracted folder to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

Have futher question or need help? Copy Section

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/NamedResource Not Found - Fix Error 0x80073B17.md Copy Chapter

WSABuilds      

Issue: Error 0x80073B17 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused/ associated with the Language Resource creation step which has moved from being processed within the Linux Bash script to a Windows PowerShell script ``MakePri.ps1/MakePri.exe``. Hence this may be caused by ``MakePri.ps1`` failing to run, and the reason for your installation failure is that the content of ``resources.pri`` is incorrect.

Main Solution:

This issue should have been fix as of the latest builds on the WSABuild releases and [this commit](https://github.com/LSPosed/MagiskOnWSALocal/commit/975bdcf4d82ef6fbca53ad5b7ea20380fcd94fdd) for [MagiskOnWSALocal](https://github.com/LSPosed/MagiskOnWSALocal/)

Make sure that you delete the extracted WSA folder and download the latest build from [Releases](https://github.com/MustardChef/WSABuilds/releases). Or make sure to reclone the [MagiskOnWSALocal Repo](https://github.com/LSPosed/MagiskOnWSALocal/) and rebuild. If the issue still persists, report this in [the GitHub Issues of this repo](https://github.com/MustardChef/WSABuilds/issues) or to the [Github Issues of the MagiskOnWSALocal Repo](https://github.com/LSPosed/MagiskOnWSALocal/issues)

Temporary Solution 1 (if the above permanent fixes do not work):

If you don't need localization and only English for WSA Settings you can follow the steps below Copy Section

1. You'll will need to delete the folder for this failed installation and regenerate it (rebuild and reextract)
2. Delete resources.pri before running the install script, Run.bat or Install.ps1
3. Delete it form filelist.txt to skip the check

Temporary Solution 2 (if the above permanent fixes do not work):

If you do need localization and language other than English for WSA Settings you can follow the steps below: Copy Section

Get the latest build with Language resources already merged and follow the normal [installation process](https://github.com/MustardChef/WSABuilds#--installation): Copy Section

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Fix Guides/Pre-Install Issues/Specified Logon Error.md Copy Chapter

WSABuilds      

Issue: A Specified Logon Session Does Not Exist Copy Chapter

Preface: Copy Section

This issue occurs when you are not installing WSA from an admin account. This is due to the [limitations of installing unsigned MSIX on non-Admin accounts](https://github.com/LSPosed/MagiskOnWSALocal/issues/276#issuecomment-1492594872).

Example: Copy Section

Solution: Copy Chapter

Make sure that the account that you are installing from is a Windows Administrator account. Copy Section

To check:

• 1. Open CMD

• 2. Type ```net localgroup administrators``` and press enter

• 3. Check if the account you are installing from, exists in the list of accounts in the "administrators" localgroup.

• 4. If it does not, then you are not installing from an admin account.

Make sure that you run ```run.bat``` as Administrator. Copy Section

Make sure that you run ```Install.ps1``` as Administrator. Copy Section

File: Documentation/Sponsors/PetroSky.md Copy Chapter

Hello, Android Emulator Experts! Copy Chapter

• Tired of slow, laggy emulator performance? Frustrated with long load times? PetroSky’s Pro+ plans are here to change that.

• Boost Your Android Emulator Performance with PetroSky Pro+!

Why PetroSky Pro+? Copy Section

PetroSky’s Pro+ plans bring powerful Virtual Private Servers (VPS) optimized for Android emulators. No more overloading your computer—let our VPS handle the heavy lifting. Copy Section

Key Benefits: Copy Section

• Blazing Speed: Run Android emulators without lag.

• Always Accessible: Access your Android setup anytime, anywhere.

• Unmatched Power: Run multiple emulators effortlessly.

• No PC Upgrades: Upgrade your VPS plan instead of your hardware.

• Work Anywhere: Connect from any internet-enabled device.

Who Can Benefit? Copy Section

• Developers: Test apps across versions side by side.

• App Testers: Run tests faster with fewer interruptions.

• Anyone: Enjoy Android apps smoothly without slowing your PC.

• No tech expertise? No problem—our team will guide you through setup.

Say goodbye to lag and hello to seamless Android emulation with PetroSky Pro+! Copy Section

Boost Android Emulator Performance with PetroSky Pro+ Plans! Copy Section

File: Documentation/Usage Guides/General Usage Guides/BusyBox.md Copy Chapter

WSABuilds      

Guide: How to install BusyBox Copy Chapter

Preface: Copy Section

Since Magisk has BusyBox built-in already, this proceedure is very simple

Process Copy Chapter

Step 1: Copy Section

Using an Android browser downloaded though the Play Store/sideloaded into WSA, download the following Magisk Module to install and symlink BusyBox with its applets to the Magisk built-in busybox binary. No need to do it manually or to get a Custom Build.

Step 2: Copy Section

Through Magisk Manager, install the Magisk module .zip file

Step 3 (Optional): Copy Section

You can then test if BusyBox is working by either using a Root Checker:

or by using ADB Shell and:

adb shell
su
busybox | head -1

If you find yourself stuck, or do not understand any steps in the guide, Join the Discord and ask here: Copy Section

File: Documentation/Usage Guides/General Usage Guides/ChangingGPU.md Copy Chapter

WSABuilds      

Guide: Changing the GPU used by Windows Subsystem For Android™ Copy Section

1. Open up Windows Subsystem For Android™ Settings --> Either by going to the Start Menu and searching for it or by using the Search feature

2. Make sure to turn off Windows Subsystem For Android™ by pressing Turn off in the Turn off Windows Subsystem For Android™ tab

3. In Windows Subsystem For Android™ Settings select the Graphics and Performance Tab

4. Click on the selection for GPU used for apps for Android™ and select the GPU that you would like Windows Subsystem For Android™ to use.

File: Documentation/Usage Guides/General Usage Guides/KernelSU.md Copy Chapter

Next Steps: Copy Chapter

1. Download the KernelSU Manager .apk Copy Section

2. Sideload the KernelSU Manager .apk into WSA Copy Section

Enjoy WSA with KernelSU! Copy Chapter

Having any issues?

Join the WSA Community Discord server via the invite below to recieve advice and support! Copy Section

File: Documentation/Usage Guides/General Usage Guides/LocalHostLoopback.md Copy Chapter

WSABuilds      

Guide: LocalHost Loopback Copy Chapter

Localhost Loopback has now been officially added to the update 2308 of WSA, and so this guide is probably outdated now. Copy Section

Preface: You want to connect WSA to the localhost (Windows 11 hosting machine) or to a development server I run on Windows 11 or any such scenario where you would want to connect to the Windows 11 localhost, but are unable to

Process: Copy Chapter

1. Run PowerShell as administrator

2. Execute

Set-NetFirewallHyperVVMSetting -VMCreatorId '{9E288F02-CE00-4D9E-BE2B-14CE463B0298}' -LoopbackEnabled True

3.Execute

New-NetFirewallHyperVRule -DisplayName LoopbackAllow -VMCreatorId '{9E288F02-CE00-4D9E-BE2B-14CE463B0298}' -Direction Inbound -Action Allow -LocalPorts [PORT]

(replacing [PORT] with the port you're trying to expose)

File: Documentation/Usage Guides/General Usage Guides/MoveToExtDrive.md Copy Chapter

WSABuilds      

Guide: Moving/Installing Windows Subsystem For Android™ (WSA) to another partition or disk Copy Chapter

Preface: Copy Section

WSA can take up a lot of storage space, hence you want to move it to another partition or disk with more space. This guide goes through a method by which you can install WSA from another disk and to store the data in that drive (instead of "%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe").

Prerequisites: Copy Section

• The partition/ disk that you want to move/install Windows Subsystem For Android™ to, MUST be NTFS
• Recommended that both disks, C:/ and the disk/partition that you want to install (move) WSA on (to), are SSDs
  • HDDs may work, but performance issues may arise
• Basic knowledge on Command Prompt (CMD) usage
• There must be enough space on the disk/partiton that you are installing/moving WSA to (recommended 20GB, as the VHDX can become very large in size)

[!NOTE]

If you want to preseve your data, make a backup of the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx file. After uninstalling, copy the VHDX file back to the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache folder.

Process: Copy Chapter

• Step 1: Remove all previous installations from WSABuilds or official WSA Releases Copy Section

  • To remove WSA installed through WSABuild:

    • 1.) Make sure that Windows Subsystem For Android™ is not running

    • 2.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

    • 3.) Delete the WSA folder that you extracted and Run.bat was run from to install WSA (MagiskOnWSA folder)

    • 4.) Go to %LOCALAPPDATA%/Packages/ and delete the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe

      • If you get an error that states that the file(s) could not be deleted, make sure that WSA is turned off

  • To remove WSA installed from the Microsoft Store:

    • 1.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

• Step 2: Install WSA from the desired partition Copy Section

  • 1.) Download the latest WSA Build according to Windows Version and CPU Archtecture from Downloads
  • 2.) Extract to the desired partition or drive
  • Using the same process as detailed in Installation
  • 3.) Open the extracted folder and run Run.bat

• Step 3: Moving the AppData (VHDX + data) from your Windows drive (C:\) to the desired partition/drive Copy Section

  • 1.) Go to %LOCALAPPDATA%\Packages\ and copy the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe to the desired drive/partition, making sure to delete the folder from %LOCALAPPDATA%\Packages\ after copying

  • 2.) Open Command Prompt (Admin) through Windows Terminal (Admin) or directly and run the command:

mklink /J "%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe" "Location_Of_Folder_In_Other_Drive"

Replacing Location_Of_Folder_In_Other_Drive with the location of the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe, copied to the desired to the drive/partition in 1st point of Step 3

• Step 4: Testing if everything is working Copy Section

  • Run Windows Subsystem For Android™ Settings
    • If it crashes, you have made a mistake whilst following the guide. Try following it again.

If you find yourself stuck, or do not understand any steps in the guide, Join the Discord and ask here: Copy Section

File: Documentation/Usage Guides/General Usage Guides/MoveToExtDrive_CN.md Copy Chapter

WSABuilds      

指南：将 Windows Subsystem For Android™（WSA）移动/安装到其他分区或磁盘 Copy Chapter

前言： Copy Section

WSA 可以占用大量存储空间，因此您想将其移动到具有更多空间的其他分区或磁盘。本指南介绍了一种方法，通过该方法，您可以从其他磁盘安装 WSA 并将数据存储在该驱动器中（而不是“%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe”）。

先决条件： Copy Section

• 您要将 Windows Subsystem For Android™ 移动/安装到的分区/磁盘，必须为 NTFS
• 建议 C:/ 和您要安装（移动）WSA 的磁盘/分区都是 SSD
  • HDD 可能可以工作，但可能会出现性能问题
• 基本了解如何使用命令提示符（CMD）
• 安装/移动 WSA 的磁盘/分区上必须有足够的空间（建议为 20GB，因为 VHDX 可以变得非常大）

注意

如果您要保留数据，请备份 %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx 文件。卸载后，将 VHDX 文件复制回 %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache 文件夹。

过程： Copy Chapter

• 步骤 1：从 WSABuilds 或官方 WSA 发行版中删除所有以前的安装 Copy Section

  • 要从 WSABuild 安装中删除 WSA：

    • 1.） 确保 Windows Subsystem For Android™ 没有运行
    • 2.） 使用内置的 Windows 搜索或通过“添加和删除程序”搜索“Windows Subsystem For Android™ 设置”，然后按卸载
    • 3.） 删除您提取和运行 Run.bat 安装 WSA 的 WSA 文件夹（MagiskOnWSA 文件夹）
    • 4.） 转到“%LOCALAPPDATA%/Packages/”并删除名为“MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe”的文件夹
      • 如果出现无法删除文件的错误，请确保 WSA 已关闭

  • 要从 Microsoft Store 安装中删除 WSA：

    • 1.） 使用内置的 Windows 搜索或通过“添加和删除程序”搜索“Windows Subsystem For Android™ 设置”，然后

• 步骤2：从所需分区安装WSA Copy Section

  • 1.) 从下载页面下载适用于Windows版本和CPU架构的最新WSA Build
  • 2.) 将其解压到所需分区或驱动器
  • 使用与安装中详细描述的相同过程
  • 3.) 打开已提取的文件夹并运行Run.bat

• 步骤3：将AppData（VHDX +数据）从Windows驱动器（C:\）移动到所需的分区/驱动器 Copy Section

  • 1.) 转到%LOCALAPPDATA%\Packages\并复制名为MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe的文件夹到所需的驱动器/分区，确保在复制后从%LOCALAPPDATA%\Packages\中删除该文件夹

  • 2.) 通过Windows终端（管理员）或直接打开管理员命令提示符，并运行以下命令：

mklink /J "%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe" "Other_Drive中文件夹的位置"

用所需分区/驱动器中复制到的名为 MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe 的文件夹位置替换 "Other_Drive_中的文件夹位置"。

• 步骤 4：测试一切是否正常 Copy Section

  • 运行 Windows 子系统 For Android™ 设置
    • 如果崩溃了，那么您在遵循本指南时可能犯了一个错误。请尝试再次遵循指南。

如果您遇到困难或不理解指南中的任何步骤，请加入 Discord 并在此处询问： Copy Section

File: Documentation/Usage Guides/General Usage Guides/Remove Non Existent Entries.md Copy Chapter

WSABuilds      

Guide: Removing entries of apps that do not exist Copy Chapter

Preface: Copy Section

Sometimes, switching from a WSA Build with Amazon Appstore to a build with "Removed Amazon Appstore" or a build with "MindTheGapps" to a build with "No-Gapps" etc., the system apps that were installed (either Google Play Store and related apps and/or the Amazon Appstore) from the previous build may still show up in the WSA Settings's "Apps" section. This guide goes through a method by which you can remove these entries from the WSA Settings's "Apps" section.

Sometimes after uninstalling WSA completely, apps still show up on Add and Remove programs or third-party uninstallers/app managers

Example: Copy Section

Steps: Copy Chapter

1. Open Registry Editor (regedit.exe) as Administrator

2. Navigate to `Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall`

3. You will find all the entries from WSA apps here. Search for the app you want to remove from the WSA Settings's "Apps" section.

4. Once you find the entry, delete it.

5. Repeat steps 3 and 4 for all the apps you want to remove from the WSA Settings's "Apps" section.

6. Restart your PC.

7. The apps you deleted the entries of should no longer show up in the WSA Settings's "Apps" section.

Hope this helps! Copy Section

Have futher question or need help? Copy Chapter

Join the Discord if you have any other questions or need help!

File: Documentation/Usage Guides/Post-Installation Guides/Amazon Appstore Only.md Copy Chapter

Having any issues?

Join the WSA Community Discord server via the invite below to recieve advice and support! Copy Section

File: Documentation/Usage Guides/Post-Installation Guides/Gapps and AMZ Appstore.md Copy Chapter

Having any issues?

Join the WSA Community Discord server via the invite below to recieve advice and support! Copy Section

File: Documentation/Usage Guides/Post-Installation Guides/Magisk.md Copy Chapter

Having any issues?

Join the WSA Community Discord server via the invite below to recieve advice and support! Copy Section

File: Documentation/Usage Guides/Post-Installation Guides/MagiskDelta.md Copy Chapter

Having any issues?

Join the WSA Community Discord server via the invite below to recieve advice and support! Copy Section

File: Documentation/Usage Guides/Post-Installation Guides/MindTheGapps.md Copy Chapter

Having any issues?

Join the WSA Community Discord server via the invite below to recieve advice and support! Copy Section

File: Documentation/Usage Guides/Post-Installation Guides/KernelSU/MindTheGapps and AMZ/MindTheGapps and AMZ.md Copy Chapter

Next Steps: Copy Chapter

1. Download the KernelSU Manager .apk Copy Section

2. Sideload the KernelSU Manager .apk into WSA Copy Section

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/KernelSU/MindTheGapps and Removed AMZ/MindTheGapps and Removed AMZ.md Copy Chapter

Next Steps: Copy Chapter

1. Download the KernelSU Manager .apk Copy Section

2. Sideload the KernelSU Manager .apk into WSA Copy Section

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/KernelSU/No Gapps and AMZ/No Gapps and AMZ.md Copy Chapter

Next Steps: Copy Chapter

1. Download the KernelSU Manager .apk Copy Section

2. Sideload the KernelSU Manager .apk into WSA Copy Section

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/KernelSU/No Gapps and Removed AMZ/No Gapps and Removed AMZ.md Copy Chapter

Next Steps: Copy Chapter

1. Download the KernelSU Manager .apk Copy Section

2. Sideload the KernelSU Manager .apk into WSA Copy Section

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and AMZ/Alpha.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and AMZ/Beta.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and AMZ/Canary.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and AMZ/Debug.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and AMZ/Delta.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and AMZ/Stable.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and Removed AMZ/Alpha.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and Removed AMZ/Beta.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and Removed AMZ/Canary.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and Removed AMZ/Debug.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and Removed AMZ/Delta.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/MindTheGapps and Removed AMZ/Stable.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and AMZ/Alpha.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and AMZ/Beta.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and AMZ/Canary.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and AMZ/Debug.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and AMZ/Delta.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and AMZ/Stable.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and Removed AMZ/Alpha.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and Removed AMZ/Beta.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and Removed AMZ/Canary.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and Removed AMZ/Debug.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and Removed AMZ/Delta.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/Magisk/No Gapps and Removed AMZ/Stable.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/No Root/MindTheGapps and AMZ/MindTheGapps and Amazon Appstore.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/No Root/MindTheGapps and Removed AMZ/MindTheGapps and Removed Amazon.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/No Root/No Gapps and AMZ/No Gapps and Amazon Appstore.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Post-Installation Guides/No Root/No Gapps and Removed AMZ/No Gapps and Removed Amazon.md Copy Chapter

Click on the "Troubleshoot" button above or join the WSA Community Discord server via the invite below to recieve advice and support!

File: Documentation/Usage Guides/Sideloading Guides/ADB-Sideloading.md Copy Chapter

WSABuilds      

Sideloading APKs in to Windows Subsystem for Android

Setting up ADB to work with WSA Copy Chapter

• Launch Windows Subsystem for Android.
• Here, click on Advanced Settings and then enable Developer mode by clicking on the toggle button.
• Take note of IP address and port shown in the Developer mode section.
• Launch Windows Terminal and make sure ADB is installed (install ADB).
• Use command adb pair to pair ADB with WSA.
• In Wireless debugging window, see Device name and under it IP address and port.
• Use command adb connect to connect WSA with ADB.

Once this is done, use command adb devices to make sure that WSA is connected.

Installing APKs using ADB Copy Chapter

Now you can install any app you want, but I personally suggest installing a web browser and a file manager first.

• Download the APK.
• Open File Explorer, right click on downloaded APK and tap on Copy as path.
• Launch Windows Terminal.
• Use adb install <file path> to install the APK.
  [P.S. You can right click to paste in Terminal]

After installation using ADB Copy Chapter

You can now open the web browser you installed in Android, and download and install Aurora Store like you do on any Android device - normally sideloading APK without using ADB.

A list of suggested apps to install on WSA: Copy Section

• microG: A free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries.
• Aurora Store: an app store that lets you download apps from Google Play without a Google account.
• FX File Explorer: FX File Explorer is a mix of explorers (SD, FTP, Lan, Cloud and other storage explorers) and is a fast, smooth, beautiful, reliable and full-featured file manager with a simple and intuitive user interface.
• Bromite: A Chromium fork with support for ad blocking and enhanced privacy.

File: Documentation/Usage Guides/Sideloading Guides/Sideloading.md Copy Chapter

WSABuilds      

Guide: Sideloading APKs Copy Chapter

This guide covers the five different methods of sideloading and installing APKs (from Windows) into Windows Subsystem For Android™ Copy Section

File: Documentation/Usage Guides/Sideloading Guides/WSA-Sideloader.md Copy Chapter

WSABuilds      

WSA Sideloader Usage Guide

With WSA Sideloader, you can install any APK file onto WSA, as well as XAPK, APKM and APKS files.

This guide will show you how to use it.

How to Download and Install WSA-Sideloader Copy Chapter

You can download WSA Sideloader in 3 different ways:

Setup Copy Chapter

Step 1. Once installed, you should see this screen:

[!NOTE]
If you get a message that says WSA is not installed, check that you have downloaded and installed WSA correctly as per the WSABuilds instructions.

Step 2. Next, open WSA Settings from the start menu or by typing wsa-settings:// in your browser's address bar, select Developer and enable Developer mode.

Step 3. Now, you can click the Browse button to select your APK file. You can also double click a file in File Explorer to automatically open WSA Sideloader with the APK file already selected.

Step 4. The first time you install an APK, it will ask to allow ADB debugging. Allow it and attempt the installation again. Check the always allow box if you don't want to manually accept the permission every time you install an app.

Step 5. It should take a few seconds to install the APK. Once it says The application has been successfully installed, you can click Open app. Bundle files may take longer depending on the file size.

[!NOTE]
If WSA is off, WSA Sideloader will start it for you. After 30 seconds, the installation will automatically continue.

You can find all your installed WSA apps on the start menu, as well as via the "Installed apps" button in WSA Sideloader:

Updating WSA Sideloader Copy Chapter

From time to time, there may be updates that improve the reliability of the app, as well as ensuring it works properly with future releases of WSA.

Therefore, it's highly recommended you keep it up to date. The application will notify you of an update the next time you launch it.

Troubleshooting Copy Chapter

If you get an error like the one below, check that you have allowed the ADB authorization and enabled Developer Mode. Also try disabling and enabling USB debugging under manage developer settings as that can sometimes fix issues with the ADB connection.

If you get a message saying No connection could be made because the target machine actively refused it, follow this guide

If you continue to face problems, make a note of the error info displayed in WSA Sideloader and join the Discord server below for further assistance.

Credits Copy Chapter

Special Thanks to infinitepower18

Feel free to Star the [WSA-Sideloader Github Repo](https://github.com/infinitepower18/WSA-Sideloader/), if you found the app useful

File: Documentation/Usage Guides/Sideloading Guides/WSAFiles.md Copy Chapter

Sideloading using the Files app

Starting with WSA version 2305, you can sideload APK files using the Files app. This guide will show you how.

[!IMPORTANT]
This guide is only applicable for WSA versions 2305 and above. If you're using an older version, you will need to use ADB or one of the listed APK installers.

Setup Copy Chapter

1. Open the Windows Subsystem for Android app, go to Advanced Settings and enable share user folders found under experimental features. Then select the folder that you would like to share by clicking on "Change folder".

2. Go to the "System" section and open the Files app.

3. Click on Subsystem for Android, followed by Windows to browse through your Windows files.

4. Click the APK you want to install and choose package installer if it asks. Agree to the warnings and then click install.

[!NOTE]
If you're facing problems, try disabling Block installation of malicious apps in the WSA app.

After installation Copy Chapter

Once installed, you can launch the sideloaded app from the Start Menu.

If you want to install bundle files, such as .apkm or .xapk, you can install [SAI](https://apkpure.com/split-apks-installer-sai/com.aefyr.sai) and use that to install bundle files, as well as regular APKs.

File: Documentation/Usage Guides/Sideloading Guides/WSAPacman.md Copy Chapter

WSABuilds      

WSAPacman

Step 1:   Download and install WSA Pacman

Step 2:   Go to Windows Subsystem for Android → Developer and turn on Developer mode.

[!IMPORTANT]

You have to give WSAPacman, ADB Debugging permission.

Issues and Solutions Copy Chapter

[!NOTE]

If the "Install" button is greyed out while installing apk

Solution: Open WSAPacman and turn on WSA from there.

[!NOTE]

If WSAPacman states that the "Installation timed out":

Solution: Wait for a few minutes, and see if the app is installed and shows in the Start Menu. If not retry the installation In the case that nothing works, report this to the [WSAPacman Github](https://github.com/alesimula/wsa_pacman)

File: Documentation/WSABuilds/Backup and Restore.md Copy Chapter

WSABuilds      

  Backup and Restore Userdata

Backing Up Your Userdata Copy Chapter

In order to make a backup of your WSA data you must copy the Userdata.vhdx (which includes, but is not limited Android Apps and their data, settings etc.), located at %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx, to a safe location

Restoring Your Backup Copy Chapter

Before attempting to restore your backup, you must remove WSA if installed. Then before you run the Run.bat script (to reinstall WSA after removing it), you need to remove these lines from Install.ps1, located in the your extracted WSA folder:

[!TIP]
The Lines (as shown below) that you need to remove in Install.ps1 may vary depending on the type of WSA Build that you are trying to install.

Android Settings:

Start-Process "wsa://com.android.settings"

Official Magisk:

Start-Process "wsa://com.topjohnwu.magisk"

Magisk Delta:

Start-Process "wsa://io.github.huskydg.magisk"

Magisk Alpha:

Start-Process "wsa://io.github.vvb2060.magisk"

Google Play Store:

Start-Process "wsa://com.android.vending"

Amazon Appstore:

Start-Process "wsa://com.amazon.venezia"

After removing the lines above, run the script.

When the Powershell window states "Press any key to quit", at that time multiple dialouge boxes will open:

[!IMPORTANT]
Ignore these and do not click on anything or close these popups

Go to %localappdata%\Packages and (if these folders/directory do not exist, create them) in MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\ paste the userdata.vhdx

Now close the popups and run WSA and your userdata should hopefully be restored

File: Documentation/WSABuilds/Credits.md Copy Chapter

WSABuilds      

  Credits

Other Projects used as reference or referenced Copy Section

• WSA-Sideloader: Easily sideload Android apps on Windows Subsystem for Android

• WSAPacman: A GUI package manager and package installer for Windows Subsystem for Android (WSA)

• APK-Installer: An Android Application Installer for Windows

• StoreLib: API for downloading WSA

• Magisk: The Magic Mask for Android

• KernelSU: A Kernel based root solution for Android

• WSAGAScript: The first GApps integration script for WSA

• MagiskOnWSA: Deprecated Integrate Magisk root and Google Apps into WSA

Is this GitHub Repo affiliated with Microsoft™? Copy Section

NO!

- Microsoft and the Dev team at MSFT are the developers of Windows Subsystem For Android. We do not claim to develop, or have a part in developing this emulator. We also have no real influence on the direction of development of WSA and nor do we claim to.

- What the WSABuild repo does is that it provides prebuilt WSA builds with Root and GMS built using the MagiskOnWSALocal project (and WSAPatch for the Windows 10 patch.) That is that we simply modify the emulator to add extra functionality to it.

- All this is, is an unofficial project not related in any way to Microsoft and the team working on Windows Subsystem For Android.

Is this GitHub Repo affiliated with Google™ or Android™? Copy Section

NO!

This is an unofficial project not related in any way to Google and the team working on Android.

[!IMPORTANT]
The repository is provided as a utility.
Android is a trademark of Google LLC. Windows™ and Windows Subsystem for Android™ are trademarks of Microsoft LLC.
The developers of this repository are not affiliated with Google LLC or Microsoft LLC.
The developers of this repository are not responsible for any damage caused by the use of the software provided in this repository

File: Documentation/WSABuilds/Custom Builds.md Copy Chapter

WSABuilds      

  Custom Builds Requests

  ❓Want to request a prebuilt custom build❓

If you can't find the build that you are looking for, I will be happy to fufill any custom build requests.

Open an issue in the [Issues page](https://github.com/MustardChef/WSABuilds/issues) with the information below.

[!IMPORTANT]

• State the Device Model (Default: Pixel 5)?
• State the Root Solution (Magisk, KernelSU or none)?
• State if you want a WSA build with Magisk, what variant of magisk would you like?
• State if you would you like GApps (Google Play Store and Play Services (GMS))?
• State if you would you like to keep the Amazon Appstore?

File: Documentation/WSABuilds/FAQ.md Copy Chapter

WSABuilds      

  FAQ

Help me, I am having problems with the MagiskOnWSA Builds

• Open an issue in Github or join the Discord and describe the issue with sufficent detail

Help me, I am having problems with installing Windows Subsystem For Android™ on Windows™ 10

• I am not working on the patch, and nor claim to. Open an issue in the Discord or Github, and I will try to assist you with the problem if possible. For full support visit the project homepage and open an issue there: https://github.com/cinit/WSAPatch/issues/

How do I get a logcat?

• There are two ways:

  text Copy

  adb logcat

  or

• Location in Windows ---> %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalState\diagnostics\logcat

Can I delete the installed folder?

• No.

How can I update Windows Subsystem For Android™ to a new version?

• As Explained Installation instructions. Download the latest Windows Subsystem For Android™ Version and replace the content of your previous installation and rerun Install.ps1. Don't worry, your data will be preserved

How do I update Magisk?

• Do the same as updating Windows Subsystem For Android™. Wait for a new MagiskOnWSA release that includes the newer Magisk version, then follow the Installation instructions to update

Can I pass SafetyNet/Play Integrity?

• No. Virtual machines like Windows Subsystem For Android™ cannot pass these mechanisms on their own due to the lack of signing by Google. Passing requires more exotic (and untested) solutions like: <https: 145#discussioncomment-2170917="" discussions="" github.com="" kdrag0n="" safetynet-fix="">

What is virtualization?

• Virtualization is required to run virtual machines like Windows Subsystem For Android™. Run.bat helps you enable it. After rebooting, re-run Run.bat to install Windows Subsystem For Android™. If it's still not working, you have to enable virtualization in your BIOS/UEFI. Instructions vary by PC vendor, look for help online

Can I remount system partition as read-write?

• No. Windows Subsystem For Android™ is mounted as read-only by Hyper-V. You can, however, modify the system partition by creating a Magisk module, or by directly modifying the system.img file

I cannot adb connect localhost:58526

• Make sure developer mode is enabled. If the issue persists, check the IP address of Windows Subsystem For Android™ on the Settings ---> Developer page and try

  text Copy

  adb connect ip:5555

Magisk online module list is empty?

• Magisk actively removes the online module repository. You can install the module locally or by

  Step 1

  text Copy

  adb push module.zip /data/local/tmp

  Step 2

  text Copy

  adb shell su -c magisk --install-module /data/local/tmp/module.zip

How do I uninstall Magisk?

• Request, using Issues, a Windows Subsystem For Android™ version that doesn't include Magisk from the Releases page. Then follow the Installation instructions

Can I switch between OpenGApps and MindTheGapps?

• No. GApps will no longer function. Do a complete uninstallation before switching

How do I install custom Magisk or GApps?

• To request a build with custom Magisk or GApps, feel free to open an issue in the Issues page You can also achieve this by using the MagiskOnWSALocal Script and following the provided instructions located in the repo.

File: Documentation/WSABuilds/Having Issues.md Copy Chapter

WSABuilds      

  Having Issues?

Common Issues: Copy Section

File: Documentation/WSABuilds/Information.md Copy Chapter

WSABuilds      

  WSABuilds Project Status

⚠️❗IMPORTANT: Read Before Downloading❗⚠️

WSABuilds Repo Info Copy Chapter

Known Issues that may affect your WSA experiences:

• GApps Issues : https://github.com/LSPosed/MagiskOnWSALocal/issues/595
• Folder Issue : Long folder name for the WSA Folder (auto generated by the MagiskOnWSALocal script) may cause WSA to not start. Rename the folder to WSA after extracting and before installing WSA.
• Installed Magisk Modules disappear after install and subsequent reboot (WSA v2307): https://github.com/MustardChef/WSABuilds/issues/154

File: Documentation/WSABuilds/Installation.md Copy Chapter

WSABuilds      

  Installation

[!NOTE]

If you have the official Windows Subsystem For Android™ installed, you must completely uninstall it to use MagiskOnWSA.

[!IMPORTANT]

In case you want to preserve your data from the previous installation (official or MagiskOnWSA), you can backup Userdata.vhdx, located at %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx before uninstallation and restore it after installation. A guide for this process is located further down in this README.

Video Guide: Copy Section

Special Thanks to kilObit (creator of the video)

1. Go to the Releases page
2. In the latest release, go to the Assets section and download the Windows Subsystem For Android™ version of your choosing (do not download "Source code")
3. Extract the .7z archive and rename the folder (that you extracted) to WSA
4. Delete the .7z archive
5. Move the newly extracted folder to a suitable location (Documents folder is a good choice), as you will need to keep the folder on your PC to use MagiskOnWSA

[!NOTE]
If you're updating WSA, merge the folders and replace the files for all items when asked

6. Open the Windows Subsystem For Android™ folder: Search for and double-click Run.bat

   • If you previously have a MagiskOnWSA installation, it will automatically uninstall the previous one while preserving all user data and install the new one, so don't worry about your data.

   • If the popup windows disappear without asking administrative permission and Windows Subsystem For Android™ is not installed successfully, you should manually run Install.ps1 as administrator:

     • Press Win+x and select Windows™ Terminal (Admin)

     • Input the command below and press enter, replacing {X:\path\to\your\extracted\folder} including the {} with the path of the extracted folder

       powershell Copy

       cd "{X:\path\to\your\extracted\folder}"

     • Input the command below and press enter

       powershell Copy

       PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1

     • The script will run and Windows Subsystem For Android™ will be installed

     • If this workaround does not work, your PC is not supported for WSA

7. Once the installation process completes, Windows Subsystem For Android™ will launch (if this is a first-time install, a window asking for consent to diagnositic information will be shown instead. Sometimes two identical windows will show, this is fine and nothing bad happens if you click OK in both windows)

8. Click on the PowerShell window, then press any key on the keyboard, the PowerShell window should close

9. Close File Explorer

10. Enjoy

--- 

Notice (Applicable for both Windows 10 and 11): Copy Section

1. You can NOT delete the Windows Subsystem For Android™ installation folder.
   What Add-AppxPackage -Register .\AppxManifest.xml does is to register an appx package with some existing unpackaged files,
   so you need to keep them as long as you want to use Windows Subsystem For Android™.
   Check https://learn.microsoft.com/en-us/powershell/module/appx/add-appxpackage?view=windowsserver2022-ps for more details.
2. You need to register your Windows Subsystem For Android™ appx package before you can run Windows Subsystem For Android™.
   For WSABuilds and MagiskOnWSALocal users, you need to run Run.bat in the extracted dir.
   If the script fails, you can take the following steps for diagnosis (admin privilege required):

   1. Open a PowerShell window and change working directory to your Windows Subsystem For Android™ directory.

   2. Run the command below in PowerShell. This should fail with an ActivityID, which is a UUID required for the next step.

      powershell Copy

      Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml

   3. Run the command below in PowerShell. This should print the log of the failed operation.

      powershell Copy

      Get-AppPackageLog -ActivityID <uuid>

   4. Check the log for the reason of failure and fix it.

File: Documentation/WSABuilds/OldBuilds.md Copy Chapter

Old WSA Builds

File: Documentation/WSABuilds/Uninstallation.md Copy Chapter

WSABuilds      

  Uninstallation

[!NOTE]

If you want to preseve your data, make a backup of the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx file. After uninstalling, copy the VHDX file back to the %LOCALAPPDATA%\Package\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache folder. For a more comprehensive and detailed guide, take a look at the Backup and Restore section in this README markdown

To remove WSA installed through WSABuild: Copy Section

• 1.) Make sure that Windows Subsystem For Android™ is not running

• 2.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

• 3.) Delete the WSA folder that extracted you extracted and Run.bat was run from to install WSA (MagiskOnWSA folder)

• 4.) Go to %LOCALAPPDATA%/Packages/ and check if the folder: MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe is still present:

  • If the folder is still present: Delete it
    • If you get an error that states that the file(s) could not be deleted, make sure that WSA is turned off
  • If the folder does not exist: Skip this step

To remove WSA installed from the Microsoft Store: Copy Section

• 1.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

File: Documentation/WSABuilds/Updating.md Copy Chapter

WSABuilds      

  Updating

How do I update without losing any of my apps and data on Windows Subsystem for Android (WSA) Copy Section

[!IMPORTANT]
Make sure that WSA has been turned off from the settings and that tools such has WSA-System-Control, WSA-Sideloader, WSAPacman etc are not running.

1. Download the latest build (that you want to update to)

2. Make sure Windows Subsystem For Android is not running (Click on "Turn off" in the WSA Settings and wait for the spinning loader to disappear)

3. Using 7-Zip, WinRAR or any other tool of choice, open the .7z archive

4. Within the .7z archive, open the subfolder

   • Example:

     • WSA_2xxx.xxxxx.xx.x_xx

     or

     • WSA_2xxx.xxxxx.xx.x_xx_Release-Nightly-with-magisk-xxxxxxx-MindTheGapps-xx.x-RemovedAmazon)

5. Select all the files that are within this subfolder and extract them to the current folder where the file for Windows Subsystem For Android (the folder you extracted, and installed WSA from) are located

6. When prompted to replace folders, select "Do this for all current items" and click on "Yes"

7. When prompted to replace files, click on "Replace the files in the destination"

8. Run the Run.bat file

9. Launch Windows Subsystem For Android Settings app and go to the About tab using the sidebar

10. Check if the WSA version matches the latest version/ the version number that you want to update to

Join the Discord if you are having any difficulties

File: Documentation/WSABuilds/Usage Guide.md Copy Chapter

WSABuilds      

  Usage Guides

GPU Guide: Copy Section

Sideload Guide/Installing an APK: Copy Section

Moving WSA to another drive or partition: Copy Section

Installing KernelSU: Copy Section

Installing BusyBox: Copy Section

Localhost Loopback Guide: Copy Section

Remove Non-Existent App Entries: Copy Section

File: MagiskOnWSA/DLL/README.md Copy Chapter

WSAPatch

https://github.com/cinit/WSAPatch/releases

File: MagiskOnWSA/DLL/docs/README.md Copy Chapter

WSA-Script

MagiskOnWSA (For Windows™ 10 and 11) by [@YT-Advanced](https://github.com/YT-Advanced/) Copy Chapter

Windows Subsystem For Android™ (WSA) with Google Play Services and Magisk Copy Section

  ❓Want to build your custom build❓

:exclamation: Important:   ⚠️DO NOT FORK⚠️
This repository is designed specifically not to be forked. MagiskOnWSA and some of the various forks and clones that have sprung up on the platform (potentially) violate GitHub's Terms of Service due to abuse of GitHub Actions and have been ultimately warned, disabled or banned.
Therefore, don't fork this repository unless you're a developer and want to modify the code itself and/or want to contribute to this Github repository.
If you want to create your Custom Build, please follow the instructions set out clearly, to avoid the repo from being taken down as a result of a misuse of Github Actions due to the large number of forks. AND ALSO if you want to build with Latest Insider version, please skip the first 7 steps

**1. Star this repos (I will happy if you do that)**

**2. Check the version from [Releases](https://github.com/YT-Advanced/WSA-Script/releases/) first. If it does not have the version you want, continue to follow this guide. If it does, then feel free to use those prebuild WSA builds**

**3. Open [this page directly](https://YT-Advanced.github.io/WSA-Script) then choose the option that you want to build**

**4. Click "Create Issues" Button, the issues page will be generated and open. Then you click "Submit New Issues" (green button) and wait.**

**5. After about 10 minutes, the bot will reply that the workflow have built successfully (like the picture below), OPEN THE LINK BELOW THE BOT COMMENT**

**6. Download the package as artifact**

DO NOT download it via multithread downloaders like IDM

**7. Install like normal using [the instructions](https://github.com/YT-Advanced/WSA-Script#--installation) in this repository** and most important of all....

Downloads Copy Chapter

Requirements Copy Chapter

Note :
If you have the official Windows Subsystem For Android™ installed, you must completely uninstall it to use MagiskOnWSA.

In case you want to preserve your data from the previous installation (official or MagiskOnWSA), you can backup %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx before uninstallation and restore it after installation. For a more comprehensive and detailed guide, take a look at the Backup and Restore section in this README markdown

1. Go to the Releases page
2. In the latest release, go to the Assets section and download the Windows Subsystem For Android™ version of your choosing (do not download "Source code")

Note :
If you want to download WSA with Magisk Delta, please go to and download the package from the Action.

3. Check integrity of downloaded file by Follow this guide
4. Extract the zip file
5. Delete the zip file
6. Move the newly extracted folder to a suitable location (Documents folder is a good choice), as you will need to keep the folder on your PC to use MagiskOnWSA

Note :
If you're updating WSA, merge the folders and replace the files for all items when asked

7. Open the Windows Subsystem For Android™ folder: Search for and double-click Run.bat

   • If you previously have a MagiskOnWSA installation, it will automatically uninstall the previous one while preserving all user data and install the new one, so don't worry about your data.

   • If the popup windows disappear without asking administrative permission and Windows Subsystem For Android™ is not installed successfully, you should manually run Install.ps1 as administrator:

     • Press Win+X and select Windows™ Terminal (Admin)

     • Input the command below and press enter, replacing {X:\path\to\your\extracted\folder} including the {} with the path of the extracted folder

       powershell Copy

       cd "{X:\path\to\your\extracted\folder}"

     • Input the command below and press enter

       powershell Copy

       PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1

     • The script will run and Windows Subsystem For Android™ will be installed

     • If this workaround does not work, your PC is not supported for WSA

8. Once the installation process completes, Windows Subsystem For Android™ will launch (if this is a first-time install, a window asking for consent to diagnositic information will be shown instead. Sometimes two identical windows will show, this is fine and nothing bad happens if you click OK in both windows)

9. Click on the PowerShell window, then press any key on the keyboard, the PowerShell window should close

10. Close File Explorer

11. Enjoy

Notice (Applicable for both Windows 10 and 11): Copy Section

1. You can NOT delete the Windows Subsystem For Android™ installation folder.
   What Add-AppxPackage -Register .\AppxManifest.xml does is to register an appx package with some existing unpackaged files,
   so you need to keep them as long as you want to use Windows Subsystem For Android™.
   Check https://learn.microsoft.com/en-us/powershell/module/appx/add-appxpackage?view=windowsserver2022-ps for more details.
2. You need to register your Windows Subsystem For Android™ appx package before you can run Windows Subsystem For Android™.
   For WSA-Script and MagiskOnWSALocal users, you need to run Run.bat in the extracted dir.
   If the script fails, you can take the following steps for diagnosis (admin privilege required):

   1. Open a PowerShell window and change working directory to your Windows Subsystem For Android™ directory.

   2. Run the command below in PowerShell. This should fail with an ActivityID, which is a UUID required for the next step.

      powershell Copy

      Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml

   3. Run the command below in PowerShell. This should print the log of the failed operation.

      powershell Copy

      Get-AppPackageLog -ActivityID <UUID>

   4. Check the log for the reason of failure and fix it.

  Updating

How do I update without losing any of my apps and data on Windows Subsystem for Android (WSA) Copy Section

1. Download the latest build (that you want to update to)
2. Make sure Windows Subsystem For Android is not running (Click on "Turn off" in the WSA Settings and wait for the spinning loader to disappear)
3. Using 7-Zip, WinRAR or any other tool of choice, open the .zip file
4. Within the .zip archive open the subfolder (Example: WSA_2xxx.xxxxx.xx.x_x64_Release-Nightly-with-magisk-xxxxxxx-MindTheGapps-13.0-as-Pixel-5-RemovedAmazon)
5. Select all the files that are within this subfolder and extract them to the current folder where the file for Windows Subsystem For Android are (the folder you extracted, and installed WSA from)
6. When prompted to replace folders, select "Do this for all current items" and click on "Yes"
7. When prompted to replace files, click on "Replace the files in the destination"
8. Run the Run.bat file
9. Launch Windows Subsystem For Android Settings app and go to the About tab using the sidebar
10. Check if the WSA version matches the latest version/ the version number that you want to update to

  Uninstallation

 

Note:

If you want to preseve your data, make a backup of the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx file. After uninstalling, copy the VHDX file back to the %LOCALAPPDATA%\Package\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache folder. For a more comprehensive and detailed guide, take a look at the Backup and Restore section in this README markdown

• To remove WSA installed:

  • 1.) Make sure that Windows Subsystem For Android™ is not running

  • 2.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

  • 3.) Delete the WSA folder that extracted you extracted and Run.bat was run from to install WSA (MagiskOnWSA folder)

  • 4.) Go to %LOCALAPPDATA%/Packages/ and delete the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe

    • If you get an error that states that the file(s) could not be deleted, make sure that WSA is turned off

• To remove WSA installed from the Microsoft Store:

  • 1.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

 

  Backup and Restore Userdata

Backing Up Your Userdata Copy Chapter

In order to make a backup of your WSA data you must copy the Userdata.vhdx (which includes, but is not limited Android Apps and their data, settings etc.), located at %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx, to a safe location

Restoring Your Backup Copy Chapter

Before attempting to restore your backup, you must remove WSA if installed. Then before you run the "Run.bat" script (to reinstall WSA after removing it), you need to remove these lines from Install.ps1:

Official Magisk:

Start-Process "wsa://com.topjohnwu.magisk"

Magisk Alpha:

Start-Process "wsa://io.github.vvb2060.magisk"

Magisk Delta:

Start-Process "wsa://io.github.huskydg.magisk"

Google Play Store:

Start-Process "wsa://com.android.vending"

Amazon Appstore:

Start-Process "wsa://com.amazon.venezia"

After running the script, do not run WSA at all, and go to %localappdata%\Packages and (if the folders do not exist, create them) in MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\ paste the userdata.vhdx

Now run WSA and your serdata should hopefully be restored

  FAQ

 
Help me, I am having problems with the MagiskOnWSA Builds

• Open an issue in Github and describe the issue with sufficent detail

Help me, I am having problems with installing Windows Subsystem For Android™ on Windows™ 10

• I am not working on the patch, and nor claim to. Open an issue in Github, and I will try to assist you with the problem if possible. For full support visit the project homepage and open an issue there: https://github.com/cinit/WSAPatch/issues/

How do I get a logcat?

• There are two ways:

  text Copy

  adb logcat

  or

• Location in Windows ---> %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalState\diagnostics\logcat

Can I delete the installed folder?

• No.

How can I update Windows Subsystem For Android™ to a new version?

• As Explained Installation instructions. Download the latest Windows Subsystem For Android™ Version and replace the content of your previous installation and rerun Install.ps1. Don't worry, your data will be preserved

How do I update Magisk?

• Do the same as updating Windows Subsystem For Android™. Wait for a new MagiskOnWSA release that includes the newer Magisk version, then follow the Installation instructions to update

Can I pass SafetyNet/Play Integrity?

• No. Virtual machines like Windows Subsystem For Android™ cannot pass these mechanisms on their own due to the lack of signing by Google. Passing requires more exotic (and untested) solutions like: https://github.com/kdrag0n/safetynet-fix/discussions/145#discussioncomment-2170917

What is virtualization?

• Virtualization is required to run virtual machines like Windows Subsystem For Android™. Run.bat helps you enable it. After rebooting, re-run Run.bat to install Windows Subsystem For Android™. If it's still not working, you have to enable virtualization in your BIOS/UEFI. Instructions vary by PC vendor, look for help online

Can I remount system partition as read-write?

• No. Windows Subsystem For Android™ is mounted as read-only by Hyper-V. You can, however, modify the system partition by creating a Magisk module, or by directly modifying the system.img file

I cannot adb connect localhost:58526

• Make sure developer mode is enabled. If the issue persists, check the IP address of Windows Subsystem For Android™ on the Settings ---> Developer page and try

  text Copy

  adb connect ip:5555

Magisk online module list is empty?

• Magisk actively removes the online module repository. You can install the module locally or by

  Step 1

  text Copy

  adb push module.zip /data/local/tmp

  Step 2

  text Copy

  adb shell su -c magisk --install-module /data/local/tmp/module.zip

How do I uninstall Magisk?

• Request, using Issues, a Windows Subsystem For Android™ version that doesn't include Magisk from the Releases page. Then follow the Installation instructions

 

  Usage Guides

Install KernelSU Manager: Copy Section

Install BusyBox: Copy Section

Check Integrity Guide: Copy Section

GPU Guide: Copy Section

Sideload Guide: Copy Section

Moving WSA to another drive or partition: Copy Section

LocalHost Loopback Guide: Copy Section

  Having Issues?

Common Issues: Copy Section

  Credits

• Microsoft: For providing Windows Subsystem For Android™ and related files. Windows Subsystem For Android™, Windows Subsystem For Android™ Logo, Windows™ 10 and Windows™ 11 Logos are trademarks of Microsoft Corporation. Microsoft Corporation reserves all rights to these trademarks. By downloading and installing Windows Subsystem For Android™, you agree to the Terms and Conditions and Privacy Policy
• Cinit and the WSAPatch Guide: Many thanks for the comprehensive guide, files and support provided by Cinit and the contributers at the WSAPatch repository. Windows™ 10 Builds in this repo rely on the hard work of this project and hence credit is given where due
• StoreLib: API for downloading WSA
• Magisk: The Magic Mask for Android
• KernelSU: A Kernel based root solution for Android
• MagiskOnWSALocal: Integrate Magisk root and Google Apps into WSA
• WSAOnWin10: Integrate Magisk root and Google Apps into WSA (Windows Subsystem for Android) and make it run on Windows 10 with GitHub Actions

The repository is provided as a utility.

Android is a trademark of Google LLC. Windows™ is a trademark of Microsoft LLC.

---

File: MagiskOnWSA/DLL/docs/Fixes/Fix Error 0x80073CF0.md Copy Chapter

Issue: Error 0x80073CF0 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to many factors such as corruption of files when downloading the .zip/.7z files or extracting from the .zip/.7z files. This can be also caused if the folder name is too long (This is the case as MagiskOnWSA tends to generate a long string for the .zip/.7z file and the folder within the archive.)

Solution Copy Chapter

1. Ensure the partition/drive you are installing from is NTFS

2. Redownload WSA Build .zip/.7z file from the Releases page (sometime the files can be corrupted during download and extraction)

3. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing (For example: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon ----> WSAArchive2XXX)

4. Extract the .zip or .7z archive (depends on the release) using 7-zip or a proper archive tool and not the built in Windows archive extractor

5. Rename the extracted folder(s) to a shorter name, which can be anything to your choosing

For example:

• Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon
• After: WSAExtracted2XXX

6. Ensure that 'Run.bat' is run as Administrator

Hope this works for you!

File: MagiskOnWSA/DLL/docs/Fixes/Fix Error 0x80073CF6.md Copy Chapter

Issue: Error 0x80073CF6 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to many factors that is preventing the app from being registered. Although there is no definite solution, we can try these steps to try to fix the problem

This installation issue may also arise in systems that are using Modified Windows OSes such as ReviOS, Tiny10/11, etc. This is due to the fact that these OSes have been modified to remove certain features that are deemed unnecessary. This may cause issues with the installation of WSA.

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered
In E:\WSA\Install.ps1:102 Character:1
+ Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion

   + CategoryInfo          : WriteError: (E:\WSA\AppxManifest.xml:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Prequisite Steps: Copy Chapter

1. Ensure the partition/drive you are installing from is NTFS

2. Redownload WSA Build .zip (sometime the files can be corrupted during download and extraction)

3. If you have installed WSA prior, make sure that it has been uninstalled and delete all folders containing "WindowsSubsystemForAndroid" from the following directories/paths and the subdirectories within:

• C:\ProgramData\Microsoft\Windows\AppRepository

• C:\ProgramData\Microsoft\Windows\WindowsApps

• %localappdata\ProgramData\Packages

4. Restart your Computer

If the issue has been fixed, then there is no need to follow through the rest of the guide.
However, if you have the same issue, it is vital that you obtain the logs and try to decipher what is causing the error

To obtain the logs (admin privilege required):

1. Open a PowerShell window and change working directory to your Windows Subsystem For Android™ directory.

2. Run the command below in PowerShell. This should fail with an ActivityID, which is a UUID required for the next step.

   powershell Copy

   Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml

3. Run the command below in PowerShell. This should print the log of the failed operation.

   powershell Copy

   Get-AppPackageLog -ActivityID <UUID>

There are various causes that lead to error 0x80073CF6 Find the fix that matches the error presented in the logs obtained from the instructions above Copy Section

Issue 1: 0x800706D9 "There are no more endpoints avaliable from endpoint mapper" Copy Chapter

**Windows Firewall** Copy Section

1. Ensure that Windows Firewall is on and is working with "Recommended Settings" being enabled

2. Ensure that Windows Firewall service is running. If not, enable it.

3. Restart your PC

Other Firewalls Copy Section

1. Ensure that your Firewall is on and is working with "Recommended Settings" being enabled

2. Ensure that your Firewall is not blocking or preventing new entries

3. Restart your PC

Issue 2: 0x80073B06 "Initial screen image for the current application context cannot be recognized" Copy Chapter

Installing MagiskOnWSA...
Add AppxPackage: Deployment failed due to HRESULT: 0x80073CF6, unable to register the package.
AppxManifest.xml (24,27): Error 0x80073B06: Unable to install or update package MicrosoftCorporateII.WindowsSubsystemForAndroid_ 8wekyb 3d8bbwe because the initial screen image for the current application context cannot be recognized. The application context may include specific language, DPI, contrast, or other special conditions. If you cannot recognize a context specific splash screen image, add a splash screen image to use as the default setting. Note: For additional information, look for [ActivityId] 94c065bb-5a2a-0004-129b-c1942a5ad901 in the event log, or use the command line Get AppPackageLo g - ActivityID 94c065bb-5a2a-0004-129b-c1942a5ad901 in the location D:  WSA  WSA  Install.ps1:106 Character: 1
+ Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion  ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : WriteError: (D:\WSA\WSA\AppxManifest.xml:String) [Add-AppxPackage], IOException
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Solution: Copy Section

1. If you encounter this problem when installing from a build built using MagiskOnWSALocal or WSA-Script, try deleting the previously built builds and rebuild. Make sure to delete and reclone the git repo if you are building using MagiskOnWSALocal.

Or

2. If you encounter this problem when installing using prebuilt builds from Releases from this repo, try redownloading the latest build. If the issue persists, report to the Issues and I will be happy to assist you

Hope these fixes work for you!

File: MagiskOnWSA/DLL/docs/Fixes/Fix Error 0x80073CF9.md Copy Chapter

Issue: Error 0x80073CF9 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to many factors such as corruption of files when downloading the .zip files or extracting from the .zip files. This can be also caused if the folder name is too long (This is the case as MagiskOnWSA tends to generate a long string for the .zip file and the folder within the archive.)

Solution Copy Chapter

1. Ensure the partition/drive you are installing from is NTFS

2. Redownload WSA .zip file on Release page (sometime the files can be corrupted during download and extraction)

3. Rename the .zip folder to a shorter name, which can be anything to your choosing (WSA_2xxx.xxxxx.xx.x_x64_Release-Nightly-with-magisk-xxxxxxx-MindTheGapps-13.0-as-Pixel-5-RemovedAmazon ----> WSAArchive2XXX)

4. Extract the .zip using WinRAR or a proper archive tool and not the built in Windows .zip extractor

5. Rename the extracted folder(s) to a shorter name, which can be anything to your choosing

For example:

• Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon
• After: WSAExtracted2XXX

6. Ensure that 'Run.bat' is run as Administrator

Hope this works for you!

File: MagiskOnWSA/DLL/docs/Fixes/Fix Error 0x80073CFB.md Copy Chapter

Issue: Error 0x80073CFB when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to the fact that "the provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details."

Solution Copy Chapter

1. Go to %LOCALAPPDATA%/Packages/, and make sure that the folder MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe is deleted. (If it does not exist, move on to Step 2.)

2. Open Powershell (as Admin) and run the following command:

Get-AppxPackage -Name "MicrosoftCorporationII.WindowsSubsystemForAndroid" -AllUsers | Remove-AppxPackage -AllUsers

3. Delete all folders related to WSA (expect the .zip files for WSA Builds), which include folders extracted for WSA installation.

4. Re-extract and re-run Run.bat

The issue should now be fixed

File: MagiskOnWSA/DLL/docs/Fixes/Fix Error 0x80073CFD.md Copy Chapter

Issue: Error 0x80073CFD when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused by having a Windows 10 Build that is too old to run WSA and hence the installer halts and presents the error, as shown below

Registering AppxManifest.xml... 
Add-AppxPackage : Deployment failed with HRESULT: 0x80073CFD, 
Prerequisite for an install could not be satisfied. Windows cannot install package MicrosoftCorporationII.WindowsSubsystemForAndroid_2301.40000.7.0_x64__8wekyb3d8bbwe because this package is not compatible with the device. 
The package requires OS version 10.0.19044.2604 or higher on the Windows.Desktop device family. 
The device is currently running OS version 10.0.19043.2364. 
NOTE: For additional information, look for [ActivityId] 8b8599fb-55c1-0002-338b-868bc155d901 in the Event Log or use the command line 
Get-AppPackageLog -ActivityID 8b8599fb-55c1-0002-338b-868bc155d901

Solution: Copy Chapter

The Solution is simple: Copy Section

Using the Microsoft Guide, update Windows 10 to the latest version

Or

Using the Windows 10 Update Assistant, update Windows 10 to the latest version

File: MagiskOnWSA/DLL/docs/Fixes/Fix Error 0x80073D10.md Copy Chapter

Issue: Error 0x80073D10 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused when your are trying to install the incorrect WSA package for your CPU Archetecture. For example, you are mistakenly trying to install the arm64 package on your x64 system.

Solution Copy Chapter

1. To ensure that you download the correct package for your CPU archtecture, go to the Release of this repository then check again

2. Click on the package matching your Operating System (OS) and CPU Archetecture

3. Download then install the package by follow the Installation guide in README.md file

File: MagiskOnWSA/DLL/docs/Fixes/FixInstallps1.md Copy Chapter

[Binary file]

File: MagiskOnWSA/DLL/docs/Fixes/FixInternet.md Copy Chapter

Issues: Copy Chapter

No Internet Copy Section

Solution: Copy Chapter

These will be split into multiple solutions due to the different causes of the problem of no internet on Windows Subsystem for Android (WSA) and Windows Subsytem for Linux (WSL)

Fix #1: Uninstalling Hyper-V Network Adapters

Some Hyper-V Network Drivers may be interferring with WSA or WSL

⚠️ Carry these instructions out with caution. ⚠️

⚠️ I do not take responsibility for any damage caused ⚠️

**Step 1: Open Device Manager**

1. Using Search or Win + X, open Device manager

**Step 2: Show Hidden Device**

3. Press on "View"
4. Select "Show hidden devices"

**Step 3: Uninstalling All Hyper-V Network Adapter**

5. Select each driver that has "Hyper-V" in its name
6. Right-Click and select "Uninstall Driver" for each of these drivers

**Step 4: Restart Windows**

Fix #2: Checking Firewall Settings

Sometimes Windows Firewall and other Firewall tools and software may be the cause of internet issues. It is therefore important that we check them if we are facing issues with internet on WSA.

Users with Windows Firewall

1. Open Windows Firewall by pressing the Windows Key and "R" key, Open Run

2. Type WF.msc, and then select OK. See also Open Windows Firewall

3. Go to the "Inbound Connection" tab

4. Find the entries in the list that state: "Windows Subsystem for Android™"

5. Confirm that these entries are Enabled and "Action" is set to "Allow" for both UDP and TCP for all entries (as shown above)

6. Now, go to the "Outbound Connection" tab

7. Find the entries in the list that state: "Windows Subsystem for Android™"

5. Confirm that these entries are Enabled and "Action" is set to "Allow" for both UDP and TCP for all entries (as shown above)

You may not have as many entries for "Windows Subsystem for Android™", as shown in the screenshots provded. These are just for illustration purposes and Firewall entries may look different on your device.

Antivirus Users

It is a known issue that some antivirus firewall such as those built-in to ESET, Bitdefender, AVG and many others, can prevent the internet for Windows Susbsystem for Android (WSA) from working.
It is highly recommended to disable the firewall provided by these Antivirus/Antimalware tools and fallback to Windows Firewall, to see if the internet starts working.

Source: From this

---

Fix #3: Changing Android DNS Settings

1. Open Windows Firewall by pressing the Windows Key and "R" key, Open Run

2. Type wsa://com.android.settings, and then select OK.

3. Wait for Android Settings to load and open.

4. In Android Settings, click on the "Network and Internet" Section.

5. In the "Network and Internet" Section, select "Private DNS" .

6. In the "Select Private DNS mode", click on "Private DNS provider hostname".

7. In the entry box below, type "dns.google" and click save.

8. Now click on the "Internet" section and click on VirtWifi.

9. Click on "Disconnect".

10. Then click on "Connect".

Your Internet should now be fixed!

---

Fix #4: Enabling and Disabling Advanced Networking from WSA Settings

1. Go to the Start Menu and search for Windows Subsystem for Android™
2. Depending on your WSA version, the Advanced Networking setting is located in different places witin the WSA Settings app

• For 2305 and newer builds, you must go to "Advanced settings" and then to "Experimental features"
• For 2304 and older builds, this setting is located in the "System" tab/ main screen when you open the Settings app

3. Make sure that if Advanced Networking is enabled, you disable it as this may be causing issues with the internet

This should fix the internet if Advanced Networking was on and the internet was not working due to this

---

File: MagiskOnWSA/DLL/docs/Fixes/FixPathTooLong.md Copy Chapter

Issue: Error stating that "Path is too long" when extracting files from .zip archive, needed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused if the folder name is too long. This is the typically the case as MagiskOnWSALocal script tends to generate a long string for the .zip file and the folder within the archive.

Solution Copy Chapter

The solution is simple, all you have to do is:

1. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

2. Rename the extracted folder to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

File: MagiskOnWSA/DLL/docs/Fixes/FixVirtError.md Copy Chapter

Issues: Copy Chapter

Solution: Copy Chapter

You may encounter this problem, even if Virtualization is enabled on your PC (in the BIOS) and shows up as enabled in Task Manager (as seen below) and Virtual Machine Platform + Windows Hypervisor Platform is Enabled. The solution is:

1. Remove WSA: Right clicking on "Windows Subsystem for Android™ Settings" and pressing uninstall + Deleting the extracted WSA (MagiskOnWSA/WSABuilds) folder that you extracted and installed from.

2. Go to "Turn Windows features on and off" and if any of these features below are enabled, DISABLE THEM.

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Subsystem for Linux

3. Restart your PC

4. Boot into your BIOS, and DISABLE Virtualization.

   • Click here for a guide for Windows 11
   • Click here for a guide for Windows 10

5. Ensure that you have Control Flow Guard enabled in Windows Security > Apps & browser control > Exploit protection. This is a known issue that can prevent WSA from starting

6. In registry editor (regedit), go to “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends"

   Change the value of “Start” from “3” to “0”

Note
You can change it back to 3, if it makes no difference

7. Then in CMD (Run as Adminstrator), paste:

bcdedit /set hypervisorlaunchtype auto

8. ENABLE the features that you disabled in Step 2 and restart a second time.

9. Boot into your BIOS, and ENABLE Virtualization.

   • Click here for a guide for Windows 11
   • Click here for a guide for Windows 10

10. Restart the Computer

11. Reinstall WSA by running Run.bat

Hope this works for you!

File: MagiskOnWSA/DLL/docs/Fixes/Google Play Issues.md Copy Chapter

Issue 1: After signing in to your Google Account from the Play Store App, Play Store keeps crashing Copy Chapter

Preface: Copy Section

This issue will prevent you from opening Play Store and effectively prevent the function of MindTheGapps/OpenGapps. This issue may usually occur after signing in. Known cases indicate that this issue is pretty common on newer hardware (12th or 13th Gen Intel Processors, for example)

Solution: Copy Chapter

Step 1.

Open Android Settings by pressing the Windows Key and "R" key, Open Run

Step 2.

Type wsa://com.android.settings, and then select OK.

Step 3.

Wait for Android Settings to load and open.

Step 4.

In Android Settings, click on the "Apps" Section and then click on "All Apps".

Step 5.

In the "All Apps" Section, find the "Google Play Services" app .

Step 6.

Click on the "Google Play Services" app, which should open a page with various different options for the app ("Permissions", "Notification", "Storage and Cache" etc.)

Step 7.

Click on "Storage and Cache"

Step 8.

Find the "Manage Space" button and click on it, which should popup a window reading "Google Play services storage"

Step 9.

Click on "Clear All Data" and done

Issue 2: Could not sign-in. There was a problem connecting to play.google.com Copy Chapter

Preface: Copy Section

This issue will prevent you from signing into Play Store and effectively prevent the function of MindTheGapps/OpenGapps. This issue may usually occur after updating. Known cases have occured after updating from a non Google Apps WSA build to a Google Apps build

Solution: If you are using VPN, please disconnect it because VPN may make WSA fail to connect to VirtWifi. Copy Chapter

File: MagiskOnWSA/DLL/docs/Fixes/InstallPs1FailedToUpdate.md Copy Chapter

Issues: Install.ps1 Failed To Update Copy Chapter

Solution: Copy Chapter

1. Run Powershell with this command:

PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1

File: MagiskOnWSA/DLL/docs/Fixes/InternetSecuritySettingsBlock.md Copy Chapter

Issue: Error stating that "Your Internet security settings prevented one or more files from opening" when trying to run `Install.ps1` or `Run.bat` to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused if the folder name is too long. This is the typically the case as MagiskOnWSALocal script tends to generate a long string for the .zip file and the folder within the archive.

Solution Copy Chapter

The solution is simple, all you have to do is:

1. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

2. Rename the extracted folder to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

File: MagiskOnWSA/DLL/docs/Fixes/Keyboard Is Not Working.md Copy Chapter

Issue: Keyboard Does Not Work Copy Chapter

Preface: Copy Section

This issue will prevent you from using your keyboard on WSA

Solution: Copy Chapter

1. ***Open Run by pressing the Windows Key and R***

2. ***Type in services.msc in the box and then select OK***

3. ***Search for Touch Keyboard and Handwriting Panel***

4. ***Enable it by switching startup type to automatic***

5. ***Click apply***

6. ***Restart your computer.***

File: MagiskOnWSA/DLL/docs/Fixes/MissingIcons.md Copy Chapter

Issue: Icons have disappeared or have turned white after updating WSA or after restarting your computer Copy Chapter

Preface: Copy Section

This looks like a bug in the WSA itself and the icons can be restored by the following steps.

Solution Copy Chapter

1. Backup userdata.vhdx from %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx

2. Uninstall WSA by Following this guide

3. Remove the two lines in Install.ps1 that automatically launches Magisk and Play Store after the installation is finished

function Finish {
    Clear-Host
    Start-Process "wsa://com.topjohnwu.magisk"
    Start-Process "wsa://com.android.vending"
}

4. Install WSA

5. Restore userdata.vhdx to %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx

6. Start WSA

Warning
Do not start WSA before restoring user data.

File: MagiskOnWSA/DLL/docs/Fixes/TargetMachineActivelyRefusedConnection.md Copy Chapter

Issue: Error: No connection could be made because the target machine actively refused it (10061) Copy Chapter

Preface: Copy Section

This issue occurs when you are either using a sideloading application such as [WSA-Sideloader](https://github.com/infinitepower18/WSA-Sideloader) or [WSAPacman](https://github.com/alesimula/wsa_pacman), or when you try to connect to a device using ``adb.exe`` via [Android SDK Platform Tools](https://developer.android.com/tools/releases/platform-tools). This issue arises due to an issue with the inability of Hyper V to reserve port 58526 causing the issue, as seen below.

cannot connect to ||127.0.0.1:58526:|| No connection could be made because the target machine actively refused it. (10061)

Solution Copy Chapter

This is a bug with the subsystem itself, restarting the PC will usually fix it. But, if you still get this error, try these steps:

• _**1. Make sure WSA is turned off and disable WSA autostart in Task Manager ---> Startup Apps before proceeding**_

• _**2. Disable Hyper-V (if it is enabled) using the command**_

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

• **3. Reboot your PC**

• _**4. Reserve port 58526 so Hyper-V doesn't reserve it back using the command**_

netsh int ipv4 add excludedportrange protocol=tcp startport=58526 numberofports=1

• _**5. Re-enable Hyper-V (if it was previously enabled) using the command `dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All` and reboot your PC**_

Hope this works for you!

File: MagiskOnWSA/DLL/docs/Fixes/WSA Does Not Load After Install + No Splashscreen.md Copy Chapter

Issue: Windows Subystem for Android (WSA) is unable to run any apps and there is no splashscreen (when opening the Files app from the settings) and no icons for Android apps. Copy Chapter

Preface: Copy Section

Why this occurs is unknown. However, after multiple attempts trying to fix this issue, a solution was found.

https://github.com/MustardChef/WSABuilds/assets/68516357/a9690842-5159-470a-b472-5990faabeac8

Solution Copy Chapter

Rename the extracted folder to a shorter name, which can be anything to your choosing.

• Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

• After: WSAArchive2XXX

https://github.com/MustardChef/WSABuilds/assets/68516357/626ec699-6f74-40ff-94fb-26fbe1c4f182

**Hope this works for you!** Copy Chapter

File: MagiskOnWSA/DLL/docs/Fixes/WSA Settings App Crashes + Android Apps Do Not Load After Installation.md Copy Chapter

Issue: Windows Subystem for Android (WSA) Settings app crashes after installation, when opened, and you are unable to run any apps. Copy Chapter

Preface: Copy Section

Why this occurs is unknown. However, after multiple attempts trying to fix this issue, a solution was found.

https://github.com/MustardChef/WSABuilds/assets/68516357/7333e8b4-7c09-4032-b816-47fc0d83767b

Solution Copy Chapter

Rename the extracted folder to a shorter name, which can be anything to your choosing.

• Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

• After: WSAArchive2XXX

https://github.com/MustardChef/WSABuilds/assets/68516357/7a33df5b-e68b-43b1-9365-9c4d7ff5c2db

**Hope this works for you!** Copy Chapter

File: MagiskOnWSA/DLL/docs/Fixes/WSA Stopped Working.md Copy Chapter

Issues: WSA Stopped Working! Copy Chapter

***You may encounter this problem. WSA has been working fine for you, but all of a sudden, it breaks/ stops working. You are distraught. What do you do, when WSA beloved had been borked.***

Solution: Copy Chapter

1. Go to "Turn Windows features on and off" and if any of these features below are enabled, DISABLE THEM.

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Subsystem for Linux

2. Restart your PC

3. Boot into your BIOS, and DISABLE Virtualization.

• Click here for a guide for Windows 11
• Click here for a guide for Windows 10

4. Ensure that you have Control Flow Guard enabled in Windows Security > Apps & browser control > Exploit protection. This is a known issue that can prevent WSA from starting

5. In registry editor (regedit), go to “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends"

   Change the value of “Start” from “3” to “0”

Note
You can change it back to 3, if it makes no difference

6. Then in CMD (Run as Adminstrator), paste:

bcdedit /set hypervisorlaunchtype auto

7. ENABLE the features that you disabled in Step 1 and restart a second time.

8. Boot into your BIOS, and ENABLE Virtualization.

• Click here for a guide for Windows 11
• Click here for a guide for Windows 10

9. Restart the Computer

10. Try re-running WSA by running Run.bat or via the Windows Subsystem for Android Settings app

Hope this works for you!

File: MagiskOnWSA/DLL/docs/Guides/ADB-Sideloading.md Copy Chapter

Sideloading APKs in to Windows Subsystem for Android

Setting up ADB to work with WSA Copy Chapter

• Launch Windows Subsystem for Android.
• Here, click on Advanced Settings and then enable Developer mode by clicking on the toggle button.
• Take note of IP address and port shown in the Developer mode section.
• Launch Windows Terminal and make sure ADB is installed (install ADB).
• Use command adb pair 127.0.0.1:58526 to pair ADB with WSA.
• In Wireless debugging window, see Device name and under it IP address and port.
• Use command adb connect 127.0.0.1:58526 to connect WSA with ADB.

Once this is done, use command adb devices to make sure that WSA is connected.

Installing APKs using ADB Copy Chapter

Now you can install any app you want, but I personally suggest installing a web browser and a file manager first.

• Download the APK.
• Open File Explorer, right click on downloaded APK and tap on Copy as path.
• Launch Windows Terminal.
• Use adb install <file path> to install the APK.
  [P.S. You can right click to paste in Terminal]

After installation using ADB Copy Chapter

You can now open the web browser you installed in Android, and download and install Aurora Store like you do on any Android device - normally sideloading APK without using ADB.

A list of suggested apps to install on WSA: Copy Section

• microG: A free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries.
• Aurora Store: an app store that lets you download apps from Google Play without a Google account.
• MiX: MiXplorer mix of explorers (SD, FTP, Lan, Cloud and other storage explorers) is a fast, smooth, beautiful, reliable and full-featured file manager with a simple and intuitive user interface.
• Bromite: A Chromium fork with support for ad blocking and enhanced privacy.

File: MagiskOnWSA/DLL/docs/Guides/BusyBox.md Copy Chapter

Guide: How to install BusyBox Copy Chapter

Preface: Copy Section

Since Magisk has BusyBox built-in already, this proceedure is very simple

Process Copy Chapter

Step 1: Copy Section

Using an Android browser downloaded though the Play Store/sideloaded into WSA, download the following Magisk Module to install and symlink BusyBox with its applets to the Magisk built-in busybox binary. No need to do it manually or to get a Custom Build.

Step 2: Copy Section

Through Magisk Manager, install the Magisk module .zip file

Step 3 (Optional): Copy Section

You can then test if BusyBox is working by either using a Root Checker:

or by using ADB Shell and:

adb shell
su
busybox | head -1

File: MagiskOnWSA/DLL/docs/Guides/ChangingGPU.md Copy Chapter

Guide: Changing the GPU used by Windows Subsystem For Android™ Copy Section

1. Open up Windows Subsystem For Android™ Settings --> Either by going to the Start Menu and searching for it or by using the Search feature

2. Make sure to turn off Windows Subsystem For Android™ by pressing Turn off in the Turn off Windows Subsystem For Android™ tab

3. In Windows Subsystem For Android™ Settings select the Graphics and Performance Tab

4. Click on the selection for GPU used for apps for Android™ and select the GPU that you would like Windows Subsystem For Android™ to use.

File: MagiskOnWSA/DLL/docs/Guides/Checksum.md Copy Chapter

Check integrity of downloaded file

**1. Press Win + X on your keyboard and select Windows™ Terminal (Admin) or Powershell (Admin) depending on the version of Windows™ you are running** Copy Section

**2. Input the command below and press enter, replacing {X:\path\to\your\downloaded\archive\package} including the {} with the path of the downloaded archive package** Copy Section

cd "{X:\path\to\your\downloaded\archive\package}"

**3. Input the command below and press enter, replacing WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon with the name of the archive package** Copy Section

certutil -hashfile "WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon" SHA256

For PowerShell:

(Get-FileHash -Path "WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon" -Algorithm SHA256).Hash

**4. Compare the SHA256 output with ones at [Release](https://github.com/YT-Advanced/WSA-Script/releases/latest) or in the `sha256-checksum.txt` (if you download artifact from the Custom Build task).** Copy Section

• If package don't have the same SHA-256 Hash, please download then check again.
• If package have the same SHA-256, install it by Following this guide

File: MagiskOnWSA/DLL/docs/Guides/KernelSU.md Copy Chapter

Install KernelSU Manager

Text Guide Copy Chapter

1. Connect to WSA with ADB
2. Run the following command:
   text Copy

   adb shell ksuinstall

If the installation completes successfully, the KernelSU Manager will launching.

File: MagiskOnWSA/DLL/docs/Guides/LocalHostLoopback.md Copy Chapter

Guide: LocalHost Loopback Copy Chapter

Preface: You want to connect WSA to the localhost (Windows 11 hosting machine) or to a development server I run on Windows 11 or any such scenario where you would want to connect to the Windows 11 localhost, but are unable to

Note: Localhost Loopback has now been officially added to the update 2308 of WSA, and so this guide is probably outdated now. Copy Section

Process: Copy Chapter

1. Run PowerShell as administrator

2. Execute

Set-NetFirewallHyperVVMSetting -VMCreatorId '{9E288F02-CE00-4D9E-BE2B-14CE463B0298}' -LoopbackEnabled True

3.Execute

New-NetFirewallHyperVRule -DisplayName LoopbackAllow -VMCreatorId '{9E288F02-CE00-4D9E-BE2B-14CE463B0298}' -Direction Inbound -Action Allow -LocalPorts [PORT]

(replacing [PORT] with the port you're trying to expose)

File: MagiskOnWSA/DLL/docs/Guides/MoveToExtDrive.md Copy Chapter

Guide: Moving/Installing Windows Subsystem For Android™ (WSA) to another partition or disk Copy Chapter

Preface: Copy Section

WSA can take up a lot of storage space, hence you want to move it to another partition or disk with more space. This guide goes through a method by which you can install WSA from another disk and to store the data in that drive (instead of `%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe`).

Prerequisites: Copy Section

• The partition/ disk that you want to move/install Windows Subsystem For Android™ to, MUST be NTFS
• Recommended that both disks, C:/ and the disk/partition that you want to install (move) WSA on (to), are SSDs
  • HDDs may work, but performance issues may arise
• Basic knowledge on Command Prompt (CMD) usage
• There must be enough space on the disk/partiton that you are installing/moving WSA to (recommended 20GB, as the VHDX can become very large in size)

Note

If you want to preseve your data, make a backup of the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx file. After uninstalling, copy the VHDX file back to the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache folder.

Process: Copy Chapter

• Step 1: Remove all previous installations from WSABuilds or official WSA Releases Copy Section

  • To remove WSA installed through WSABuild:

    • 1.) Make sure that Windows Subsystem For Android™ is not running

    • 2.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

    • 3.) Delete the WSA folder that you extracted and Run.bat was run from to install WSA (MagiskOnWSA folder)

    • 4.) Go to %LOCALAPPDATA%/Packages/ and delete the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe

      • If you get an error that states that the file(s) could not be deleted, make sure that WSA is turned off

  • To remove WSA installed from the Microsoft Store:

    • 1.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

• Step 2: Install WSA from the desired partition Copy Section

  • 1.) Download the latest WSA Build according to Windows Version and CPU Archtecture from Release.
  • 2.) Extract to the desired partition or drive
  • Using the same process as detailed in Installation
  • 3.) Open the extracted folder and run Run.bat

• Step 3: Moving the AppData (VHDX + data) from your Windows drive (C:\) to the desired partition/drive Copy Section

  • 1.) Go to %LOCALAPPDATA%\Packages\ and copy the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe to the desired drive/partition, making sure to delete the folder from %LOCALAPPDATA%\Packages\ after copying

  • 2.) Open Command Prompt (Admin) through Windows Terminal (Admin) or directly and run the command:

mklink /J "%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe" "Location_Of_Folder_In_Other_Drive"

Replacing Location_Of_Folder_In_Other_Drive with the location of the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe, copied to the desired to the drive/partition in 1st point of Step 3

• Step 4: Testing if everything is working Copy Section

  • Run Windows Subsystem For Android™ Settings
    • If it crashes, you have made a mistake whilst following the guide. Try following it again.

File: MagiskOnWSA/DLL/docs/Guides/Sideloading.md Copy Chapter

Guide: Sideloading APKs Copy Chapter

This guide covers the four different methods of sideloading and installing APKs (from Windows) into Windows Subsystem For Android™ Copy Section

File: MagiskOnWSA/DLL/docs/Guides/WSA-Sideloader.md Copy Chapter

WSA Sideloader Usage Guide

With WSA Sideloader, you can install any APK file onto WSA, as well as XAPK, APKM and APKS files.

This guide will show you how to use it.

How to Download and Install WSA-Sideloader Copy Chapter

You can download WSA Sideloader in 3 different ways:

Setup Copy Chapter

Step 1. Once installed, you should see this screen:

Note :
If you get a message that says WSA is not installed, check that you have downloaded and installed WSA correctly as per the WSABuilds instructions.

Step 2. Next, open WSA Settings from the start menu or by typing wsa-settings:// in your browser's address bar, select Developer and enable Developer mode.

Step 3. Now, you can click the Browse button to select your APK file. You can also double click a file in File Explorer to automatically open WSA Sideloader with the APK file already selected.

Step 4. The first time you install an APK, it will ask to allow ADB debugging. Allow it and attempt the installation again. Check the always allow box if you don't want to manually accept the permission every time you install an app.

Step 5. It should take a few seconds to install the APK. Once it says The application has been successfully installed, you can click Open app. Bundle files may take longer depending on the file size.

Note :
If WSA is off, WSA Sideloader will start it for you. After 30 seconds, the installation will automatically continue.

You can find all your installed WSA apps on the start menu, as well as via the "Installed apps" button in WSA Sideloader:

Updating WSA Sideloader Copy Chapter

From time to time, there may be updates that improve the reliability of the app, as well as ensuring it works properly with future releases of WSA.

Therefore, it's highly recommended you keep it up to date.

• If you installed WSA Sideloader using MS Store, you can update the app via the store.
• If you installed through other methods, the sideloader will notify you of an update the next time you launch it.

Troubleshooting Copy Chapter

If you get an error like the one below, check that you have allowed the ADB authorization and enabled Developer Mode. Also try disabling and enabling USB debugging under manage developer settings as that can sometimes fix issues with the ADB connection.

If you get a message saying No connection could be made because the target machine actively refused it, follow this guide

File: MagiskOnWSA/DLL/docs/Guides/WSAFiles.md Copy Chapter

Sideloading using the Files app

Starting with WSA version 2305, you can sideload APK files using the Files app. This guide will show you how.

NOTE:
This guide is only applicable for WSA versions 2305 and above. If you're using an older version, you will need to use ADB or one of the listed APK installers.

Setup Copy Chapter

1. Open the Windows Subsystem for Android app, go to Advanced Settings and enable share user folders found under experimental features. Then select the folder that you would like to share by clicking on "Change folder".

2. Go to the "System" section and open the Files app.

3. Click on Subsystem for Android, followed by Windows to browse through your Windows files.

4. Click the APK you want to install and choose package installer if it asks. Agree to the warnings and then click install.

NOTE:
If you're facing problems, try disabling Block installation of malicious apps in the WSA app.

After installation Copy Chapter

Once installed, you can launch the sideloaded app from the Start Menu.

If you want to install bundle files, such as .apkm or .xapk, you can install [SAI](https://apkpure.com/split-apks-installer-sai/com.aefyr.sai) and use that to install bundle files, as well as regular APKs.

File: MagiskOnWSA/DLL/docs/Guides/WSAPacman.md Copy Chapter

WSAPacman

Step 1:   Download and install WSA Pacman

Step 2:   Go to Windows Subsystem for Android → Developer and turn on Developer mode.

Warning:

You have to give WSAPacman, ADB Debugging permission.

Issues and Solutions Copy Chapter

If the "Install" button is greyed out while installing apk

Solution: Open WSAPacman and turn on WSA from there.

If WSAPacman states that the "Installation timed out":

Solution: Wait for a few minutes, and see if the app is installed and shows in the Start Menu. If not retry the installation In the case that nothing works, report this to the [WSAPacman Github](https://github.com/alesimula/wsa_pacman)

File: MagiskOnWSA/DLL/scripts/requirements.txt Copy Chapter

requests
packaging

File: MagiskOnWSA/docs/README.md Copy Chapter

Magisk on WSA (with Google Apps)

:warning: Magisk on WSA will no longer be available after March 5, 2025. Learn more.

:warning: For fork developers: Please don't build using GitHub Actions, as GitHub will count your forked GitHub Actions usage against this upstream repository, which may cause this upstream repository gets disabled by GitHub staff like MagiskOnWSA because of numerous forks building GitHub Actions, and counting the forks' Action usage against this upstream repository.

Support for generating from these systems Copy Chapter

• Linux (x86_64 or arm64)

  The following dependencies are required:

  DistrOS
  Debian	python3 aria2 unzip sudo	whiptail	python3-venv	python3-pip	p7zip-full
  openSUSE Tumbleweed	Same as above	dialog	python3-venvctrl	Same as above	Same as above
  Arch	Same as Debian	libnewt	Same as Debian	python-pip	p7zip

  The python3 library requests is used.

  Python version ≥ 3.7.2.

  • Recommended use

    • Ubuntu (You can use WSL2)

      Ready to use right out of the box.

    • Debian (You can use WSL2)

      Ready to use right out of the box.

    • openSUSE Tumbleweed (You can use WSL2)

      Ready to use right out of the box.

    run.sh will handle all dependencies automatically.

    No need to type any commands.

Features Copy Chapter

• Integrate Magisk and GApps in a few clicks within minutes
• Keep each build up to date
• Support both ARM64 and x64
• Support MindTheGapps
• Remove Amazon Appstore
• Fix VPN dialog not showing (use our VpnDialogs app)
• Add device administration feature
• Unattended installation
• Automatically activates developers mode in Windows 11
• Update to the new version while preserving data with a one-click script
• Merged all language packs

Text Guide Copy Chapter

1. Star (if you like).

2. Clone the repo to local:

   bash Copy

   git clone https://github.com/LSPosed/MagiskOnWSALocal.git --depth 1

3. Run cd MagiskOnWSALocal.

4. Run ./scripts/run.sh.

5. Select the WSA version and its architecture (mostly x64).

6. Select the version of Magisk.

7. Choose which brand of GApps you want to install:

   • MindTheGapps

     There is no other variant we can choose.

8. Select the root solution (none means no root).

9. If you are running the script for the first time, it will take some time to complete. After the script completes, two new folders named output and download will be generated in the MagiskOnWSALocal folder. Go to the output folder. While running the ./run.sh script in the step 3, if you selected Yes for Do you want to compress the output? then in output folder you will see a compressed file called WSA-with-magisk-stable-MindTheGapps_2207.40000.8.0_x64_Release-Nightlyor else there will be folder with the WSA-with-magisk-stable-MindTheGapps_2207.40000.8.0_x64_Release-Nightly. If there is a folder open it and skip to step 10. NOTE: The name of compressed file or the folder generated in the output folder may be different for you. It will be dependent on the choices made when executing ./run.sh.

10. Extract the compressed file and open the folder created after the extraction of the file.

11. Here look for file Run.bat and run it.

    • If you previously have a MagiskOnWSA installation, it will automatically uninstall the previous one while preserving all user data and install the new one, so don't worry about your data.
    • If you have an official WSA installation, you should uninstall it first. (In case you want to preserve your data, you can backup %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx before uninstallation and restore it after installation.)
    • If the popup windows disappear without asking administrative permission and WSA is not installed successfully, you should manually run Install.ps1 as Administrator:
      1. Press Win+x and select Windows Terminal (Admin).
      2. Input cd "{X:\path\to\your\extracted\folder}" and press enter, and remember to replace {X:\path\to\your\extracted\folder} including the {}, for example cd "D:\wsa"
      3. Input PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1 and press Enter.
      4. The script will run and WSA will be installed.
      5. If this workaround does not work, your PC is not supported for WSA.

12. Magisk/Play Store will be launched. Enjoy by installing LSPosed-Zygisk with Zygisk enabled or Riru and LSPosed-Riru.

FAQ Copy Chapter

• Can I delete the installed folder?

  No.

• How can I update WSA to a newer version?

  1. Update build scripts:

     bash Copy

     git pull

     For more usage of git, referred to https://git-scm.com/book

  2. Rerun the script, replace the content of your previous installation and rerun Install.ps1. Don't worry, your data will be preserved.

• How can I get the logcat from WSA?

  %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalState\diagnostics\logcat

• How can I update Magisk to a newer version?

  Do the same as updating WSA.

• How to pass Play Integrity (formerly known as SafetyNet)?

  Like all the other emulators, no way.

• Virtualization is not enabled?

  Install.ps1 helps you enable it if not enabled. After rebooting, rerun Install.ps1 to install WSA. If it's still not working, you have to enable virtualization in BIOS. That's a long story so ask Google for help.

• How to remount the system as read-write?

  No way in WSA since it's mounted as read-only by Hyper-V. You can modify the system by making a Magisk module. Or directly modify the system.img. Ask Google for help.

• I cannot adb connect localhost:58526, what to do?

  Make sure developer mode is enabled. If the issue persists, check the IP address of WSA on the setting page and try adb connect ip:5555.

• Why the Magisk online module is empty?

  Magisk actively removes the online module repository. You can install the module locally or by adb push module.zip /data/local/tmp and adb shell su -c magisk --install-module /data/local/tmp/module.zip.

• Can I use Magisk v23.0 stable or a lower version?

  No. Magisk has bugs preventing itself from running on WSA. Magisk v24+ has fixed them. So you must use Magisk v24 or later.

• How can I get rid of Magisk?

  Choose none as the root solution.

• How to install custom GApps?

  Tutorial

• Where can I download MindTheGapps?

  You can download from here MindTheGapps (mirror).

  Note that there is no x86_64 pre-build, so you need to build it by yourself (Repository).

  Or you can download the built package for 12.1 and 13 for x86_64 from this page.

• Is it possible to migrate data from a lower version like 2305 to a newer version?

  This is certainly available, Microsoft's change of read-only partition from 2305's EROFS to read-only EXT4 only affects the read-only system partition.

  It has no effect on the user data partition. Check the logs if there is a failure to boot.

• How to install KernelSU?

  Tutorial

Credits Copy Chapter

• StoreLib: API for downloading WSA
• Magisk: The most famous root solution on Android
• The Open GApps Project: One of the most famous Google Apps packages solution
• WSA-Kernel-SU and kernel-assisted-superuser: The kernel su for debugging Magisk Integration
• WSAGAScript: The first GApps integration script for WSA
• erofs-utils: Pre-build erofs-utils with erofsfuse enabled

The repository is provided as a utility.

Android is a trademark of Google LLC. Windows is a trademark of Microsoft Corporation.

File: MagiskOnWSA/docs/Custom-GApps.md Copy Chapter

How to install custom GApps

1. Build WSA without gapps to let the script download needed files

   ./build.sh --gapps-brand none

2. • For OpenGApps

     Place custom OpenGApps to download folder and rename to OpenGApps-{arch}-{variant}.zip (e.g. OpenGApps-x64-pico.zip)

   • For MindTheGapps

     Place custom MindTheGapps to download folder and rename to MindTheGapps-{arch}.zip (e.g. MindTheGapps-x64.zip)

3. Build WSA offline

   ./build.sh --offline --gapps-brand {brand} --gapps-variant {variant}

File: MagiskOnWSA/docs/KernelSU.md Copy Chapter

Install KernelSU

Install Manager Copy Chapter

1. Download KernelSU Manager from (Download the artifact named manager).

2. Unzip the downloaded zip package and get the manager apk named KernelSU_vx.x.x-xx-.....apk.

3. Use the command adb install <apkname>.apk to install the manager.

Install Kernel Copy Chapter

1. Download pre-build kernel from (Remember to download the same architecture).

2. Unzip the downloaded zip package and get the kernel file named bzImage.

3. Replace the kernel in the folder named Tools in the WSA directory with bzImage.

4. Restart WSA and then enjoy.

File: MagiskOnWSA/docs/Fixes/Fix Error 0x80073CF0.md Copy Chapter

Issue: Error 0x80073CF0 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to many factors such as corruption of files when downloading the .zip/.7z files or extracting from the .zip/.7z files. This can be also caused if the folder name is too long (This is the case as MagiskOnWSA tends to generate a long string for the .zip/.7z file and the folder within the archive.)

Solution Copy Chapter

1. Ensure the partition/drive you are installing from is NTFS

2. Redownload WSA Build .zip/.7z file from the Releases page (sometime the files can be corrupted during download and extraction)

3. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing (For example: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon ----> WSAArchive2XXX)

4. Extract the .zip or .7z archive (depends on the release) using 7-zip or a proper archive tool and not the built in Windows archive extractor

5. Rename the extracted folder(s) to a shorter name, which can be anything to your choosing

For example:

• Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon
• After: WSAExtracted2XXX

6. Ensure that 'Run.bat' is run as Administrator

Hope this works for you!

File: MagiskOnWSA/docs/Fixes/Fix Error 0x80073CF6.md Copy Chapter

Issue: Error 0x80073CF6 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to many factors that is preventing the app from being registered. Although there is no definite solution, we can try these steps to try to fix the problem

This installation issue may also arise in systems that are using Modified Windows OSes such as ReviOS, Tiny10/11, etc. This is due to the fact that these OSes have been modified to remove certain features that are deemed unnecessary. This may cause issues with the installation of WSA.

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered
In E:\WSA\Install.ps1:102 Character:1
+ Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion

   + CategoryInfo          : WriteError: (E:\WSA\AppxManifest.xml:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Prequisite Steps: Copy Chapter

1. Ensure the partition/drive you are installing from is NTFS

2. Redownload WSA Build .zip (sometime the files can be corrupted during download and extraction)

3. If you have installed WSA prior, make sure that it has been uninstalled and delete all folders containing "WindowsSubsystemForAndroid" from the following directories/paths and the subdirectories within:

• C:\ProgramData\Microsoft\Windows\AppRepository

• C:\ProgramData\Microsoft\Windows\WindowsApps

• %localappdata\ProgramData\Packages

4. Restart your Computer

If the issue has been fixed, then there is no need to follow through the rest of the guide.
However, if you have the same issue, it is vital that you obtain the logs and try to decipher what is causing the error

To obtain the logs (admin privilege required):

1. Open a PowerShell window and change working directory to your Windows Subsystem For Android™ directory.

2. Run the command below in PowerShell. This should fail with an ActivityID, which is a UUID required for the next step.

   powershell Copy

   Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml

3. Run the command below in PowerShell. This should print the log of the failed operation.

   powershell Copy

   Get-AppPackageLog -ActivityID <UUID>

There are various causes that lead to error 0x80073CF6 Find the fix that matches the error presented in the logs obtained from the instructions above Copy Section

Issue 1: 0x800706D9 "There are no more endpoints avaliable from endpoint mapper" Copy Chapter

**Windows Firewall** Copy Section

1. Ensure that Windows Firewall is on and is working with "Recommended Settings" being enabled

2. Ensure that Windows Firewall service is running. If not, enable it.

3. Restart your PC

Other Firewalls Copy Section

1. Ensure that your Firewall is on and is working with "Recommended Settings" being enabled

2. Ensure that your Firewall is not blocking or preventing new entries

3. Restart your PC

Issue 2: 0x80073B06 "Initial screen image for the current application context cannot be recognized" Copy Chapter

Installing MagiskOnWSA...
Add AppxPackage: Deployment failed due to HRESULT: 0x80073CF6, unable to register the package.
AppxManifest.xml (24,27): Error 0x80073B06: Unable to install or update package MicrosoftCorporateII.WindowsSubsystemForAndroid_ 8wekyb 3d8bbwe because the initial screen image for the current application context cannot be recognized. The application context may include specific language, DPI, contrast, or other special conditions. If you cannot recognize a context specific splash screen image, add a splash screen image to use as the default setting. Note: For additional information, look for [ActivityId] 94c065bb-5a2a-0004-129b-c1942a5ad901 in the event log, or use the command line Get AppPackageLo g - ActivityID 94c065bb-5a2a-0004-129b-c1942a5ad901 in the location D:  WSA  WSA  Install.ps1:106 Character: 1
+ Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion  ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : WriteError: (D:\WSA\WSA\AppxManifest.xml:String) [Add-AppxPackage], IOException
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Solution: Copy Section

1. If you encounter this problem when installing from a build built using MagiskOnWSALocal or WSA-Script, try deleting the previously built builds and rebuild. Make sure to delete and reclone the git repo if you are building using MagiskOnWSALocal.

Or

2. If you encounter this problem when installing using prebuilt builds from Releases from this repo, try redownloading the latest build. If the issue persists, report to the Issues and I will be happy to assist you

Hope these fixes work for you!

File: MagiskOnWSA/docs/Fixes/Fix Error 0x80073CF9.md Copy Chapter

Issue: Error 0x80073CF9 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to many factors such as corruption of files when downloading the .zip files or extracting from the .zip files. This can be also caused if the folder name is too long (This is the case as MagiskOnWSA tends to generate a long string for the .zip file and the folder within the archive.)

Solution Copy Chapter

1. Ensure the partition/drive you are installing from is NTFS

2. Redownload WSA .zip file on Release page (sometime the files can be corrupted during download and extraction)

3. Rename the .zip folder to a shorter name, which can be anything to your choosing (WSA_2xxx.xxxxx.xx.x_x64_Release-Nightly-with-magisk-xxxxxxx-MindTheGapps-13.0-as-Pixel-5-RemovedAmazon ----> WSAArchive2XXX)

4. Extract the .zip using WinRAR or a proper archive tool and not the built in Windows .zip extractor

5. Rename the extracted folder(s) to a shorter name, which can be anything to your choosing

For example:

• Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon
• After: WSAExtracted2XXX

6. Ensure that 'Run.bat' is run as Administrator

Hope this works for you!

File: MagiskOnWSA/docs/Fixes/Fix Error 0x80073CFB.md Copy Chapter

Issue: Error 0x80073CFB when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue can arise due to the fact that "the provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details."

Solution Copy Chapter

1. Go to %LOCALAPPDATA%/Packages/, and make sure that the folder MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe is deleted. (If it does not exist, move on to Step 2.)

2. Open Powershell (as Admin) and run the following command:

Get-AppxPackage -Name "MicrosoftCorporationII.WindowsSubsystemForAndroid" -AllUsers | Remove-AppxPackage -AllUsers

3. Delete all folders related to WSA (expect the .zip files for WSA Builds), which include folders extracted for WSA installation.

4. Re-extract and re-run Run.bat

The issue should now be fixed

File: MagiskOnWSA/docs/Fixes/Fix Error 0x80073CFD.md Copy Chapter

Issue: Error 0x80073CFD when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused by having a Windows 10 Build that is too old to run WSA and hence the installer halts and presents the error, as shown below

Registering AppxManifest.xml... 
Add-AppxPackage : Deployment failed with HRESULT: 0x80073CFD, 
Prerequisite for an install could not be satisfied. Windows cannot install package MicrosoftCorporationII.WindowsSubsystemForAndroid_2301.40000.7.0_x64__8wekyb3d8bbwe because this package is not compatible with the device. 
The package requires OS version 10.0.19044.2604 or higher on the Windows.Desktop device family. 
The device is currently running OS version 10.0.19043.2364. 
NOTE: For additional information, look for [ActivityId] 8b8599fb-55c1-0002-338b-868bc155d901 in the Event Log or use the command line 
Get-AppPackageLog -ActivityID 8b8599fb-55c1-0002-338b-868bc155d901

Solution: Copy Chapter

The Solution is simple: Copy Section

Using the Microsoft Guide, update Windows 10 to the latest version

Or

Using the Windows 10 Update Assistant, update Windows 10 to the latest version

File: MagiskOnWSA/docs/Fixes/Fix Error 0x80073D10.md Copy Chapter

Issue: Error 0x80073D10 when "Run.bat" is executed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused when your are trying to install the incorrect WSA package for your CPU Archetecture. For example, you are mistakenly trying to install the arm64 package on your x64 system.

Solution Copy Chapter

1. To ensure that you download the correct package for your CPU archtecture, go to the Release of this repository then check again

2. Click on the package matching your Operating System (OS) and CPU Archetecture

3. Download then install the package by follow the Installation guide in README.md file

File: MagiskOnWSA/docs/Fixes/FixInstallps1.md Copy Chapter

[Binary file]

File: MagiskOnWSA/docs/Fixes/FixInternet.md Copy Chapter

Issues: Copy Chapter

No Internet Copy Section

Solution: Copy Chapter

These will be split into multiple solutions due to the different causes of the problem of no internet on Windows Subsystem for Android (WSA) and Windows Subsytem for Linux (WSL)

Fix #1: Uninstalling Hyper-V Network Adapters

Some Hyper-V Network Drivers may be interferring with WSA or WSL

⚠️ Carry these instructions out with caution. ⚠️

⚠️ I do not take responsibility for any damage caused ⚠️

**Step 1: Open Device Manager**

1. Using Search or Win + X, open Device manager

**Step 2: Show Hidden Device**

3. Press on "View"
4. Select "Show hidden devices"

**Step 3: Uninstalling All Hyper-V Network Adapter**

5. Select each driver that has "Hyper-V" in its name
6. Right-Click and select "Uninstall Driver" for each of these drivers

**Step 4: Restart Windows**

Fix #2: Checking Firewall Settings

Sometimes Windows Firewall and other Firewall tools and software may be the cause of internet issues. It is therefore important that we check them if we are facing issues with internet on WSA.

Users with Windows Firewall

1. Open Windows Firewall by pressing the Windows Key and "R" key, Open Run

2. Type WF.msc, and then select OK. See also Open Windows Firewall

3. Go to the "Inbound Connection" tab

4. Find the entries in the list that state: "Windows Subsystem for Android™"

5. Confirm that these entries are Enabled and "Action" is set to "Allow" for both UDP and TCP for all entries (as shown above)

6. Now, go to the "Outbound Connection" tab

7. Find the entries in the list that state: "Windows Subsystem for Android™"

5. Confirm that these entries are Enabled and "Action" is set to "Allow" for both UDP and TCP for all entries (as shown above)

You may not have as many entries for "Windows Subsystem for Android™", as shown in the screenshots provded. These are just for illustration purposes and Firewall entries may look different on your device.

Antivirus Users

It is a known issue that some antivirus firewall such as those built-in to ESET, Bitdefender, AVG and many others, can prevent the internet for Windows Susbsystem for Android (WSA) from working.
It is highly recommended to disable the firewall provided by these Antivirus/Antimalware tools and fallback to Windows Firewall, to see if the internet starts working.

Source: From this

---

Fix #3: Changing Android DNS Settings

1. Open Windows Firewall by pressing the Windows Key and "R" key, Open Run

2. Type wsa://com.android.settings, and then select OK.

3. Wait for Android Settings to load and open.

4. In Android Settings, click on the "Network and Internet" Section.

5. In the "Network and Internet" Section, select "Private DNS" .

6. In the "Select Private DNS mode", click on "Private DNS provider hostname".

7. In the entry box below, type "dns.google" and click save.

8. Now click on the "Internet" section and click on VirtWifi.

9. Click on "Disconnect".

10. Then click on "Connect".

Your Internet should now be fixed!

---

Fix #4: Enabling and Disabling Advanced Networking from WSA Settings

1. Go to the Start Menu and search for Windows Subsystem for Android™
2. Depending on your WSA version, the Advanced Networking setting is located in different places witin the WSA Settings app

• For 2305 and newer builds, you must go to "Advanced settings" and then to "Experimental features"
• For 2304 and older builds, this setting is located in the "System" tab/ main screen when you open the Settings app

3. Make sure that if Advanced Networking is enabled, you disable it as this may be causing issues with the internet

This should fix the internet if Advanced Networking was on and the internet was not working due to this

---

File: MagiskOnWSA/docs/Fixes/FixPathTooLong.md Copy Chapter

Issue: Error stating that "Path is too long" when extracting files from .zip archive, needed to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused if the folder name is too long. This is the typically the case as MagiskOnWSALocal script tends to generate a long string for the .zip file and the folder within the archive.

Solution Copy Chapter

The solution is simple, all you have to do is:

1. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

2. Rename the extracted folder to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

File: MagiskOnWSA/docs/Fixes/FixVirtError.md Copy Chapter

Issues: Copy Chapter

Solution: Copy Chapter

You may encounter this problem, even if Virtualization is enabled on your PC (in the BIOS) and shows up as enabled in Task Manager (as seen below) and Virtual Machine Platform + Windows Hypervisor Platform is Enabled. The solution is:

1. Remove WSA: Right clicking on "Windows Subsystem for Android™ Settings" and pressing uninstall + Deleting the extracted WSA (MagiskOnWSA/WSABuilds) folder that you extracted and installed from.

2. Go to "Turn Windows features on and off" and if any of these features below are enabled, DISABLE THEM.

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Subsystem for Linux

3. Restart your PC

4. Boot into your BIOS, and DISABLE Virtualization.

   • Click here for a guide for Windows 11
   • Click here for a guide for Windows 10

5. Ensure that you have Control Flow Guard enabled in Windows Security > Apps & browser control > Exploit protection. This is a known issue that can prevent WSA from starting

6. In registry editor (regedit), go to “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends"

   Change the value of “Start” from “3” to “0”

Note
You can change it back to 3, if it makes no difference

7. Then in CMD (Run as Adminstrator), paste:

bcdedit /set hypervisorlaunchtype auto

8. ENABLE the features that you disabled in Step 2 and restart a second time.

9. Boot into your BIOS, and ENABLE Virtualization.

   • Click here for a guide for Windows 11
   • Click here for a guide for Windows 10

10. Restart the Computer

11. Reinstall WSA by running Run.bat

Hope this works for you!

File: MagiskOnWSA/docs/Fixes/Google Play Issues.md Copy Chapter

Issue 1: After signing in to your Google Account from the Play Store App, Play Store keeps crashing Copy Chapter

Preface: Copy Section

This issue will prevent you from opening Play Store and effectively prevent the function of MindTheGapps/OpenGapps. This issue may usually occur after signing in. Known cases indicate that this issue is pretty common on newer hardware (12th or 13th Gen Intel Processors, for example)

Solution: Copy Chapter

Step 1.

Open Android Settings by pressing the Windows Key and "R" key, Open Run

Step 2.

Type wsa://com.android.settings, and then select OK.

Step 3.

Wait for Android Settings to load and open.

Step 4.

In Android Settings, click on the "Apps" Section and then click on "All Apps".

Step 5.

In the "All Apps" Section, find the "Google Play Services" app .

Step 6.

Click on the "Google Play Services" app, which should open a page with various different options for the app ("Permissions", "Notification", "Storage and Cache" etc.)

Step 7.

Click on "Storage and Cache"

Step 8.

Find the "Manage Space" button and click on it, which should popup a window reading "Google Play services storage"

Step 9.

Click on "Clear All Data" and done

Issue 2: Could not sign-in. There was a problem connecting to play.google.com Copy Chapter

Preface: Copy Section

This issue will prevent you from signing into Play Store and effectively prevent the function of MindTheGapps/OpenGapps. This issue may usually occur after updating. Known cases have occured after updating from a non Google Apps WSA build to a Google Apps build

Solution: If you are using VPN, please disconnect it because VPN may make WSA fail to connect to VirtWifi. Copy Chapter

File: MagiskOnWSA/docs/Fixes/InstallPs1FailedToUpdate.md Copy Chapter

Issues: Install.ps1 Failed To Update Copy Chapter

Solution: Copy Chapter

1. Run Powershell with this command:

PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1

File: MagiskOnWSA/docs/Fixes/InternetSecuritySettingsBlock.md Copy Chapter

Issue: Error stating that "Your Internet security settings prevented one or more files from opening" when trying to run `Install.ps1` or `Run.bat` to install Windows Subystem for Android (WSA) Copy Chapter

Preface: Copy Section

This issue is caused if the folder name is too long. This is the typically the case as MagiskOnWSALocal script tends to generate a long string for the .zip file and the folder within the archive.

Solution Copy Chapter

The solution is simple, all you have to do is:

1. Rename the .zip/.7z file to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

2. Rename the extracted folder to a shorter name, which can be anything to your choosing

• For example:

  • Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

  • After: WSAArchive2XXX

File: MagiskOnWSA/docs/Fixes/Keyboard Is Not Working.md Copy Chapter

Issue: Keyboard Does Not Work Copy Chapter

Preface: Copy Section

This issue will prevent you from using your keyboard on WSA

Solution: Copy Chapter

1. ***Open Run by pressing the Windows Key and R***

2. ***Type in services.msc in the box and then select OK***

3. ***Search for Touch Keyboard and Handwriting Panel***

4. ***Enable it by switching startup type to automatic***

5. ***Click apply***

6. ***Restart your computer.***

File: MagiskOnWSA/docs/Fixes/MissingIcons.md Copy Chapter

Issue: Icons have disappeared or have turned white after updating WSA or after restarting your computer Copy Chapter

Preface: Copy Section

This looks like a bug in the WSA itself and the icons can be restored by the following steps.

Solution Copy Chapter

1. Backup userdata.vhdx from %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx

2. Uninstall WSA by Following this guide

3. Remove the two lines in Install.ps1 that automatically launches Magisk and Play Store after the installation is finished

function Finish {
    Clear-Host
    Start-Process "wsa://com.topjohnwu.magisk"
    Start-Process "wsa://com.android.vending"
}

4. Install WSA

5. Restore userdata.vhdx to %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx

6. Start WSA

Warning
Do not start WSA before restoring user data.

File: MagiskOnWSA/docs/Fixes/TargetMachineActivelyRefusedConnection.md Copy Chapter

Issue: Error: No connection could be made because the target machine actively refused it (10061) Copy Chapter

Preface: Copy Section

This issue occurs when you are either using a sideloading application such as [WSA-Sideloader](https://github.com/infinitepower18/WSA-Sideloader) or [WSAPacman](https://github.com/alesimula/wsa_pacman), or when you try to connect to a device using ``adb.exe`` via [Android SDK Platform Tools](https://developer.android.com/tools/releases/platform-tools). This issue arises due to an issue with the inability of Hyper V to reserve port 58526 causing the issue, as seen below.

cannot connect to ||127.0.0.1:58526:|| No connection could be made because the target machine actively refused it. (10061)

Solution Copy Chapter

This is a bug with the subsystem itself, restarting the PC will usually fix it. But, if you still get this error, try these steps:

• _**1. Make sure WSA is turned off and disable WSA autostart in Task Manager ---> Startup Apps before proceeding**_

• _**2. Disable Hyper-V (if it is enabled) using the command**_

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

• **3. Reboot your PC**

• _**4. Reserve port 58526 so Hyper-V doesn't reserve it back using the command**_

netsh int ipv4 add excludedportrange protocol=tcp startport=58526 numberofports=1

• _**5. Re-enable Hyper-V (if it was previously enabled) using the command `dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All` and reboot your PC**_

Hope this works for you!

File: MagiskOnWSA/docs/Fixes/WSA Does Not Load After Install + No Splashscreen.md Copy Chapter

Issue: Windows Subystem for Android (WSA) is unable to run any apps and there is no splashscreen (when opening the Files app from the settings) and no icons for Android apps. Copy Chapter

Preface: Copy Section

Why this occurs is unknown. However, after multiple attempts trying to fix this issue, a solution was found.

https://github.com/MustardChef/WSABuilds/assets/68516357/a9690842-5159-470a-b472-5990faabeac8

Solution Copy Chapter

Rename the extracted folder to a shorter name, which can be anything to your choosing.

• Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

• After: WSAArchive2XXX

https://github.com/MustardChef/WSABuilds/assets/68516357/626ec699-6f74-40ff-94fb-26fbe1c4f182

**Hope this works for you!** Copy Chapter

File: MagiskOnWSA/docs/Fixes/WSA Settings App Crashes + Android Apps Do Not Load After Installation.md Copy Chapter

Issue: Windows Subystem for Android (WSA) Settings app crashes after installation, when opened, and you are unable to run any apps. Copy Chapter

Preface: Copy Section

Why this occurs is unknown. However, after multiple attempts trying to fix this issue, a solution was found.

https://github.com/MustardChef/WSABuilds/assets/68516357/7333e8b4-7c09-4032-b816-47fc0d83767b

Solution Copy Chapter

Rename the extracted folder to a shorter name, which can be anything to your choosing.

• Before: WSA_2XXX.XXXXXXX_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon

• After: WSAArchive2XXX

https://github.com/MustardChef/WSABuilds/assets/68516357/7a33df5b-e68b-43b1-9365-9c4d7ff5c2db

**Hope this works for you!** Copy Chapter

File: MagiskOnWSA/docs/Fixes/WSA Stopped Working.md Copy Chapter

Issues: WSA Stopped Working! Copy Chapter

***You may encounter this problem. WSA has been working fine for you, but all of a sudden, it breaks/ stops working. You are distraught. What do you do, when WSA beloved had been borked.***

Solution: Copy Chapter

1. Go to "Turn Windows features on and off" and if any of these features below are enabled, DISABLE THEM.

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Subsystem for Linux

2. Restart your PC

3. Boot into your BIOS, and DISABLE Virtualization.

• Click here for a guide for Windows 11
• Click here for a guide for Windows 10

4. Ensure that you have Control Flow Guard enabled in Windows Security > Apps & browser control > Exploit protection. This is a known issue that can prevent WSA from starting

5. In registry editor (regedit), go to “\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends"

   Change the value of “Start” from “3” to “0”

Note
You can change it back to 3, if it makes no difference

6. Then in CMD (Run as Adminstrator), paste:

bcdedit /set hypervisorlaunchtype auto

7. ENABLE the features that you disabled in Step 1 and restart a second time.

8. Boot into your BIOS, and ENABLE Virtualization.

• Click here for a guide for Windows 11
• Click here for a guide for Windows 10

9. Restart the Computer

10. Try re-running WSA by running Run.bat or via the Windows Subsystem for Android Settings app

Hope this works for you!

File: MagiskOnWSA/docs/Guides/ADB-Sideloading.md Copy Chapter

Sideloading APKs in to Windows Subsystem for Android

Setting up ADB to work with WSA Copy Chapter

• Launch Windows Subsystem for Android.
• Here, click on Advanced Settings and then enable Developer mode by clicking on the toggle button.
• Take note of IP address and port shown in the Developer mode section.
• Launch Windows Terminal and make sure ADB is installed (install ADB).
• Use command adb pair 127.0.0.1:58526 to pair ADB with WSA.
• In Wireless debugging window, see Device name and under it IP address and port.
• Use command adb connect 127.0.0.1:58526 to connect WSA with ADB.

Once this is done, use command adb devices to make sure that WSA is connected.

Installing APKs using ADB Copy Chapter

Now you can install any app you want, but I personally suggest installing a web browser and a file manager first.

• Download the APK.
• Open File Explorer, right click on downloaded APK and tap on Copy as path.
• Launch Windows Terminal.
• Use adb install <file path> to install the APK.
  [P.S. You can right click to paste in Terminal]

After installation using ADB Copy Chapter

You can now open the web browser you installed in Android, and download and install Aurora Store like you do on any Android device - normally sideloading APK without using ADB.

A list of suggested apps to install on WSA: Copy Section

• microG: A free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries.
• Aurora Store: an app store that lets you download apps from Google Play without a Google account.
• MiX: MiXplorer mix of explorers (SD, FTP, Lan, Cloud and other storage explorers) is a fast, smooth, beautiful, reliable and full-featured file manager with a simple and intuitive user interface.
• Bromite: A Chromium fork with support for ad blocking and enhanced privacy.

File: MagiskOnWSA/docs/Guides/BusyBox.md Copy Chapter

Guide: How to install BusyBox Copy Chapter

Preface: Copy Section

Since Magisk has BusyBox built-in already, this proceedure is very simple

Process Copy Chapter

Step 1: Copy Section

Using an Android browser downloaded though the Play Store/sideloaded into WSA, download the following Magisk Module to install and symlink BusyBox with its applets to the Magisk built-in busybox binary. No need to do it manually or to get a Custom Build.

Step 2: Copy Section

Through Magisk Manager, install the Magisk module .zip file

Step 3 (Optional): Copy Section

You can then test if BusyBox is working by either using a Root Checker:

or by using ADB Shell and:

adb shell
su
busybox | head -1

File: MagiskOnWSA/docs/Guides/ChangingGPU.md Copy Chapter

Guide: Changing the GPU used by Windows Subsystem For Android™ Copy Section

1. Open up Windows Subsystem For Android™ Settings --> Either by going to the Start Menu and searching for it or by using the Search feature

2. Make sure to turn off Windows Subsystem For Android™ by pressing Turn off in the Turn off Windows Subsystem For Android™ tab

3. In Windows Subsystem For Android™ Settings select the Graphics and Performance Tab

4. Click on the selection for GPU used for apps for Android™ and select the GPU that you would like Windows Subsystem For Android™ to use.

File: MagiskOnWSA/docs/Guides/Checksum.md Copy Chapter

Check integrity of downloaded file

**1. Press Win + X on your keyboard and select Windows™ Terminal (Admin) or Powershell (Admin) depending on the version of Windows™ you are running** Copy Section

**2. Input the command below and press enter, replacing {X:\path\to\your\downloaded\archive\package} including the {} with the path of the downloaded archive package** Copy Section

cd "{X:\path\to\your\downloaded\archive\package}"

**3. Input the command below and press enter, replacing WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon with the name of the archive package** Copy Section

certutil -hashfile "WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon" SHA256

For PowerShell:

(Get-FileHash -Path "WSA_2XXX.XXXXX.X.X_XXXX_Release-Nightly-with-magisk-XXXXXXX-XXXXXX-MindTheGapps-XX.X-RemovedAmazon" -Algorithm SHA256).Hash

**4. Compare the SHA256 output with ones at [Release](https://github.com/YT-Advanced/WSA-Script/releases/latest) or in the `sha256-checksum.txt` (if you download artifact from the Custom Build task).** Copy Section

• If package don't have the same SHA-256 Hash, please download then check again.
• If package have the same SHA-256, install it by Following this guide

File: MagiskOnWSA/docs/Guides/KernelSU.md Copy Chapter

Install KernelSU Manager

Text Guide Copy Chapter

1. Connect to WSA with ADB
2. Run the following command:
   text Copy

   adb shell ksuinstall

If the installation completes successfully, the KernelSU Manager will launching.

File: MagiskOnWSA/docs/Guides/LocalHostLoopback.md Copy Chapter

Guide: LocalHost Loopback Copy Chapter

Preface: You want to connect WSA to the localhost (Windows 11 hosting machine) or to a development server I run on Windows 11 or any such scenario where you would want to connect to the Windows 11 localhost, but are unable to

Note: Localhost Loopback has now been officially added to the update 2308 of WSA, and so this guide is probably outdated now. Copy Section

Process: Copy Chapter

1. Run PowerShell as administrator

2. Execute

Set-NetFirewallHyperVVMSetting -VMCreatorId '{9E288F02-CE00-4D9E-BE2B-14CE463B0298}' -LoopbackEnabled True

3.Execute

New-NetFirewallHyperVRule -DisplayName LoopbackAllow -VMCreatorId '{9E288F02-CE00-4D9E-BE2B-14CE463B0298}' -Direction Inbound -Action Allow -LocalPorts [PORT]

(replacing [PORT] with the port you're trying to expose)

File: MagiskOnWSA/docs/Guides/MoveToExtDrive.md Copy Chapter

Guide: Moving/Installing Windows Subsystem For Android™ (WSA) to another partition or disk Copy Chapter

Preface: Copy Section

WSA can take up a lot of storage space, hence you want to move it to another partition or disk with more space. This guide goes through a method by which you can install WSA from another disk and to store the data in that drive (instead of `%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe`).

Prerequisites: Copy Section

• The partition/ disk that you want to move/install Windows Subsystem For Android™ to, MUST be NTFS
• Recommended that both disks, C:/ and the disk/partition that you want to install (move) WSA on (to), are SSDs
  • HDDs may work, but performance issues may arise
• Basic knowledge on Command Prompt (CMD) usage
• There must be enough space on the disk/partiton that you are installing/moving WSA to (recommended 20GB, as the VHDX can become very large in size)

Note

If you want to preseve your data, make a backup of the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx file. After uninstalling, copy the VHDX file back to the %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache folder.

Process: Copy Chapter

• Step 1: Remove all previous installations from WSABuilds or official WSA Releases Copy Section

  • To remove WSA installed through WSABuild:

    • 1.) Make sure that Windows Subsystem For Android™ is not running

    • 2.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

    • 3.) Delete the WSA folder that you extracted and Run.bat was run from to install WSA (MagiskOnWSA folder)

    • 4.) Go to %LOCALAPPDATA%/Packages/ and delete the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe

      • If you get an error that states that the file(s) could not be deleted, make sure that WSA is turned off

  • To remove WSA installed from the Microsoft Store:

    • 1.) Search for Windows Subsystem For Android™ Settings using the built-in Windows Search, or through Add and Remove Programs and press uninstall

• Step 2: Install WSA from the desired partition Copy Section

  • 1.) Download the latest WSA Build according to Windows Version and CPU Archtecture from Release.
  • 2.) Extract to the desired partition or drive
  • Using the same process as detailed in Installation
  • 3.) Open the extracted folder and run Run.bat

• Step 3: Moving the AppData (VHDX + data) from your Windows drive (C:\) to the desired partition/drive Copy Section

  • 1.) Go to %LOCALAPPDATA%\Packages\ and copy the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe to the desired drive/partition, making sure to delete the folder from %LOCALAPPDATA%\Packages\ after copying

  • 2.) Open Command Prompt (Admin) through Windows Terminal (Admin) or directly and run the command:

mklink /J "%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe" "Location_Of_Folder_In_Other_Drive"

Replacing Location_Of_Folder_In_Other_Drive with the location of the folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe, copied to the desired to the drive/partition in 1st point of Step 3

• Step 4: Testing if everything is working Copy Section

  • Run Windows Subsystem For Android™ Settings
    • If it crashes, you have made a mistake whilst following the guide. Try following it again.

File: MagiskOnWSA/docs/Guides/Sideloading.md Copy Chapter

Guide: Sideloading APKs Copy Chapter

This guide covers the four different methods of sideloading and installing APKs (from Windows) into Windows Subsystem For Android™ Copy Section

File: MagiskOnWSA/docs/Guides/WSA-Sideloader.md Copy Chapter

WSA Sideloader Usage Guide

With WSA Sideloader, you can install any APK file onto WSA, as well as XAPK, APKM and APKS files.

This guide will show you how to use it.

How to Download and Install WSA-Sideloader Copy Chapter

You can download WSA Sideloader in 3 different ways:

Setup Copy Chapter

Step 1. Once installed, you should see this screen:

Note :
If you get a message that says WSA is not installed, check that you have downloaded and installed WSA correctly as per the WSABuilds instructions.

Step 2. Next, open WSA Settings from the start menu or by typing wsa-settings:// in your browser's address bar, select Developer and enable Developer mode.

Step 3. Now, you can click the Browse button to select your APK file. You can also double click a file in File Explorer to automatically open WSA Sideloader with the APK file already selected.

Step 4. The first time you install an APK, it will ask to allow ADB debugging. Allow it and attempt the installation again. Check the always allow box if you don't want to manually accept the permission every time you install an app.

Step 5. It should take a few seconds to install the APK. Once it says The application has been successfully installed, you can click Open app. Bundle files may take longer depending on the file size.

Note :
If WSA is off, WSA Sideloader will start it for you. After 30 seconds, the installation will automatically continue.

You can find all your installed WSA apps on the start menu, as well as via the "Installed apps" button in WSA Sideloader:

Updating WSA Sideloader Copy Chapter

From time to time, there may be updates that improve the reliability of the app, as well as ensuring it works properly with future releases of WSA.

Therefore, it's highly recommended you keep it up to date.

• If you installed WSA Sideloader using MS Store, you can update the app via the store.
• If you installed through other methods, the sideloader will notify you of an update the next time you launch it.

Troubleshooting Copy Chapter

If you get an error like the one below, check that you have allowed the ADB authorization and enabled Developer Mode. Also try disabling and enabling USB debugging under manage developer settings as that can sometimes fix issues with the ADB connection.

If you get a message saying No connection could be made because the target machine actively refused it, follow this guide

File: MagiskOnWSA/docs/Guides/WSAFiles.md Copy Chapter

Sideloading using the Files app

Starting with WSA version 2305, you can sideload APK files using the Files app. This guide will show you how.

NOTE:
This guide is only applicable for WSA versions 2305 and above. If you're using an older version, you will need to use ADB or one of the listed APK installers.

Setup Copy Chapter

1. Open the Windows Subsystem for Android app, go to Advanced Settings and enable share user folders found under experimental features. Then select the folder that you would like to share by clicking on "Change folder".

2. Go to the "System" section and open the Files app.

3. Click on Subsystem for Android, followed by Windows to browse through your Windows files.

4. Click the APK you want to install and choose package installer if it asks. Agree to the warnings and then click install.

NOTE:
If you're facing problems, try disabling Block installation of malicious apps in the WSA app.