Magisk on WSA (with Google Apps)

Features

• Integrate Magisk and OpenGApps in a few clicks within minutes
• No Linux environment required for integration
• Keep each build up to date
• Support both ARM64 and x64
• Support all OpenGApps variants except for aroma (aroma does not support x86_64, please use super instead)
• Fix external storage access of DocumentUI
• Fix VPN dialog not showing (use our VpnDialogs app)
• Unattended installation
• Automatically activates developers mode in Windows 11
• Update to new version while preserving data with one-click script
• Merged all language packs
• Support managing start menu icons (manually installing WSAHelper to use this feature)

Video Guide

https://user-images.githubusercontent.com/5022927/145696886-e13ebfc1-ff25-4410-893e-d3e517af70ea.mp4

Text Guide

1. Star (if you like) and fork this repo (keep it PUBLIC, private repo is not supported)
2. Go to the Action tab in your forked repo
3. In the left sidebar, click the Build WSA workflow.
4. Above the list of workflow runs, select Run workflow
5. Select the version of Magisk and select the OpenGApps variant (none is no OpenGApps) you like, select the root solution (none means no root), select WSA version and its architecture (mostly x64) and click Run workflow
6. Wait for the action to complete and download the artifact DO NOT download it via multithread downloaders like IDM or ADM
7. Unzip the artifact
   • The size shown in the webpage is uncompressed size and the zip you download will be compressed. So the size of the zip will be much less than the size shown in the webpage.
8. Right-click Install.ps1 and select Run with PowerShell
   • If you previously have a MagiskOnWSA installation, it will automatically uninstall the previous while preserving all userdata 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 you want to restore the icons to start menu, please install and use WSAHelper.)
   • 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
9. Magisk/Play store will be launched. Enjoy by installing LSPosed-zygisk with zygisk enabled or Riru and LSPosed-riru

FAQ

• Can I delete the unzipped folder?

  No.

• Why the size of the zip does not match the one shown?

  The zip you downloaded is compressed and Github is showing the uncompressed size.

• How can I update WSA to new version?

  Rerun the Github action, download the new artifact, 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 new version?

  Do the same as updating WSA

• VPN is not working?

  Tell Microsoft to fix it. We cannot fix it easily.

• How to pass 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 system as read-write?

  No way in WSA since it's mounted as read-only by Hyper-V. You can modify system by making a Magisk module. Or directly modify system.img. Ask Google for help.

• I cannot adb connect localhost:58526

  Make sure developer mode is enabled. If the issue persists, check the IP address of WSA in the setting page and try adb connect ip:5555.

• Magisk online module list is empty?

  Magisk actively remove online module repository. You can install 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 23.0 stable or lower version?

  No. Magisk has bugs preventing itself running on WSA. Magisk 24+ has fixed them. So you must use Magisk 24 or higher version.

• How can I get rid of Magisk?

  Choose none as root solution.

• Github Action script is updated, how can I synchronize it?

  1. In your fork repository, click fetch upstream
  2. Then and click fetch and merge

Credits

• 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