Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Cannot run on Copilot+ PCs and other ARM64 Windows 11 devices #325

Open
TGSAN opened this issue Mar 3, 2024 · 43 comments
Open

[BUG] Cannot run on Copilot+ PCs and other ARM64 Windows 11 devices #325

TGSAN opened this issue Mar 3, 2024 · 43 comments
Labels
Bug Something isn't working Investigation Needed This issue need futher investigation

Comments

@TGSAN
Copy link

TGSAN commented Mar 3, 2024

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
Copy link

FEI352 commented Mar 13, 2024

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

@TGSAN
Copy link
Author

TGSAN commented Mar 13, 2024

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
Copy link
Owner

MustardChef commented Mar 13, 2024

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

@Wapitiii
Copy link

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

@MustardChef
Copy link
Owner

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
Copy link

Wapitiii commented Apr 14, 2024

Including LTS Builds?

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

@MustardChef
Copy link
Owner

Including LTS Builds?

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

What ARM CPU do you have?

@Wapitiii
Copy link

Wapitiii commented Apr 14, 2024

What ARM CPU do you have?

Snapdragon 8cx Gen 3

@Wapitiii
Copy link

Wapitiii commented Apr 15, 2024

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
Copy link

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
Copy link
Owner

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
Copy link
Owner

MustardChef commented Apr 25, 2024

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

@MustardChef MustardChef added Bug Something isn't working Investigation Needed This issue need futher investigation labels Apr 25, 2024
@Aloereed
Copy link

All builds can't run on ASUS Vivobook S 15 (X1E-78-100), even the official one.

@HappyMax0
Copy link

Can't run on Surface Pro 11th, X Plus version

@MustardChef
Copy link
Owner

Can't run on Surface Pro 11th, X Plus version

@HappyMax0 Even the official version?

@HappyMax0
Copy link

HappyMax0 commented Jun 19, 2024 via email

@MustardChef
Copy link
Owner

Seems like something was removed in 24H2.
Without access to a Snapdragon X processor system or 24H2, I cannot diagnose the issue.
Guess we should wait until someone finds the cause.

@2001zhaozhao
Copy link

Happens on Surface Pro 11 w Snapdragon X Elite as well.

The VmmemWSA seems to hang a certain number of CPU threads to 100% for a few minutes and then closes. The GApps Amazon Magisk one hangs between 4-7 threads seemingly randomly. The KernelSU one always only hangs one thread (constant 8% CPU usage). Changing display driver makes no difference. Haven't tried the GApps-less versions yet

@Wapitiii
Copy link

Seems like something was removed in 24H2.

I've upgraded from 23h2 to 24h2, WSA still works on my arm64 device with the 8cx gen 3.
image

@2001zhaozhao
Copy link

Ok tried both the Amazon only WSABuilds as well as the official WSA. These also don't work but with a different behavior. Both crash during launch quickly, getting to about 400MB memory usage before shutting down. I'm starting to think maybe Microsoft just didn't bother with WSA support on these new CPUs

@MustardChef MustardChef pinned this issue Jun 19, 2024
@HappyMax0
Copy link

HappyMax0 commented Jun 19, 2024 via email

@MOONOTUS
Copy link

MOONOTUS commented Jun 24, 2024

Each version don't work on Surface Pro 11 with XElite inside, also the official version installed by install Amazon Store.
They have similar behavior —— run for a minute and show four same window what titled "Windows Subsystem of Android", and then all closed. The IP could be correct during the first time of trying starting, and then the port will changes to 0.

@raptor1jec
Copy link

Each version don't work on Surface Pro 11 with XElite inside, also the official version installed by install Amazon Store. They have similar behavior —— run for a minute and show four same window what titled "Windows Subsystem of Android", and then all closed. The IP could be correct during the first time of trying starting, and then the port will changes to 0.

Yes this is exactly what's happening on my Surface Laptop 7.

@jom-g
Copy link

jom-g commented Jun 28, 2024

Each version don't work on Surface Pro 11 with XElite inside, also the official version installed by install Amazon Store. They have similar behavior —— run for a minute and show four same window what titled "Windows Subsystem of Android", and then all closed. The IP could be correct during the first time of trying starting, and then the port will changes to 0.

Same here for my X Plus Surface Pro 11

@josh900
Copy link

josh900 commented Jun 28, 2024

Same for lenovo 7x snapdragon x elite

@MustardChef MustardChef changed the title [BUG] Cannot run in ARM64 devices [BUG] Cannot run On some ARM64 devices and Copilot+ PCs Jun 30, 2024
@MustardChef MustardChef changed the title [BUG] Cannot run On some ARM64 devices and Copilot+ PCs [BUG] Cannot run on Copilot+ PCs and other ARM64 Windows 11 devices Jun 30, 2024
@snickler
Copy link

@MustardChef - If you modify the vendor and system partitions, set the properties to make it an arm64-v8 only distro, replace the armv7 binaries/services with armv8 versions, this will be resolved. I'm going to try and write up some instructions to repro how I made it work through all my trial/error.

Buuuuuuut... Here ya go. And I owe it to your build.sh script to show how to PROPERLY mount these partitions as rw then convert back to vhdx. That saved my arse, because manually editing via hex editor / Notepad++ was not fun.

https://x.com/sinclairinat0r/status/1812676637953019964

@snickler
Copy link

https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/

https://github.com/snickler/WSA-Patched/releases/tag/0.0.1 <-- I zipped up my system and vendor vhdx. The same exact steps on here to do the custom WSA install folder apply for replacing the vhdxs. There's some things not implemented properly. The Camera doesn't work due to one of the media components still being armv7, but I'm sure someone with actual experience with Android internals can fix this.

BTW, I pulled the armv8 versions and some of the changes from one of the Android 13 Armv8 Google emulators.

@MustardChef - If you want to play around with these and modify, feel free :).

@arasshah
Copy link

https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/

https://github.com/snickler/WSA-Patched/releases/tag/0.0.1 <-- I zipped up my system and vendor vhdx. The same exact steps on here to do the custom WSA install folder apply for replacing the vhdxs. There's some things not implemented properly. The Camera doesn't work due to one of the media components still being armv7, but I'm sure someone with actual experience with Android internals can fix this.

BTW, I pulled the armv8 versions and some of the changes from one of the Android 13 Armv8 Google emulators.

@MustardChef - If you want to play around with these and modify, feel free :).

First thank you for your big achievement
I have a question it work this patch for me but I have a problem all Apps that must run a video
Iptv youtube brave browser when I open youtube websit not working . Do you have any idea why ??!

@snickler
Copy link

https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/
https://github.com/snickler/WSA-Patched/releases/tag/0.0.1 <-- I zipped up my system and vendor vhdx. The same exact steps on here to do the custom WSA install folder apply for replacing the vhdxs. There's some things not implemented properly. The Camera doesn't work due to one of the media components still being armv7, but I'm sure someone with actual experience with Android internals can fix this.
BTW, I pulled the armv8 versions and some of the changes from one of the Android 13 Armv8 Google emulators.
@MustardChef - If you want to play around with these and modify, feel free :).

First thank you for your big achievement I have a question it work this patch for me but I have a problem all Apps that must run a video Iptv youtube brave browser when I open youtube websit not working . Do you have any idea why ??!

Likely related to the same issue of the media service I haven't gotten to work properly yet, which is likely causing the issue I have with /storage/emulated/0 not being mounted properly. I'm trying to see if I can pull something else from the android emulator that would work.

@2001zhaozhao
Copy link

2001zhaozhao commented Jul 25, 2024

I tried the patched WSA and it does work, which is amazing!
It is quite buggy though. Unfortunately Amazon Appstore does not let me log in (the verification code step doesn't respond), and same goes for Kindle. Mobile firefox doesn't seem to be able to load any webpage. I'd love to see these issues ironed out.

Btw if you already have WSA from WSABuilds installed, I haven't tried but you should be able to just copy the two files from wsa-patched.7z into your WSA installation folder (replacing the files that are already there) and this should result in a working WSA installation. Of course it won't include things like google play services though.

Edit: Authenticator app login on Amazon account does work. Weird. Might be my internet since i am on mobile hotspot.

@MustardChef
Copy link
Owner

MustardChef commented Jul 26, 2024

@snickler Thank you for the great work.
It would be quite helpful if you would detail the process of patching WSA to allow it to run on Snapdragon X SoCs/Copilot+ PCs and the specific components pulled from the Android 13 ARMv8 AVDs.
This would allow me to push builds compatible with Snapdragon X SoCs/Copilot+ PCs with Google Play Store and Root etc.
It will also allow other developers to build upon your work to help improve compatibility.

@snickler
Copy link

@snickler Thank you for the great work.
It would be quite helpful if you would detail the process of patching WSA to allow it to run on Snapdragon X SoCs/Copilot+ PCs and the specific components pulled from the Android 13 ARMv8 AVDs.
This would allow me to push builds compatible with Snapdragon X SoCs/Copilot+ PCs with Google Play Store and Root etc.
It will also allow other developers to build upon your work to help improve compatibility.

@MustardChef I totally agree with that. I'm going to finish up the process details tonight and link to them. It makes the most sense.

Also, I would LOVE to have help around figuring out why vold isn't mounting /data/media properly. That one of the biggest bugs I have right now. The process details should be helpful with that.

@josh900
Copy link

josh900 commented Jul 27, 2024

Niceeee

@arasshah
Copy link

Does the Amazon app verification work with you, or multimedia such as YouTube in the browser, or any app that contains a video player?"

@snickler
Copy link

Does the Amazon app verification work with you, or multimedia such as YouTube in the browser, or any app that contains a video player?"

No, not yet. BUUTTTT

https://x.com/sinclairinat0r/status/1817326463634338105

^^ I've made a milestone that involves the emulated storage working! Camera works too for taking pictures, but fails when recording (likely the same issue related to anything involving video). I should have enough of my trial/erroring done to write steps on how to modify an unmodified image to put it in this "mostly" working state.

@josh900
Copy link

josh900 commented Aug 11, 2024

@snickler Do you have any instructions or modified files? I tried extracting (7-zip) system.vhdx and vendor.vhdx from the amazon+Gapps latest, removing all 32-bit components and references, and repackaging the files.
It installed but with the same issue of not having any apps, and continuous loading screen.

@HappyMax0
Copy link

HappyMax0 commented Aug 11, 2024 via email

@cksachdev
Copy link

cksachdev commented Sep 6, 2024

I tried on Surface Pro 11 Copilot PC arm64 and getting similar issue.

Version installed: WSA_2407.40000.0.0_arm64_Release-Nightly-GApps-13.0-NoAmazon
Extracted in: C:\WSA_2407.40000.0.0_arm64E

The popup appears which shows
image

This popup stays for a minute and then closes without any errors.

Windows version:
image

@snickler : Here is a sequence of what I tried:

  1. Downloaded and installed WSA_2407.40000.0.0_arm64E (WSA_2407.40000.0.0_arm64_Release-Nightly-GApps-13.0-NoAmazon.7z)
  2. Output is as above
  3. Based on instructions from https://www.xda-developers.com/windows-subsystem-for-android-snapdragon-how-to/ there were no AppxBlockMap.xml and AppxSignature.p7x in C:\WSA_2407.40000.0.0_arm64E
  4. Executed
Get-AppxPackage -AllUser | Where {$_.Name -match "SubsystemForAndroid"} | Remove-AppxPackage -AllUsers
  1. Pasted the 2 files from your pre-release 0.0.1 in C:\WSA_2407.40000.0.0_arm64E
  2. Tried running the Run.bat
  3. Still similar output
  4. Tried running the following command
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml
  1. Still similar output
  2. Tried 0.0.2 and replaced all 4 files in C:\WSA_2407.40000.0.0_arm64E
  3. Tried running following command
Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml

Please suggest if I am missing or having a wrong sequence of steps.

Note: I haven't tried uninstallation, as there were no AppxBlockMap.xml and AppxSignature.p7x in my installation directory.

@GuyZhangZhang
Copy link

GuyZhangZhang commented Oct 12, 2024

Same issue. I got application crash on my copilot pc:

Faulting application name: WsaClient.exe, version: 2311.40000.5.0, time stamp: 0x6595e732
Faulting module name: ucrtbase.dll, version: 10.0.26100.2033, time stamp: 0xd393af07
Exception code: 0xc0000409
Fault offset: 0x000000000007c31c
Faulting process id: 0x721C
Faulting application start time: 0x1DB1C7CD9F833E9
Faulting application path: C:\Users\guyxt\OneDrive\Apps\WSA\WsaClient\WsaClient.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 62b40888-5802-4fe8-9572-ef5abd5062e9
Faulting package full name: MicrosoftCorporationII.WindowsSubsystemForAndroid_2311.40000.5.0_arm64__8wekyb3d8bbwe
Faulting package-relative application ID: App

image

If need any further information, i can try to provide

@hohoaisan
Copy link

hohoaisan commented Nov 13, 2024

the same issue related to anything involving video

Would love to see if Video issue will be resolved

@massoudasadi
Copy link

same issue

@vladimir-scat
Copy link

This version started successfully on snap 8cx gen3

WSA_2307.40000.6.0_arm64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon

@n-ver
Copy link

n-ver commented Dec 30, 2024

Snapdragon X Elite:

Tried a normal install with WSA_2407.40000.4.0_x64_Release-Nightly-with-KernelSU-v1.0.2-MindTheGapps-13.0-RemovedAmazon, which was never able to launch. Replacing vendor.vhdx and system.vhdx with the custom patch also failed. WSA_2307.40000.6.0_arm64_Release-Nightly-MindTheGapps-13.0-RemovedAmazon ran into the same issue, but applying the patch here actually worked. Google appstore is stubbornly stuck on "checking info", though...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Investigation Needed This issue need futher investigation
Projects
None yet
Development

No branches or pull requests