Error: "The stub received bad data" #7570
Comments
|
/logs |
|
Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it. Thank you! |
ghost
added
the
|
wsl.etl |
|
@sirius-fan - thanks for providing the trace. I do see the RPC error, but it looks like it's originating somewhere in COM. @OneBlue - looks like we may have to get some more COM tracing to see what is going wrong with this RPC interface. @sirius-fan - do other commands work? For example |
|
This is interesting, I can see that the VM successfully started, then the distro successfully starts, but then we fail to create a process because of this RPC error. @sirius-fan: Couple questions:
|
no problem |
Additional information |
|
I tried to convert to wsl1 and then started smoothly. |
|
Also encountered this problem. Same windows version |
|
@sirius-fan or @asqw6677 - if you run wsl.exe directly (not ubunu.txt) does the shell launch? |
Nope win+R to run wsl.exe will open the window and then crash |
|
Thanks for the info @sirius-fan. It looks like the issue comes from COM so we need more info to diagnose this. Can you please take a trace with the attached profile, reproduce the issue, and share logs ? Instructions (in an elevated prompt): |
|
logs |
|
Thanks @sirius-fan, looking at the logs, I can see: That's interesting because I can't reproduce this so there must be something about your machine / configuration that triggers this. Can you share the content of |
|
The content of registry I did not find a file named .wslconfig in my user profile folder, I don’t remember that I ever created or configured this file. |
Mine is like this |
|
My win11 system was also re-made on October 23 |
|
Ver de qué app es
|
@sirius-fan: This is the content of |
|
sorry,I misread it. @OneBlue |
|
Thanks @sirius-fan. Going down the rabbit hole, this error could be caused by a missing entry in winsock's protocol catalog. Can you please share the content of |
This is the preservation of docker don't know if it helps |
|
|
@OneBlue Cause of problemI used Nolsp.exe to solve the issue #4177 ，and about Nolsp.exe see #4177 (comment) The solutionOpen an administrative command prompt or powershell，run For me, this has solved the problem and it still works after restarting the system，If it is only temporarily effective for other computers with this problem, recommended to try |
|
Hello, I can reproduce the issue in Windows 11 insider beta (22616.1) using Windows Subsystem for Linux Preview. |
|
Thanks for reporting this @xsm1997. Can you try following these instructions but instead of calling NoLsp.exe for For the latest version of WSL that should be |
|
@OneBlue I managed to get it working. I need to call NoLsp.exe with wslservice.exe in the WindowsStore wsl2 folder additionally along with the wsl.exe. Thanks! |
|
Awesome, thanks for the update @xsm1997. |
This only works for me temporarily. Every time WSL updates via the store I need to run the same NoLsp command again. Are there plans for a fix? |
|
How I managed to solve the problem: |
Yes that's how I fix it too. But then the next time WSL updates the paths change and I need to do it all over again. |
Thanks. This solved my problem. |
If anyone is here because Proxifier automatically configured Winsock for you, this is the solution that reverts the changes that Proxifier made. |
|
This problem still exists |
|
Well, while the problem still exists, the solution works. I recently add an "Easy Connect VPN"，and may be its port conflicts. |
Version
Microsoft Windows [Version 10.0.22000.258]
WSL Version
Kernel Version
5.10.60.1
Distro Version
Ubuntu
Other Software
No response
Repro Steps
When I install "Windows Subsystem for Linux Preview" from Microsoft Store，the following problems will appear when running wsl.
There is no problem before "Windows Subsystem for Linux Preview" is installed，and if I uninstall it, wsl is normal again.
Expected Behavior
"Windows Subsystem for Linux Preview" and wsl that have been installed can coexist.
Actual Behavior
wsl can't start.
Diagnostic Logs
The text was updated successfully, but these errors were encountered: