The Easy Way to Get The Google Play Store Working on Windows 11
Full steps to get Google Play Services and the Google Play Store working on the Windows Subsystem for Android [Updated packages to 1.8.32828.0]
Windows Subsystem for Android™️ enables your Windows 11 device to run Android applications that are available in the Amazon Appstore.
By enabling the Windows Subsystem for Android in Windows 11, you are enabling your Windows device to run Android apps. Android applications are downloaded from the Amazon Appstore on your Android device.
Microsoft released the Windows Subsystem for Android to Windows Insiders on the Beta build of Windows 11 earlier this week, it didn't take long for developers to tinker with the build of Android.
John Wu, the creator of Magisk successfully achieved root on the Windows Subsystem for Android.
Until today, it was impossible to launch the Google Play Store and sign in to your Google account successfully or use apps that depended on Google Play Services.
A clever student by the name of ADeltaX from Italy, managed to successfully install the Google Play Store and sign in to his Google account, this means that he's able to use any apps that needed Google Play Services.
It's now possible to use Google's Android apps such as Google Keep or Google Home on Windows 11.
Make sure virtualization is enabled first, go to Control Panel > Programs > Turn Windows features on or off. Make sure the boxes next to ‘Virtual Machine Platform’ are ticked, then click ‘OK’ to confirm.
Uninstall Windows Subsystem for Android if it's already installed.
Enable Developer options in Windows 11.
- Download the already-patched MSIX package from below:
I have condensed the instructions to make it a lot quicker and easier for you to install the Windows Subsystem for Android.
Microsoft bumped the new version of Windows Subsystem for Android up to 1.8.32828.0, it's not clear what the changes are, but it should bring some stability fixes to the build.
Test out the build and let us know in the comments if Android apps are more stable for you.
Thanks to a new method from LSPosed, we now have WSA with built-in Magisk support.
Xposed is a framework for modules that can change the behavior of the system and apps without touching any APKs. That's great because it means that modules can work for different versions and even ROMs without any changes (as long as the original code was not changed too much). It's also easy to undo.
As all changes are done in the memory, you just need to deactivate the module and reboot to get your original system back. There are many other advantages, but here is just one more: Multiple modules can do changes to the same part of the system or app. With modified APKs, you to decide for one. No way to combine them, unless the author builds multiple APKs with different combinations.
Extract the Zip file (ideally to your C: Drive).
Run Powershell as Administrator.
Modify the Powershell command with the location of the extracted Zip-file
Add-AppxPackage -Register C:\WSA-with-magisk-GApps-pico_1.8.32828.0_x64_Release-Nightly\AppxManifest.xml
The WSA app should now be installing in the background. If you get an error, please ensure all of the steps have been followed correctly.
- Launch the Windows Subsystem for Android.
You'll need the Magisk app once you've installed one of the packages below.
- You should now be able to login to the Google Play Store with your Google Account.
We can now enjoy the full suite of Google Play Apps on our Windows 11 machines.
Use this link to download the msixbundle with the settings ProductId: 9P3395VX91NR, Ring: SLOW
Ubuntu is used in this guide but any other distro will work for this
(We are assuming that you are using the exact terminal, and you are also continuing this from where the last command left off)
sudo apt-get update sudo apt install unzip lzip
Select Platform: x86_64 if Windows architecture is x64 otherwise choose ARM64, Android: 11 and Variant: Pico on OpenGApps
Download 7zip or a similar archival program and open the recently downloaded msixbundle. Find the msix file inside the msixbundle relating to your architecture and extract that to a folder. Delete the files appxblockmap, appxsignature and [content_types] along with the folder appxmetadata
git clone https://github.com/ADeltaX/WSAGAScript cd WSAGAScript/\#IMAGES mv /mnt/path-to-extracted-msix/*.img . cd ../\#GAPPS cp /mnt/path-to-downloaded-gapps/*.zip .
paths in wsl follow the same as windows after /mnt/ its just the drive letter then folder structure as normal. For example /mnt/c/users would be the c:\users folder
Set executable permission for the scripts
cd.. sudo chmod +x extract_gapps_pico.sh sudo chmod +x extend_and_mount_images.sh sudo chmod +x apply.sh sudo chmod +x unmount_images.sh
Change the root directory in VARIABLES.sh
(take note of the output)
replace the root variable with the output of pwd up until and including the WSAGAScript folder
sudo ./extract_gapps_pico.sh sudo ./extend_and_mount_images.sh sudo ./apply.sh sudo ./unmount_images.sh
cd \#IMAGES cp *.img /mnt/path-to-extracted-msix/
Enable developer mode in windows settings
Uninstall any other installed versions of WSA
Open powershell as admin and run
Add-AppxPackage -Register path-to-extracted-msix\AppxManifest.xml
WSA will install with gapps
Copy the kernel file from this repo and replace the kernel file inside the Tools folder of your extracted msix (make sure WSA is not running)
This will allow you use use su inside adb shell
Enter adb shell and run
su setenforce 0
You can now sign in