Running Android apps on a Windows desktop can fill gaps where a service only ships a mobile client, and it keeps companion tools available without switching devices.
Windows 11 delivered Android app support through Windows Subsystem for Android (WSA), which runs an AOSP-based Android environment inside a lightweight virtual machine and integrates app windows and notifications into the Windows shell. App installation was handled through the Amazon Appstore integration, with sideloading available for .apk packages using the ADB debugging interface.
Hardware virtualization must be enabled in firmware, and Windows features such as Virtual Machine Platform must be turned on for WSA to start reliably. Microsoft ended support for WSA on March 5, 2025, and the Amazon Appstore entry was removed from the Microsoft Store, so only systems that already have WSA installed can keep running it. Sideloading bypasses store vetting, so treat third-party .apk files as untrusted until verified.
Important: Starting March 5, 2025, Windows Subsystem for Android and the Amazon Appstore are not available in the Microsoft Store, and no updates or fixes are provided.
New installations are not available from the Microsoft Store after March 5, 2025.
Common labels include Intel Virtualization Technology, VT-x, AMD-V, or SVM Mode.
Some virtualization software may switch to a Hyper-V compatibility mode when this feature is enabled.
Developer mode exposes an ADB debugging endpoint; disable it after sideloading.
This starts the Android environment so the IP address and Port become available.
PS> adb connect 172.30.240.1:58526 connected to 172.30.240.1:58526
Run adb.exe from the platform-tools directory when the command is not found.
PS> adb devices List of devices attached 172.30.240.1:58526 device
PS> adb install .\app-release.apk Performing Streamed Install Success
Only sideload .apk files from trusted sources.