Skip to main content
After successfully installing Windows Subsystem for Android, you’ll see a confirmation message indicating which variant you installed. This page helps you understand what comes next.

​
What You Have Installed

Depending on your chosen build, you may have installed WSA with:
  • Root Access: Magisk (Stable/Canary/Beta/Alpha/Debug), MagiskDelta, or KernelSU
  • Google Services: MindTheGapps or no Google services
  • App Store: Amazon Appstore included or removed

​
Build Stability

Different build configurations have varying stability levels:
Magisk Builds: Some users report modules disappearing after install and reboot on certain PCs. A temporary workaround is available.
No Root with MindTheGapps: Generally stable with no major issues reported.

​
Initial Setup Steps

1

Launch WSA Settings

Open Windows Subsystem for Android Settings from the Start Menu or through Windows Search.
2

Configure Basic Settings

Review and adjust:
  • Subsystem resources (memory allocation)
  • Screen resolution settings
  • GPU selection (if you have multiple GPUs)
3

Enable Developer Mode (Optional)

If you plan to sideload apps, navigate to Developer settings and enable Developer mode. This allows ADB connections and app sideloading.
4

Choose Subsystem Screen Reader

Configure accessibility options if needed under the System section.

​
Next Steps

Sideload Apps

Learn how to install Android apps from APK files

Configure GPU

Switch between Intel HD and dedicated GPU

Setup Localhost

Enable network access between WSA and Windows

Install BusyBox

Add BusyBox utilities for advanced terminal usage

​
Accessing WSA Settings

You can open Windows Subsystem for Android Settings in multiple ways:
  • Search for “Windows Subsystem for Android” in the Start Menu
  • Search using Windows Search (Win + S)
  • Navigate through Settings > Apps > Installed apps
  • Type wsa-settings:// in your browser’s address bar

​
Troubleshooting

If WSA Settings crashes on first launch:
  1. Ensure you followed all installation steps correctly
  2. Verify you have the correct Windows 11 version
  3. Check that virtualization is enabled in BIOS
  4. Review the Troubleshooting Guide for common issues

Need Help?

Join the WSA Community Discord server for advice and support

Build docs developers (and LLMs) love

Get started for freeTalk to us