microsoft / WSA

Developer-related issues and feature requests for Windows Subsystem for Android
MIT License
1.45k stars 798 forks source link

WSA Does Not Function on Surface Laptop 7 #562

Open NetworkGuy149 opened 5 days ago

NetworkGuy149 commented 5 days ago

Steps to reproduce

Use start to open WSA. Click on Files - Does not open Under advanced settings - Click Manage developer settings - Does not open

✔️ Expected Behavior

Expect to see screen open showing files Expect to see screen with dev settings

❌ Actual Behavior

WSA tried to start, it looks like 4 times and then just ends without an error message.

Attached is a recording of what happens

https://github.com/microsoft/WSA/assets/22349492/b1fd737d-468a-4d46-92cd-b068e14de3f2

Other Software

No response

Please specify the version of Windows Subsystem for Android

2311.40000.5.5

sundave1998 commented 4 days ago

can confirm similar behavior from surface pro 11

Wagz123 commented 4 days ago

Can also confirm on surface pro 11th edition with windows 11 pro OS license.

Faulting application name: WsaClient.exe, version: 2311.40000.5.0, time stamp: 0x6595e732 Faulting module name: WsaClient.exe, version: 2311.40000.5.0, time stamp: 0x6595e732 Exception code: 0xc0000409 Fault offset: 0x000000000002290c Faulting process id: 0x400C Faulting application start time: 0x1DAC6AA599BDF20 Faulting application path: C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForAndroid_2311.40000.5.0_arm648wekyb3d8bbwe\WsaClient\WsaClient.exe Faulting module path: C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForAndroid_2311.40000.5.0_arm648wekyb3d8bbwe\WsaClient\WsaClient.exe Report Id: 6e86d308-2ae4-48b9-9fc9-fcee602b5c13 Faulting package full name: MicrosoftCorporationII.WindowsSubsystemForAndroid_2311.40000.5.0_arm64__8wekyb3d8bbwe Faulting package-relative application ID: App

Fault bucket 2047466465880745062, type 5 Event Name: MoBEX Response: Not available Cab Id: 0

Problem signature: P1: MicrosoftCorporationII.WindowsSubsystemForAndroid_2311.40000.5.0_arm64__8wekyb3d8bbwe P2: praid:App P3: 2311.40000.5.0 P4: 6595e732 P5: WsaClient.exe P6: 2311.40000.5.0 P7: 6595e732 P8: 000000000002290c P9: c0000409 P10: 0000000000000007

Attached files: \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9a332674-91cc-453a-af25-ce02922ceb88.tmp.mdmp \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7bafdc73-718a-4899-aeb5-344f52d8cf9b.tmp.WERInternalMetadata.xml WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240619_1_EC_0_inject.etl \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5edfc7f8-d1ae-4fe1-b069-4d3a621c523c.tmp.etl WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9c23840e-8b7e-4bb8-a19c-cacea3e48c5b.tmp.etl \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b4b865b5-d3af-4557-8b9c-c6efe9a08f96.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d2070414-3d2d-4b7a-b42b-0bd90d517c16.tmp.txt \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.021edb06-6e5a-4ae5-ab19-cf4ac764c403.tmp.xml

These files may be available here: \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MicrosoftCorpora_3d899dac5b2d2ec8db2a39301933fe6d42e2cd9_6f911537_57d5a579-bfcc-4d5b-98e0-a0993d2f869e

Analysis symbol: Rechecking for solution: 0 Report Id: 1e439d52-252c-4dcd-9107-284defed255c Report Status: 268435456 Hashed bucket: 0dc101e27570ec0c7c6a0fe71c58a466 Cab Guid: 0

NetworkGuy149 commented 3 days ago

I have been told that WSA not working on the new ARM based Surface is a Known Issue.

Unfortunately MS Support has not been been informed of that and had me re-install Windows 11 and wipe out everything on my laptop.

MOONOTUS commented 3 days ago

It does exactly the same behavior on surface pro 11 running Windows on Arm with XElite inside.