About Magisk on WSA
Magisk is a systemless root solution for Android that provides root access without modifying system partitions. WSABuilds integrates Magisk to enable:- Root access for advanced Android apps
- Systemless modifications via Magisk modules
- SafetyNet/Play Integrity workarounds (limited)
- Advanced debugging and development
Magisk Versions
WSABuilds offers different Magisk variants to suit various needs:- Stable
- Beta/Canary
- Delta
- Alpha
Official Magisk (Stable)The standard Magisk release maintained by topjohnwu.
- Package:
com.topjohnwu.magisk - Update frequency: Monthly or as needed
- Stability: Highest
- Recommended for: Most users
- Core root functionality
- Module system
- MagiskHide (deprecated, replaced by DenyList)
- Zygisk support
First Launch
After installing WSA with Magisk:Launch Magisk Manager
Open the Start Menu and search for “Magisk” or look for the Magisk app in the WSA app list.
Grant root access
Magisk will initialize on first launch. This may take a few moments.
Unlike on physical devices, Magisk on WSA doesn’t require a reboot after initialization.
Managing Root Access
Granting Root to Apps
When an app requests root access:- A Magisk prompt will appear
- Review the app name and package
- Choose:
- Grant - Allow root access
- Deny - Block root access
- Set duration (permanent, timeout, etc.)
Managing Root Permissions
Installing Magisk Modules
Magisk modules provide systemless modifications without altering system files.Installation Methods
- Via ADB (Recommended)
- Via Magisk Manager
Module Installation Examples
Managing Modules
Enable/disable modules
Toggle the switch next to each module:
- Enabled (green): Module is active
- Disabled (gray): Module is inactive
Module Troubleshooting
Module disappears after reboot
Module disappears after reboot
Known Issue: Some WSA builds experience this problem.Workaround:
- Install modules immediately after WSA installation
- Avoid restarting WSA unless necessary
- See temporary workaround
- Consider switching to a stable WSA version (2211 or earlier)
Module causes bootloop
Module causes bootloop
Solution: Boot into Safe Mode:
- Connect via ADB
- Disable problematic module:
- Restart WSA
Module incompatibility with WSA
Module incompatibility with WSA
Common issues:
- Modules that modify kernel parameters
- Hardware-specific modules (camera, sensors)
- Modules requiring specific device models
Magisk Configuration
Recommended Settings
Enable Zygisk for advanced module support (like LSPosed).Requires WSA restart after enabling.
Enable DenyList to hide root from specific apps.Configure in Magisk Settings → Configure DenyList.
Enable Systemless Hosts for system-wide ad blocking.Requires a hosts module or manual hosts file configuration.
DenyList Configuration
Hide root from specific apps:Select apps to hide root from
Toggle apps that should not detect root:
- Banking apps
- Payment apps
- Games with anti-cheat
- Netflix, Disney+, etc.
Updating Magisk
Magisk on WSA cannot be updated directly through the Magisk Manager app.Check for new WSABuilds releases
Visit the Releases page to see if a newer Magisk version is available.
Update WSA
Follow the update procedure to replace your current installation.
User data and installed apps will be preserved during the update.
Advanced: Magisk Customization
For users building custom WSA packages:Using Custom Magisk Builds
Magisk Files Location
Key Magisk files within WSA:Known Limitations
- SafetyNet/Play Integrity: Cannot be fully bypassed due to VM environment
- Hardware modules: Modules requiring hardware access won’t work
- Kernel modules: Cannot modify kernel parameters
- Boot image modifications: Not applicable to WSA architecture
- Module persistence: May experience issues on some WSA versions
Getting Help
WSABuilds Discord
Get community support for Magisk on WSA
Magisk Documentation
Official Magisk documentation
GitHub Issues
Report Magisk-related problems
Module Repository
Browse available Magisk modules
