Skip to main content

Frequently Asked Questions

Installation & Updates

No. The installed folder contains the WSA system files and is required for WSA to run. Deleting it will break your installation.
Download the latest Windows Subsystem For Android Version from the releases page and replace the content of your previous installation, then rerun Install.ps1.Your data will be preserved during the update process.
Wait for a new WSABuilds release that includes the newer Magisk version, then follow the installation instructions to update. Magisk cannot be updated independently from the WSA build.
No. Switching between different GApps packages will break functionality. You must do a complete uninstallation before switching to a different GApps variant.

Troubleshooting

WSA on Windows 10 requires the WSAPatch project. Open an issue in the Discord or GitHub for assistance.For full support with Windows 10 installation, visit the WSAPatch project.
Virtualization is required to run virtual machines like Windows Subsystem For Android.If virtualization is not enabled:
  1. Run Run.bat which will help you enable it
  2. Reboot your computer
  3. Re-run Run.bat to install WSA
If it’s still not working, you need to enable virtualization in your BIOS/UEFI. Instructions vary by PC vendor - search online for your specific motherboard or laptop model.

Features & Capabilities

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. See: https://github.com/kdrag0n/safetynet-fix/discussions/145#discussioncomment-2170917
No. WSA is mounted as read-only by Hyper-V. However, you can modify the system partition by:
  • Creating a Magisk module
  • Directly modifying the system.img file
There are two ways to get logs:Method 1 - ADB Command:
adb logcat
Method 2 - Log File Location:
%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalState\diagnostics\logcat

ADB & Development

  1. Make sure developer mode is enabled in WSA Settings
  2. If the issue persists, check the IP address on the WSA Settings → Developer page
  3. Try connecting with:
adb connect <IP_ADDRESS>:5555
Magisk actively removed the online module repository. You must install modules locally:Step 1: Push the module to the device
adb push module.zip /data/local/tmp
Step 2: Install via shell
adb shell su -c magisk --install-module /data/local/tmp/module.zip
Request a Windows Subsystem For Android version without Magisk from the Releases page using the Issues page.Then follow the installation instructions to switch to a non-Magisk build.

Custom Builds

Option 1: Request a custom build by opening an issue on the Issues pageOption 2: Build it yourself using the MagiskOnWSALocal script and following the instructions in that repository.

Need More Help?

Join the Discord Community

Get real-time support from the community and developers

Build docs developers (and LLMs) love