lsposed/magiskonwsalocal

Integrate Magisk root and Google Apps into WSA (Windows Subsystem for Android)

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 5th, 2026
Created on August 14th, 2022
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 25,331
Total Stargazers: 10,594 (+0)
Total Subscribers: 168 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.3 hours
Mean response time: 37.6 days
90th percentile: 96.1 days
Tracked items: 13

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 537 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (13)
  • enhancement (1)
  • invalid (1)
  • spam (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Magisk on WSA is a tool that integrates Magisk root access and Google Apps into Windows Subsystem for Android.

The tool automates the process of building a customized WSA image by combining Magisk, Google Apps, and the base Android system. It handles dependency installation automatically through a shell script, supports both ARM64 and x64 architectures, and offers options for different Google Apps packages including MindTheGapps. The build process runs on Linux systems and produces a ready-to-install WSA image that can be deployed on Windows 11.

Developers working on Windows 11 who need root access within Android or want Google Play Services should consider this tool. It suits anyone who wants a streamlined alternative to manual WSA modification. The project recommends Ubuntu, Debian, or openSUSE Tumbleweed as build environments, with WSL2 support available for running these on Windows. The tool removes the Amazon Appstore by default, fixes VPN dialog visibility issues, and includes device administration features. It also handles language packs and can update existing installations while preserving user data.

Development activity shows consistent maintenance with regular updates to keep builds current. The project includes safeguards against misuse of GitHub Actions in forks to prevent upstream repository disruption. Documentation is straightforward with both automated setup and manual text-based guidance provided. The codebase is primarily shell-based, reflecting the automation-focused nature of the build process.