WSA Builds with Google Apps Are Breaking After June 2025—Here's the Fix and Where to Get LTS Releases

If you've been running Android apps on Windows through the Windows Subsystem for Android (WSA), you might have noticed something frustrating lately: apps that used to work fine are suddenly stuck on splash screens, refusing to start, or crashing outright. The culprit? A wave of issues hitting GApps (Google Play Services) builds across Windows 11 after June 2025. The good news is that there's a project actively tracking the problem and shipping fixes—WSABuilds by MustardChef.

WSABuilds is a community project that provides pre-built WSA packages for Windows 10 and 11, bundled with Google Play Services, Magisk, and KernelSU. Think of it as the easiest way to get a fully functional Android environment on your Windows machine without wrestling with build scripts yourself.

What It Does

At its core, WSABuilds is exactly what the name suggests: ready-to-download builds of WSA that come with the Google Play Store and Services baked in. The project is based on MagiskOnWSA, which is the standard toolchain for creating modified WSA packages. But instead of making you run the build process yourself, WSABuilds hosts pre-compiled archives for both Windows 10 and Windows 11, in x64 flavors.

The builds come in two main variants: those with GApps (Google Play Store and Services) and those with NoGApps in the archive name, which skip Google's proprietary components entirely. Both variants include Magisk for root access and KernelSU support, giving you flexibility depending on whether you need Google's ecosystem or prefer a cleaner, Google-free setup.

The project also maintains a dedicated LTS (Long-Term Support) release track. These LTS builds are pinned to specific, stable versions—currently Windows 11 and Windows 10 builds tagged as 2407.40000.4.0_LTS_8—and are the recommended go-to when things go sideways with newer releases.

Why It's Cool

The most compelling thing about WSABuilds right now isn't just that it exists—it's how actively it responds to real-world breakage. The README opens with a big, flashing warning about the June 2025 GApps crash issue, and it doesn't stop at acknowledging the problem. It points you to specific workarounds and tracks progress on a dedicated GitHub issue (#593) and a public project board where you can see exactly what bugfixes are being worked on.

Here's what makes this project stand out:

• LTS releases as a safety net. When the latest builds start acting up, you don't have to hunt through release history hoping to find something stable. The project maintains explicit LTS tags that are known-good, and the README directs affected users straight to them. That's a level of maintenance discipline you don't always see in community projects.

• Clear, actionable troubleshooting. The README doesn't just say "update"—it tells you what to do if apps still misbehave after updating (clear app data and cache, reinstall, or do a clean install with a backup). It also offers alternative paths: switch to NoGApps builds or fall back to older WSA versions (2211/2210) that are known to work.

• Transparency about ongoing issues. Rather than burying known problems, the project surfaces them front and center. You know what's broken, what the current recommended fix is, and where to watch for updates. For developers and power users who rely on WSA daily, that honesty is invaluable.

• Community engagement. There's an XDA Developers thread, a Discord server, and a Ko-fi page for supporting the work. It's clearly a project with an active user base, which means issues get reported, tested, and addressed faster.

How to Try It

Getting started is straightforward. Head over to the WSABuilds GitHub repository and follow these steps:

1. Check the warnings first. If you're running a GApps build on Windows 11 and experiencing crashes, read the top of the README. The recommended fix is linked in issue #593, and you should apply that before anything else.

2. Download the right build. Go to the Downloads section of the README. You'll find separate tables for Windows 10 and Windows 11, with both GApps and NoGApps variants. If you want the latest stable experience, grab the LTS release directly:

   • Windows 11 x64 LTS
   • Windows 10 x64 LTS

3. Extract and install. The archives are .7z files. Extract them to a folder, then run the Install.ps1 script (or follow the installation instructions in the README) to register the WSA package with Windows.

4. If apps still break after updating, clear the problematic app's data and cache, or reinstall it. If that doesn't work, you may need to do a clean install of WSA—just make a backup first.

The README also links to a project board where you can see what fixes and improvements are in progress, so you can gauge when it's worth updating again.

Final Thoughts

WSABuilds is a solid example of what a community-maintained project should look like, especially when the upstream technology (WSA itself) is in a rocky state. It's not flashy—it's practical. The project gives you pre-built, working WSA packages, and when those break, it tells you exactly what to do about it and where to watch for fixes.

If you're someone who runs Android apps on Windows regularly and you've been pulling your hair out over the recent GApps crashes, this is the first place you should check. And even if you're not affected right now, the LTS release track is worth bookmarking for the next time a Windows update or WSA change throws a wrench into your setup.

Follow @githubprojects for more developer tools and open source projects.