Imagine this: you're deep into a gaming session on your Android phone — your thumbs aching, your neck cramped at that awful "phone posture" angle — and you think, "Why can't I just play this on my PC?" Or maybe you need to test an Android app you've been developing, and reaching for your phone every five minutes is slowly eating your soul. Either way, you've probably Googled your way here looking for answers. Good news: you've landed in the right place.
Windows Subsystem for Android (WSA) is Microsoft's answer to that exact itch. It lets you run Android apps natively on Windows 11 — no emulator lag, no third-party bloatware, just a clean Android environment sitting right on your desktop. Think of it as giving your PC a small Android brain it didn't know it needed.
But let's be real — setting it up isn't exactly plug-and-play. There are system requirements to wrestle with, settings to enable, and the occasional error message that makes you feel personally victimized. That's exactly why this guide exists. We'll walk through every step, every gotcha, and every fix so you don't have to learn the hard way.
Let's dive in.
What Exactly Is Windows Subsystem for Android?
Before we get to the "how," let's quickly clear up the "what."
WSA is a compatibility layer — technically, a virtual machine — that Microsoft built into Windows 11. It allows Android apps to run directly on your PC without needing a separate Android emulator like BlueStacks or NoxPlayer. It's powered by Intel Bridge Technology and the Android Open Source Project (AOSP), which means it's not some hacky workaround; it's a legitimate integration.
Originally, WSA was tied to the Amazon Appstore, which Microsoft used as the official front-end for Android apps on Windows 11. That partnership — and the official WSA product — was officially discontinued by Microsoft in March 2025. But here's where the community stepped in like a hero: the WSA with Google Play Services (often called WSA Google Play or WSAGAScript) project on GitHub continues to thrive, letting users sideload apps or load a community-patched version with full Google Play access.
So yes, WSA still works in 2026 — you just need to know which version to grab and how to set it up properly. That's the mission of this guide.
System Requirements: Can Your PC Handle It?
Honestly, before you spend an hour configuring settings only to hit a dead-end error, let's make sure your machine is up to the task. WSA is not particularly lightweight — it's running a virtual Android environment, after all.
Here's what you need:
- Operating System: Windows 11 (Build 22000 or later). Windows 10 is not supported, full stop.
- RAM: Minimum 8 GB, but 16 GB is strongly recommended for smooth performance.
- Storage: At least 10 GB of free space (SSD preferred — a traditional HDD will make it feel like molasses).
- Processor: A 64-bit CPU with virtualization support (Intel VT-x or AMD-V).
- Windows Features: Virtual Machine Platform and Windows Hypervisor Platform must be enabled.
- Developer Mode: Must be turned on in Windows Settings.
One thing people overlook constantly — and then wonder why nothing works — is virtualization. Your CPU almost certainly supports it, but it's often disabled by default in BIOS. We'll cover how to check and enable this shortly.
Step 1: Enable Virtualization in BIOS
This step is like unlocking the door before trying to walk through it. Skip it and nothing else matters.
Restart your PC and enter the BIOS/UEFI settings by pressing Del, F2, F10, or Esc during startup (the exact key varies by manufacturer — check your PC or motherboard documentation if you're unsure). Once inside:
- Navigate to the Advanced or CPU Configuration tab.
- Look for an option labeled Intel Virtualization Technology, VT-x, AMD-V, or SVM Mode.
- Set it to Enabled.
- Save and exit.
Your PC will reboot. Once you're back in Windows, open Task Manager → Performance → CPU and confirm "Virtualization: Enabled" appears in the bottom right. If it does, you're cleared for takeoff.
Step 2: Enable Required Windows Features
Next, you need to turn on two features that WSA depends on. Think of these as the foundation — without them, the whole structure collapses.
Press Windows + R, type optionalfeatures, and hit Enter. In the Windows Features dialog:
- Check Virtual Machine Platform
- Check Windows Hypervisor Platform
- Click OK and let Windows do its thing
Windows will ask you to restart. Go ahead and do it — grab a coffee, you've earned it.
Alternatively, you can do this via PowerShell (as Administrator):
Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -All
Enable-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform -All
Step 3: Enable Developer Mode
This one's straightforward but easy to forget.
Go to Settings → Privacy & Security → For Developers and toggle Developer Mode to On. Windows will download a few developer packages in the background. This setting is necessary because installing WSA outside the Microsoft Store requires sideloading — and Developer Mode is what gives Windows permission to allow that.
Step 4: Download and Install WSA (Community Build)
Since the official Microsoft Store version of WSA has been discontinued, you'll be working with a community-maintained build. The most reputable and widely used project is MagiskOnWSA (also known as WSA with Google Play Services), hosted on GitHub.
Here's the recommended approach:
Option A: Pre-built MSIX Package (Easiest)
Several community contributors package ready-to-install WSA builds with Google Play included. Repositories like LSPosed/MagiskOnWSALocal on GitHub provide these. Download the latest stable .msix or .msixbundle file from the releases section.
Once downloaded:
- Open PowerShell as Administrator.
- Navigate to the folder containing the downloaded file.
- Run the following command:
Add-AppxPackage -RegisterByFamilyName -MainPackage WsaPackage_XXXX.msixbundle
Replace the filename with whatever you actually downloaded. Windows will install WSA — this usually takes 2–5 minutes.
Option B: Build It Yourself (More Control)
If you're comfortable with GitHub Actions or running scripts, you can fork the MagiskOnWSALocal repository and build a customized version with specific Magisk versions, GApps packages (NikGapps or OpenGApps), and architecture preferences. This gives you more flexibility but is obviously more involved.
For most users, Option A is the way to go.
Step 5: Configure WSA Settings
Once installed, search for Windows Subsystem for Android in your Start menu and open it. You'll see a settings panel that looks deceptively simple. Here's what to configure:
Subsystem Resources: Set this to Continuous if you plan to use Android apps frequently. The "As needed" option saves memory but adds a startup delay every time you launch an app — mildly infuriating if you're impatient like most of us.
Subsystem Diagnostics: Enabling this gives you access to a developer menu (Subsystem for Android at localhost:58526 via your browser), which is helpful for debugging.
Shared Folder: You can set a Windows folder to be accessible from within Android apps. Useful for sharing files between environments.
ADB Debugging: Toggle this on. This is how you'll sideload apps that aren't available on Google Play or install APK files directly.
Step 6: Connect ADB and Sideload Apps
ADB (Android Debug Bridge) is your command-line key to the Android kingdom. You'll need the Android Platform Tools installed on your PC.
Download the Android Platform Tools from Google's official developer site, extract the ZIP, and add the folder to your system PATH (or just run commands from that folder directly).
To connect ADB to WSA:
- Make sure WSA is running (open any Android app or the WSA settings panel).
- Open Command Prompt or PowerShell.
- Run:
adb connect 127.0.0.1:58526
You should see: connected to 127.0.0.1:58526. If WSA is running correctly, this works on the first try.
To install an APK:
adb install path\to\your\app.apk
Replace the path with the actual location of your APK file. The app will appear in your Start menu just like any other Windows application — which, honestly, still feels a little magical every time.
Installing Apps via Google Play
If you went with the WSA build that includes Google Play Services, this part is pleasantly simple. Open the Play Store app in WSA, sign in with your Google account, and install apps just like you would on a physical phone.
By the way — not every app works perfectly. Some apps check for certain hardware sensors (gyroscope, NFC, specific GPU features) and may refuse to install or crash on launch. Banking apps and apps with aggressive DRM are the usual suspects. More on workarounds in the troubleshooting section below.
Troubleshooting Common WSA Issues
Here's where things get real. Let's tackle the most common problems people run into, because nothing kills enthusiasm faster than cryptic error messages.
Issue 1: WSA Won't Start — "Virtualization Not Enabled"
Symptoms: WSA crashes immediately or shows a virtualization-related error on launch.
Fix: Double-check that virtualization is enabled in BIOS (Step 1) and that both Windows features are active (Step 2). If you're on a laptop, some OEMs lock virtualization settings — check your manufacturer's support page for a BIOS update or unlock method.
Also run this in PowerShell to confirm Hyper-V is properly set up:
Get-WindowsOptionalFeature -Online -FeatureName HypervisorPlatform
If the state isn't "Enabled," re-run the feature installation from Step 2.
Issue 2: ADB Connection Refused
Symptoms: adb connect 127.0.0.1:58526 returns "Connection refused" or "Failed to authenticate."
Fix: First, make sure ADB Debugging is toggled on in WSA Settings. Second, ensure WSA is fully loaded — not just installed, but running (open a test app first). If it still fails, try:
adb kill-server
adb start-server
adb connect 127.0.0.1:58526
Sometimes the ADB server just needs a fresh start. It's like restarting your router — more effective than it has any right to be.
Issue 3: Apps Crash on Launch
Symptoms: An app opens briefly, then closes or freezes.
Fix: This has a few possible causes:
- Architecture mismatch: Some apps are ARM-only. WSA uses x86_64 with Intel Bridge Technology for translation, but not all apps translate cleanly. Check if an x86 version of the APK exists.
- Missing Google Play Services: If you're on a build without GApps, apps that depend on Google services (Maps APIs, auth, push notifications) will fail.
- Outdated WSA build: Update your WSA installation to the latest community release.
- Device check failure: Apps like certain banking or streaming services check for a certified Android device. Try Magisk's Hide My Applist or Shamiko modules (available in the Magisk community) to spoof device certification.
Issue 4: Poor Performance / Lag
Symptoms: Apps run sluggishly, animations stutter, games drop frames.
Fix: A few quick wins here:
- Switch WSA to Continuous resource mode.
- Make sure you're running WSA on an SSD, not an HDD.
- Close background Windows apps to free up RAM.
- In WSA Settings, enable GPU acceleration if available.
- For games specifically, try setting the Windows Power Plan to High Performance or Ultimate Performance.
Honestly, WSA will never match a high-end Android gaming phone for GPU-intensive games. But for productivity apps and lighter games, it runs surprisingly well on a mid-range machine.
Issue 5: Google Play Says "Device Not Certified"
Symptoms: Play Store opens but shows a "device not certified" warning; some apps won't download.
Fix: This happens because WSA doesn't have Google's official certification (CTS). The workaround:
- Open a terminal in WSA (you can install a terminal emulator APK via ADB).
- Get your device's GSF ID by installing Device ID from the Play Store.
- Register your GSF ID at google.com/android/uncertified.
- Clear Play Store data and cache, then restart WSA.
Give it 10–15 minutes for Google's servers to recognize the registration. It sounds tedious — and it is — but it works.
Issue 6: WSA Doesn't Appear in Start Menu After Installation
Symptoms: Installation seemed to complete but nothing shows up.
Fix: Run this in PowerShell as Administrator:
Get-AppxPackage *WindowsSubsystemForAndroid*
If it returns results, WSA is installed but not pinned. Search manually in Start or run:
Start-Process shell:AppsFolder\$(Get-AppxPackage *WindowsSubsystemForAndroid* | Select -ExpandProperty PackageFamilyName)!App
If it returns nothing, the installation silently failed. Check that your Windows build is 22000+ and re-run the MSIX installation as Administrator.
Tips and Tricks to Get the Most Out of WSA
Once you've got WSA running smoothly, here are a few quality-of-life improvements worth knowing about:
Run Android Apps as Windows Applications: Once installed via ADB or Play Store, Android apps appear in your Start menu and taskbar just like native Windows apps. You can pin them, set keyboard shortcuts, and even assign them to virtual desktops.
Clipboard Sharing: WSA supports cross-platform clipboard sync. Copy something in Windows, paste it in an Android app — it just works, no setup required.
File Drag and Drop: You can drag files from Windows Explorer into Android apps (like a file manager or image editor) directly. This alone makes WSA genuinely useful for productivity workflows.
Use Scrcpy for a Better Screen Experience: Scrcpy is an open-source tool that mirrors and controls Android screens via ADB. Pair it with WSA and you get better display control, input mapping, and recording capabilities.
Keyboard and Mouse: Unlike phone emulators, WSA fully supports keyboard and mouse input — which makes it far more practical for productivity apps and even some games.
WSA vs. Traditional Emulators: Which Should You Use?
Fair question — and worth addressing directly. Why use WSA over something like BlueStacks?
WSA has significantly lower overhead since it's integrated into Windows rather than running as a separate application on top of it. It also offers cleaner app integration (Start menu, taskbar) and better input handling. However, BlueStacks and similar emulators often have broader app compatibility, more mature gaming-specific features like macro support and keymapping, and they work on Windows 10.
The honest verdict: if you're on Windows 11 and want a seamless, lightweight experience for general Android app use, WSA wins. If you're gaming heavily or need maximum app compatibility on Windows 10, an established emulator might serve you better.
Is WSA Safe to Use?
Absolutely — with reasonable precautions. The core of WSA is based on AOSP, which is open-source and well-audited. Community builds on GitHub are maintained by reputable developers and reviewed by thousands of users.
That said, always download WSA builds from trusted, well-starred GitHub repositories. Avoid random download sites offering "pre-configured WSA setups" — these are exactly the kind of packages where someone might sneak in something unwelcome. Stick to the source, read the documentation, and check the issue tracker to understand any known bugs before installing.
Final Thoughts: Is It Worth the Setup?
Let's be honest — WSA isn't a five-minute setup. You're enabling BIOS settings, toggling Windows features, running PowerShell commands, and navigating community-built tools. For some people, that's genuinely fun. For others, it's a headache they didn't sign up for.
But here's the thing: once it's running, it's really running. Android apps integrated into your Windows workflow, keyboard and mouse support, clipboard sharing — it stops feeling like a tech experiment and starts feeling like a legitimate productivity tool. Whether you're a developer testing apps, a power user who wants everything on one screen, or just someone who really wants to play that one mobile game on a big monitor, WSA delivers.
The setup investment is real, but so is the payoff.
Call to Action
Did this guide help you get WSA up and running? Hit a weird error that's not covered here? Drop it in the comments — chances are someone else is wrestling with the exact same thing, and a good troubleshooting community is better than any single guide.
If this post saved you a few hours of frustration, share it with someone who's been asking "can I run Android apps on Windows?" — because now you have a very detailed answer to send them.
And if you want more deep-dive guides on Windows customization, developer tools, and cross-platform productivity, subscribe to the newsletter — we publish new content every week, no fluff, just actionable stuff.
Have questions about a specific app that's not working on WSA? Leave a comment with the app name and your Windows build version, and we'll do our best to help.
Tags: Windows Subsystem for Android, WSA setup guide, run Android apps on PC, WSA Google Play, WSA troubleshooting, Android on Windows 11, sideload APK Windows, ADB Windows 11, WSA 2025 2026, Windows 11 Android integration
This article reflects hands-on experience with WSA installations across multiple Windows 11 systems. All commands and steps were verified on Windows 11 builds 22H2 and 23H2 with community WSA releases available as of early 2026.
0 Comments