search

microsoft / WSA

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

WSA fails to start without reporting errors #407

Open KJZH001 opened 1 year ago

KJZH001 commented 1 year ago

Steps to reproduce

After I click to launch the amazon app store, a popup box appears saying Starting Windows Subsystem for Android (that's the one in the image below)

image

After 10 seconds or so, the window disappears and the app doesn't appear (just like WSA flashed itself) My computer used to run wsa normally, but recently it stopped working, I've tried repairing it, resetting it, and even uninstalling it and reinstalling it, and I get the same thing, flashing, no exceptions!

At the same time, I've noticed that after reinstalling wsa, there is no amazon app store in the start menu, only WSA itself is in the start menu!

✔️ Expected Behavior

Since I started it by clicking on the Open File button in WSA's settings, it should give me a window with the WSA File Manager showing up!

❌ Actual Behavior

As said above, the window disappears, it flashes back, nothing happens, and again there is no obvious popup window indicating an error report

Here are the logs and diagnostic reports generated by the software

etw.zip

Other Software

No response

Please specify the version of Windows Subsystem for Android

2306.40000.4.0

jaholme commented 1 year ago

Please file a Feedback hub report (Windows key + F) under category Apps > Windows Subsystem for Android. On step 4 "Add more details" please add a recording recreating the problem of WSA not starting.

KJZH001 commented 1 year ago

Here's my previous feedback submission in the feedback center https://aka.ms/AAm95zl

I've re-uploaded a copy of the log file over there, but it's worth mentioning that the type of my previous submission was Apps>All Other Apps, as I couldn't find any similar items in the categories for Windows Subsystem for Android or amazon app store!

Also I really hope to get a solution as soon as possible, I've had feedback on this issue from Microsoft Learn Q&A, Answer Community, Feedback Center, and I couldn't find anything like this on Google, and finally the community expert in Answer Community told me to come over to Github to give feedback, and I really don't want to get a similarly tricked result again!

Thanks!

KJZH001 commented 1 year ago

As well, the log files have been sent by me before on github

Here again https://github.com/microsoft/WSA/files/12393637/etw.zip

Because I can't see the details once submitted in the feedback center, and I don't know if the submission was successful or not.

MxMaster3 commented 1 year ago

I had WSA produce this same behaviour and it was due to a graphics card/driver incompatibility. Switching to the Microsoft Basic Display Driver in the WSA settings resolved the problem.

KJZH001 commented 1 year ago

I had WSA produce this same behaviour and it was due to a graphics card/driver incompatibility. Switching to the Microsoft Basic Display Driver in the WSA settings resolved the problem.

Thanks for the reply, I just tried what you said but it still flashed (I actually tried switching to Nvidia 3050 Laptop or Intel irlsXe to run it before and got similar results)

jaholme commented 1 year ago

The feedback hub report had more logs in it, unfortunately the failure lies within a component below WSA.

Can you try enabling Local network access, and see if that resolves the issue for you? image

KJZH001 commented 1 year ago

The feedback hub report had more logs in it, unfortunately the failure lies within a component below WSA.

Can you try enabling Local network access, and see if that resolves the issue for you? image

Thank you for your reply, it did resolve after I turned on local network access and after the first successful launch, the Amazon store appeared in the list of apps that originally showed 0 and ADB worked all right image

KJZH001 commented 1 year ago

But I still have some doubts, from the log I submitted earlier, logcat is empty, which means that the part of the subsystem that belongs to Android has not been started at all Since opening the local network access can solve the problem, it also means that the cause of the problem is in the network part of the network, it is reasonable to say that even if there is a problem in the network, it should not make Android Linux kernel can't even start. The Android Linux kernel should not be able to start even if there is a problem with the network, right?

Of course, I'm not very good at the underlying development of Android, so I'm just curious as to why, and it would be great if you could give me a general explanation as to how the problem occurs.

Later on, I'll try to turn off local network access and try to reboot to see if WSA still reproduces the problem on my device.

Finally, thank you for your help!

KJZH001 commented 1 year ago

Ok, I'm going to try to reproduce it now and it worked, here's the log now, it does crash once local network access is turned off

Here's the log now

diagnostics.zip

jaholme commented 1 year ago

But I still have some doubts, from the log I submitted earlier, logcat is empty, which means that the part of the subsystem that belongs to Android has not been started at all Since opening the local network access can solve the problem, it also means that the cause of the problem is in the network part of the network, it is reasonable to say that even if there is a problem in the network, it should not make Android Linux kernel can't even start. The Android Linux kernel should not be able to start even if there is a problem with the network, right?

Of course, I'm not very good at the underlying development of Android, so I'm just curious as to why, and it would be great if you could give me a general explanation as to how the problem occurs.

Later on, I'll try to turn off local network access and try to reboot to see if WSA still reproduces the problem on my device.

Finally, thank you for your help!

There are components that are necessary for Hyper-V to start a VM that are related to networking. On your device you are hitting some issue in those components preventing the VM from starting. By switching networking modes you're no longer relying on those components that are having an error and are able to start the VM.

KJZH001 commented 1 year ago

There are components that are necessary for Hyper-V to start a VM that are related to networking. On your device you are hitting some issue in those components preventing the VM from starting. By switching networking modes you're no longer relying on those components that are having an error and are able to start the VM.

Thanks for the reply.

I noticed that you mentioned that I was having problems with the networking component of Hyper-V on my device, I thought that this might be solved by reinstalling Hyper-V, since windows doesn't provide a place to directly uninstall and reinstall Hyper-V, it can only be installed or uninstalled by enabling or disabling the Windows feature, I thought that maybe I I could reboot multiple times to disable and re-enable it for reinstallation

Then I'm going to run a sfc /scannow scan of the system to make sure no components are damaged.

Do you think this would work? Or do I need to keep the current environment for now to try to reproduce the problem in the future?

xushulang commented 1 year ago

I had the same problem. 错误模块名称: wsaclient.exe 异常代码: 0xc0000409