[BUG]无法启动所有的安卓程序

[Guiwow-am]

Describe the bug

使用WSA打开一个安卓软件 它显示正在启动适用于Windows的安卓（如图“补充背景”） 但是 过一会之后 那个窗口就消失了 并没有打开我要打开的安卓软件 我重新尝试了好多遍也没有用（这个BUG包括启动安卓的自带的“文件资源管理器” 我怀疑这安卓系统根本没有启动成功）

Steps to reproduce the issue

使用此版本的WSA打开任意一个安卓软件 都有这个问题

Expected behaviour

应该会顺利的打开安卓软件

Downloaded Build Of WSA

WSA_2407.40000.4.0_x64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon.7z
下载链接：https://github.com/MustardChef/WSABuilds/releases/tag/Windows_11_2407.40000.4.0_v2

Windows build number

Windows 11 专业版 版本号：25H2    操作系统版本：26200.8246 

PC Specification

设备：
处理器 Intel(R) Core(TM) Ultra 5 125H (3.60 GHz)
机带 RAM 32.0 GB (31.5 GB 可用)
设备 ID 9AB05955-7A04-48DD-8A82-F198FC719E4A
产品 ID 00330-80000-00000-AA231
系统类型 64 位操作系统, 基于 x64 的处理器
笔和触控 为 10 触摸点提供笔和触控支持

Additional context

[Guiwow-am]

English（By Microsoft Translator）
Describe the bug
Using WSA to open an Android app, it shows that it is starting Android for Windows (as shown in the figure 'Supplementary Background'). However, after a while, that window disappears and the Android app I want to open does not launch. I have tried many times again, but it doesn't work (this bug also occurs when starting the built-in 'File Explorer' of Android. I suspect that the Android system did not start successfully at all).

Steps to reproduce the issue
It should be able to open Android apps smoothly.

Downloaded Build Of WSA
WSA_2407.40000.4.0_x64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon.7z
Downloaded：https://github.com/MustardChef/WSABuilds/releases/tag/Windows_11_2407.40000.4.0_v2

Windows build number
Windows 11 Professional Edition，Version Number: 25H2，Operating System Version: 26200.8246

PC Specification
Processor: Intel(R) Core(TM) Ultra 5 125H (3.60 GHz)
Installed RAM: 32.0 GB (31.5 GB usable)
Device ID: 9AB05955-7A04-48DD-8A82-F198FC719E4A
Product ID: 00330-80000-00000-AA231
System type: 64-bit operating system, x64-based processor
Pen and touch: Pen and touch support with 10 touch points

Additional context

[wesmar]

I figured out the cause through reverse engineering, but I tailored the fix specifically for Windows 11 26H1. Since it's a semantic patch rather than relying on dumb byte patterns, it should likely work on other versions like 24H2, 25H2, and recent updates. Let me know if it helps you.
https://github.com/wesmar/WSAPatch

[mkohlman]

Nice... It did indeed fix the issue for me. Also on 26H1