How I run Android apps on Windows with WSA.

The author uses community Windows Subsystem for Android (WSA) builds from GitHub to run Android apps on Windows like native apps, installing from the Play Store or sideloading APKs via Developer Options and ADB; Microsoft ended official WSA support in 2025 but community builds continue to be used.

The article describes running Android apps on Windows using Windows Subsystem for Android (WSA) community builds. The author prefers WSA because apps open in their own windows, appear on the taskbar, and support mouse and keyboard input like native Windows apps. Microsoft officially ended WSA support in 2025, and modified community builds on GitHub are being used to keep the functionality available. The piece outlines setup basics, Play Store sign-in, and sideloading via ADB as reported steps. Key points: - Virtualization features such as Hyper-V and the Virtual Machine Platform should be enabled before installing WSA, according to the article. - The author downloads WSA builds from GitHub; a ‘‘MindtheGapps’’ build is noted to include both the Play Store and the Amazon Appstore, while other builds remove Amazon and include only the Play Store. - Microsoft ended official WSA development in 2025, and community-modified builds are described as the current way to run WSA on Windows. - Installation files in the archive include an install.ps1 that the article says can be run with PowerShell; a Run.bat is mentioned as an alternative if the main window does not appear. - On first launch the WSA interface and an emulated device Settings window should appear; the Apps tab shows installed apps and the Play Store, and Advanced Settings can enable Developer Options for an ADB IP address. - Installed Android apps appear in the Windows Start menu and can open in separate windows, be pinned to the taskbar, and be managed from the WSA interface. Summary: WSA community builds are presented as a way to run Android apps on Windows with native-like behavior, supporting Play Store installs and APK sideloading via ADB. Microsoft’s 2025 end of official support means community maintenance is central to continued use; Undetermined at this time.