Recently, we explained how to install Android apps on Windows 11 using the official subsystem and some alternative stores. However, users have one big question: How to install Google Play on Windows 11. Google's ecosystem is too large and varied to give up, and the lack of cooperation between the two giants leaves only one option... doing the work ourselves. The web already offers ready-to-use packages, but you'll have to get your hands dirty once more...
It All Starts with a Script
The GitHub user ADeltaX shared a script called WSAGAScript that helps us install the GApps package inside a Windows Subsystem for Android image, and enable optional root access. The problem is that his installation guide is a real nightmare. It requires Windows Subsystem for Linux, cloning the repository, assigning permissions for other scripts, and more.
Fortunately, we can save a lot of time by using some already processed and modified packages. As always, this carries some risk because we don't know their origin, but the ETA PRIME channel shared an excellent step-by-step with the main details, and I must admit his method is simpler. If you want to know how to install Google Play on Windows 11 this way, keep reading.
How to Install Google Play on Windows 11, Step by Step
- First, you must verify that all virtualization functions are enabled correctly on your computer. That includes a visit to the UEFI to check the options there, then go to the classic Control Panel, enter Programs and Features, click on Turn Windows features on or off, and select Virtual Machine Platform. Restart your computer.
- **Enable Developer Mode in Windows 11**. This is easy: Settings - Privacy & security - For developers, and finally Developer Mode. Windows 11 will show a warning, accept it anyway.
- **You'll need to download three files:** The 15 seconds ADB Installer available in the XDA Developers forums, the modified Windows Subsystem for Android image, and a replacement kernel. Both the WSA image and the kernel were uploaded to MEGA. We haven't detected anything strange in them, but we must mention where they come from.
- **Proceed to install ADB.** Extract the contents of the zip, and double-click the executable. Select 'Y' for the three questions the installer asks, and let it install the Google ADB driver. This all takes a few seconds.
- **Extract the contents of the Windows Subsystem for Android image into a temporary folder**. I also recommend **renaming it to 'WSA' and moving it to the root of some drive** so it's more comfortable to work with later.
- **Copy the kernel file** into the WSA folder. Note that the kernel file has no extension.
- **Open PowerShell with elevated privileges**, and go to the WSA folder where all the files are ready to be installed.
- Run the command Add-AppxPackage -Register .\AppxManifest.xml. That will install Windows Subsystem for Android on the system.
- **Open Windows Subsystem for Android, enable developer mode, and then click Files**. Microsoft will ask for feedback, but you can disable it.
- The first load always takes a while, but don't forget that the program will show a warning if your computer has less than 8 GB of RAM, and you should definitely allow any firewall exceptions. While all this happens, Google Play Store installs in the background. Be patient.
- If you try to access Google Play Store now, you'll find that you can't because the sign-in button doesn't work. **This is fixed with ADB: Open the system console with elevated privileges, and go to the ADB folder.**
- Run ADB once to check it works (this will show a list of all its commands), but before continuing you must go back to the Windows Subsystem for Android settings, **and get the connection IP address**. It's right below developer mode. Click Refresh if it doesn't appear.
- Back in ADB, run the command adb connect with the IP address generated in WSA. The daemon will start automatically. If you get a connection error, remember you need those firewall exceptions, or it will be impossible to connect to WSA. At the same time, the connection can be a bit picky, but restarting the computer should resolve any issue.
- We only have three commands left to run: The first is adb shell, which takes us to the redfin shell. The second is su, because we need to work as root. The last command is setenforce 0. Once confirmed, you can close the window or type exit three times to exit.
- We're ready! Open Google Play, and enter your Google credentials (you can always use an alternative account if you don't want to use your main one). This will set up WSA as if it were another device on your profile. Try installing an app!
Possible Issues
WSA doesn't generate an IP address to connect ADB: Restart your computer. Yes, really. I only encountered this problem once. When clicking Refresh the address didn't appear, but restarting the computer, running ADB once, and toggling developer mode in WSA was enough to get the address.
(Insert app here) doesn't work or isn't available: The fact that installing Google Play on Windows 11 should noticeably improve compatibility for many apps, but don't forget there are also architecture differences. The entire environment is interpreted as x86, and some applications have a problem with that. As an alternative, you can always experiment with sideloading and try to force things...
I want to add Google Play to an already installed WSA: From what I've seen so far, it's not recommended. Fortunately, uninstalling any build of Windows Subsystem for Android is as easy as right-clicking its icon and choosing Uninstall. It'll be much more comfortable for you if you start from scratch.
Good luck!
ETA PRIME's YouTube channel: Click here
