-
Notifications
You must be signed in to change notification settings - Fork 809
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
Error code: Wsl/Service/0x8007273d #9331
Comments
I have this problem too. Did you fix it? |
The same. I used to run WSL using the Windows optional component version before, and after updating to the store version, the problem occurs. I tried to remove the store version, and it works again. Seems the update didn't remove the old version, otherwise I cannot restore my WSL so easily. |
@qzmlgfj where di you get the non-store version out of curiosity? This issue happened to me with the latest update of Windows 10, it worked fine before but this is on $corporate machine that forced the upgrade. |
Same here, I'm on Windows 10 and this error showed up after installing updates (KB5021233 and KB5021089). Tried the reg fix here but no luck. |
I was able to "fix" this issue by doing the following:
Which seems like what @qzmlgfj did as well. |
Thank you so much, it worked for me |
I think it is sufficient just to uninstall "Windows Subsystem for Linux" (either from the Apps Settings, or perhaps instead from the Programs and Features control panel). That takes you back to the old version of WSL (Windows optional feature, not Windows Store), and everything works again. I was really looking forward to using the new WSL2 features (especially WSLg and systemd) in Windows 10, so I'd really like to be able to update. But whenever I do update, I always have the same error when I start a distribution:
I get the same error whether I use an old distribution, or a new one created as part of the update. I've tried Ubuntu, Debian, and CentOS7. I've tried uninstalling everything (unregister all distributions, uninstall WSL App, WSL Kernal update, WSL and Virtual Machine Platform from Windows Features) and then installing from scratch with
That runs fine, until it starts the newly-installed distribution, at which point I get the same error code when it tries to set the default username. Sorry for the long report, but I hope this makes it clear that we don't have a fix, just a way to back out the new version. For the record, here are the version numbers I get with the broken WSL after the update:
|
@ffainelli I started using WSL in 2020, and it seems the latest update of Windows 10 didn't affect my WSL. The notification occurs when login WSL tells me to run |
then restarting my PC works for me WSL version: 1.0.3.0 |
This is interesting. The problems I reported before were on an ASUS laptop. I tried on another machine (Dell), and this time it worked! 😄
Here are some differences between the two machines:
I don't know if it relevant, but the ASUS's CPU is not on Microsoft's list of Intel processors supported for Windows 11, while the Dell's CPU is. Of course both are running Windows 10, so that shouldn't make a difference. Both CPU have the same feature set, and both work with the previous version of WSL2, so they should work the same. Apart from the Windows version number reported above, the Does anyone else who sees this error, have anything that matches my ASUS machine better than my Dell machine? Maybe that'll give us a clue as to what's going on here. |
That fixed the problem for me too! 😁 I ran the winsock reset on my ASUS machine (the one experiencing the problem before I restored the old version of WSL), then ran Thanks, this is fantastic! |
It's really works. Thanks a lot! |
It works. Thanks for this! |
work for me too |
It also works for me; thank you! |
I found another solution (noLSP): https://wangyj.medium.com/the-solution-to-wsl-error-the-attempted-operation-is-not-supported-for-the-type-of-object-aa559854d1e3 you can fix Steps for early version (fresh system installation or install wsl from Windows Feature):
(Alternatively) If you dont want to use Nolsp.exe binary file, you can Manually add the following items to the registry using regedit.exe. Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\Windows\System32\wsl.exe"
"PermittedLspCategories"=dword:80000000 Steps for windows store users or you once run
|
This Worked for me without event restarting my PC! |
Just run this fixed this for me :D |
I can confirm that using:
works, however after a few hours of uptime, my WSL instances stop responding and just freeze. This did not happen before using the latest WSL update from the store. Anyone seeing this as well? |
|
Afterwards I tried running |
i have same problem with Proxycap |
I had the same issue, |
Thanks for help guys here! netsh winsock reset - helped me . wsl --set-version Ubuntu-18.04 1 ( for instance downgrade ubuntu version 1 wsl) |
Thanks @nurhasyim354. WSL: 1.2.5.0 |
yes, it can be fixed. Realted issue #4177 if it does not work, see my update #9331 (comment) |
Work for me. Thank you |
Thank you. This work for me too, I also have Proxifier installed on my Windows, so I think this is the proper solution/workaround. In addtion, I run |
dunno why this solution is so damn hard to find. It is single solution that worked for me. |
This worked for me but with the following paths for wsl and wslservice:
|
This solution does not work for me |
Version
Microsoft Windows [Version 10.0.19044.2364]
WSL Version
Kernel Version
No response
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Start Ubuntu 22.04 or 20.04 installed from the Microsoft Store and notice the following error being reported upon startup:
The attempted operation is not supported for the type of object referenced. Error code: Wsl/Service/0x8007273d Press any key to continue...
Expected Behavior
Ubuntu should start fine.
Actual Behavior
The attempted operation is not supported for the type of object referenced. Error code: Wsl/Service/0x8007273d Press any key to continue...
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: