[BUG] Cannot run in ARM64 devices

[TGSAN]

Describe the bug

After installation, I found that the WSA settings app lost i18n, so it will only display the English interface. At the same time, when starting, it will display the Starting Windows Subsystem for Android™ window, and then disappear after a few minutes. During the window display, I noticed that vmmemCmZygote had no memory usage changes.

Steps to reproduce the issue

1. Download WSA_2311.40000.5.0_arm64_Release-Nightly-with-KernelSU-v0.7.5-MindTheGapps-13.0-RemovedAmazon.7z
2. Extract and move folder to a suitable location.
3. Run Run.bat
4. Start WSA.

Expected behaviour

WSA started

Downloaded Build Of WSA

WSA_2311.40000.5.0_arm64_Release-Nightly-with-KernelSU-v0.7.5-MindTheGapps-13.0-RemovedAmazon.7z
In GitHub release page.

Windows build number

10.0.22635.3212

PC Specification

System Model Surface Pro X
System Type ARM64-based PC
Processor Microsoft SQ1 @ 3.0 GHz，2995 Mhz，8 Cores
RAM 16.0 GB

Additional context

No response

[FEI352]

galaxybook2 扩容的8G表示可以正常的使用，比我三年前装的好多了。不过同样是只显示英文。

[TGSAN]

I tried and found that only the KernelSU version fails to boot. Additionally, the loss of i18n is due to makepri.exe becoming a file without an extension. Switching to a version other than KernelSU and then changing makepri.exe back to its original state resolves the issue.

[MustardChef]

Thank you for the info.
Issue will be fixed in the first WSABuilds LTS update.

[Wapitiii]

For me every build doesnt work, the only one that works is the official one from the microsoft store on my arm64 device.

[MustardChef]

For me every build doesnt work, the only one that works is the official one from the microsoft store on my arm64 device.

Including LTS Builds?

[Wapitiii]

Including LTS Builds?

Yep, tried latest build. It just loads and then closes itself.

[MustardChef]

Including LTS Builds?

Yep, tried latest build. It just loads and then closes itself.

What ARM CPU do you have?

[Wapitiii]

What ARM CPU do you have?

Snapdragon 8cx Gen 3

[Wapitiii]

Hey @MustardChef i've found something related about that issue:

Protocol name: Application
Source: Application Error
Date: 15.04.2024 23:36:43
Event ID: 1000
Task Category: Application Crash Events
Level: Error
Keywords:
User: X13S-THINKPAD\Admin
Computer: X13S-THINKPAD
Description:
Faulting application name: WsaClient.exe, Version: 2311.40000.5.0, Timestamp: 0x6595e732
Faulting module name: ucrtbase.dll, Version: 10.0.22621.3374, Timestamp: 0xac93a291
Exception code: 0xc0000409
Fault offset: 0x0000000000076ebc
Faulting process ID: 0x1878
Faulting application start time: 0x1DA8F7CB72007AD
Faulting application path: C:\Users\Admin\Documents\WSA\WsaClient\WsaClient.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report ID: 373befac-ee9b-4676-81c2-bcc4677c8945
Full name of the faulty package: MicrosoftCorporationII.WindowsSubsystemForAndroid_2311.40000.5.0_arm64__8wekyb3d8bbwe
Application ID relative to the faulty package: App

WinDBG:
0:034> g
00:17:03.423244 ~ Heartbeat timeout ignored due to attached debugger.
ModLoad: 00007ff834680000 00007ff8346a0000 C:\Windows\system32\wbem\wbemprox.dll
ModLoad: 00007ff845c60000 00007ff845d77000 C:\Windows\SYSTEM32\wbemcomn.dll
ModLoad: 00007ff838230000 00007ff83825d000 C:\Windows\system32\wbem\wbemsvc.dll
ModLoad: 00007ff836580000 00007ff8367bb000 C:\Windows\system32\wbem\fastprox.dll
ModLoad: 00007ff8336d0000 00007ff833705000 C:\Windows\SYSTEM32\amsi.dll
ModLoad: 00007ff8316e0000 00007ff8317a5000 C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.24030.9-0\MpOav.dll
ModLoad: 00007ff840c80000 00007ff840c95000 C:\Windows\system32\version.dll
D:\a_work\1\s\WsaClient\Framework\InstanceManager.cpp(1348)\WsaClient.exe!00007FF60F259064: (caller: 00007FF60F25C7E8) Exception(2) tid(4d44) 80370109 The process encountered a timeout because no response was received from the virtual computer or container.
CallContext:[\InstanceManagerRun\StartNewSession]
(6c8.4d44): C++ EH exception - code e06d7363 (first chance)
(6c8.4d44): Unknown exception - code c000041d (!!! second chance !!!)
KERNELBASE!RaiseException+0x54:
00007ff8`583d8464 910243ff add sp,sp,#0x90

[Wapitiii]

I found the only 2 versions that work for me:

WSA_2311.40000.5.0_arm64_Release-Nightly-NoGApps-NoAmazon.7z

WSA_2311.40000.5.0_arm64_Release-Nightly-NoGApps.7z

Might be a gapps issue?

[MustardChef]

I found the only 2 versions that work for me:

WSA_2311.40000.5.0_arm64_Release-Nightly-NoGApps-NoAmazon.7z

WSA_2311.40000.5.0_arm64_Release-Nightly-NoGApps.7z

Might be a gapps issue?

Probably.

[MustardChef]

I have check on a Windows 11 arm64 device (Surface Pro X) and all WSABuilds LTS 1 builds seem to be working for me.