Error code: Wsl/Service/0x8007273d #9331

ffainelli · 2022-12-14T23:42:44Z

Version

Microsoft Windows [Version 10.0.19044.2364]

WSL Version

WSL 2
WSL 1

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:

zysun · 2022-12-16T08:25:17Z

I have this problem too. Did you fix it？

qzmlgfj · 2022-12-16T08:31:23Z

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.

ffainelli · 2022-12-16T18:38:44Z

@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.

Tyromancer · 2022-12-17T01:21:51Z

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.
Also tried wsl --update and wsl --shutdown then reopen, also no luck

ffainelli · 2022-12-17T01:39:36Z

I was able to "fix" this issue by doing the following:

in Add or remove programs: uninstall first "Windows Subsystem for Linux Update" and then "Windows Subsystem for Linux"
try to start your distribution again and it will point you to: https://aka.ms/wsl2kernel
from there download the wsl_update_x64.msi file and run it, install the WSL kernel
start your distribution again

Which seems like what @qzmlgfj did as well.

Tyromancer · 2022-12-17T01:46:41Z

I was able to "fix" this issue by doing the following:

in Add or remove programs: uninstall first "Windows Subsystem for Linux Update" and then "Windows Subsystem for Linux"

try to start your distribution again and it will point you to: https://aka.ms/wsl2kernel

from there download the wsl_update_x64.msi file and run it, install the WSL kernel

start your distribution again

Which seems like what @qzmlgfj did as well.

Thank you so much, it worked for me

timadye · 2022-12-17T23:47:57Z

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:

C:\home>wsl
The attempted operation is not supported for the type of object referenced.
Error code: Wsl/Service/0x8007273d

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

wsl --install

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:

C:\home>wsl --version
WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2364

qzmlgfj · 2022-12-18T13:47:10Z

@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.

@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 wsl --update, and everything goes wrong after that.

nurhasyim354 · 2022-12-18T23:03:00Z

netsh winsock reset

then restarting my PC works for me

WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2364

timadye · 2022-12-18T23:14:50Z

This is interesting. The problems I reported before were on an ASUS laptop. I tried on another machine (Dell), and this time it worked! 😄

wsl --update ran smoothly and after that, all my distros ran fine, but now with the new features. So there must be something with my first machine that causes this error with the WSL update.

Here are some differences between the two machines:

ASUS laptop, Intel 7th Gen (i7-6700HQ), Windows 10 22H2 (10.0.19045.2364) - wsl fails after update
Dell laptop, Intel 8th Gen (i5-8350U), Windows 10 21H2 (10.0.19044.2364) - wsl works after update

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 wsl --version is the same on both machines after update.

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.

timadye · 2022-12-18T23:39:55Z

@nurhasyim354:

netsh winsock reset

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 wsl --update again, and wsl works for both my distros.

Thanks, this is fantastic!

HAAZZZEEEE · 2022-12-19T16:11:30Z

@nurhasyim354:
netsh winsock reset
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 wsl --update again, and wsl works for both my distros.

Thanks, this is fantastic!

It's really works. Thanks a lot!

arcayi · 2022-12-27T13:15:02Z

netsh winsock reset
then restarting my PC works for me

It works. Thanks for this!

yywing · 2023-01-01T16:08:57Z

netsh winsock reset
then restarting my PC works for me

WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364

work for me too

marcosrosse · 2023-01-09T15:52:03Z

netsh winsock reset
then restarting my PC works for me

WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364

It also works for me; thank you!

hycinth22 · 2023-01-22T16:16:04Z

netsh winsock reset
then restarting my PC works for me

WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364

netsh winsock reset makes WSL2 works , but also make Proxifier(use winsock) broken.
In fact, it is likely that the changes made to Winsock by Proxifier or similar software caused the 0x8007273d error in wsl2.

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
This solution disable proxifier in wsl2, so they can live together.

you can fix Error code: Wsl/Service/0x8007273d by the following steps:

Steps for early version (fresh system installation or install wsl from Windows Feature):

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe
configure nolsp via NoLSP.exe "C:\Windows\System32\wsl.exe", it will add a proper registry.
run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well.

(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 `wsl --update` (both install wsl from Windows Store):

You are using wsl2 from windows store, so please specify the file path of wsl2 store app("C:\Program Files\WindowsApps\WSL_DIRNAME\wsl.exe") instead of default C:\Windows\System32\wsl.exe.

Firstly, you can obtain the WSL_DIRNAME by the following instruction in cmd(admin):

cd "C:\Program Files\WindowsApps\"
dir MicrosoftCorporationII.WindowsSubsystemForLinux_*

you will see WSL_DIRNAME, it seems like MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe.
(different WSL_DIRNAME for different wsl2 versions.)

Next steps:

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe
run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\wsl.exe", it will add a proper registry.
run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\wslservice.exe", it will add a proper registry.
(Note: use your WSL_DIRNAME to modify the 1.2.5.0_x64__8wekyb3d8bbwe if you are using a different version.)
run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well. And be aware that path to WindowsApps change every time wsl update(so you will need to reconfig nolsp in the future)

(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\0A89E33B]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\\wsl.exe"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\3A1A96F3]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\\wslservice.exe"

(Note: modify the 1.2.5.0_x64__8wekyb3d8bbwe if you are using a different version.
And modify the 0A89E33B&3A1A96F3 (yet I dont know how to get valid one if not use NoLSP.exe. so I recommand you use NoLSP.exe)

muhammadelmogy · 2023-02-04T12:26:37Z

netsh winsock reset
then restarting my PC works for me

WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364

This Worked for me without event restarting my PC!

BodhiHu · 2023-02-23T07:39:21Z

netsh winsock reset

Just run this fixed this for me :D
Grateful! Thanks a lot!

ffainelli · 2023-03-12T16:41:48Z

I can confirm that using:

netsh winsock reset

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?

adeiming · 2023-03-30T00:50:14Z

wsl --update work for me

lesleyrs · 2023-03-30T00:50:15Z

netsh winsock reset only temporarily fixed the problem for me, second time I try to access wsl I get the error again.

Afterwards I tried running wsl --update and that seems to have fixed it (hopefully).

tonycoc · 2023-03-30T07:02:46Z

@hycinth22 >

i have same problem with Proxycap
did fix the problem with proxifire??

sistek · 2023-03-30T17:02:23Z

I had the same issue,
netsh winsock reset
and
wsl --update
worked for me.

jdstone · 2023-04-16T02:15:25Z

This worked for me:
If you did not enable Windows Subsystem for Linux (see screenshot number 1 below) before downloading WSL from the Microsoft Store, then follow these directions to fix your issue.

Uninstall Windows Subsystem for Linux that was installed from the Microsoft Store (see add/remove programs)
Restart computer
Enable the Windows Subsystem for Linux and Virtual Machine Platform feature in optional features
Restart computer
Install WSL from the Microsoft Store
All set! You can now install a distribution.

Screenshots:

bazilxp · 2023-05-07T18:54:38Z

Thanks for help guys here!
I run into problem Error code: Wsl/Service/0x8007273d
Tried (downloading, uninstalling ) does not help much

netsh winsock reset - helped me .
wsl -l - quite useful command
if nothing still works you can also downgrade machine to version 1

wsl --set-version Ubuntu-18.04 1 ( for instance downgrade ubuntu version 1 wsl)
wsl --set-version Ubuntu-18.04 2 ( upgrade ubuntu to version 2 wsl)
Before i did winsock reset, i downgrade to version it was working :)

ihaveonesun · 2023-07-03T22:36:45Z

Thanks @nurhasyim354.
netsh winsock reset Saved my skin!

WSL: 1.2.5.0
kernel: 5.15.90.1
WSLg: 1.0.51
MSRDC: 1.2.3770
Direct3D: 1.608.2-61064218
DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows: 10.0.19045.3086

hycinth22 · 2023-07-04T12:09:01Z

@hycinth22 >

i have same problem with Proxycap did fix the problem with proxifire??

yes, it can be fixed. Realted issue #4177

if it does not work, see my update #9331 (comment)

balokolos · 2023-08-04T09:38:12Z

I was able to "fix" this issue by doing the following:

in Add or remove programs: uninstall first "Windows Subsystem for Linux Update" and then "Windows Subsystem for Linux"

try to start your distribution again and it will point you to: https://aka.ms/wsl2kernel

from there download the wsl_update_x64.msi file and run it, install the WSL kernel

start your distribution again

Which seems like what @qzmlgfj did as well.

Work for me. Thank you
If it helps other, it also help me launch docker desktop

parcox · 2023-12-15T08:20:17Z

netsh winsock reset
then restarting my PC works for me
WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364
netsh winsock reset makes WSL2 works , but also make Proxifier(use winsock) broken. In fact, it is likely that the changes made to Winsock by Proxifier or similar software caused the 0x8007273d error in wsl2.

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 This solution disable proxifier in wsl2, so they can live together.

you can fix Error code: Wsl/Service/0x8007273d by the following steps:

Steps for early version (fresh system installation or install wsl from Windows Feature):

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

configure nolsp via NoLSP.exe "C:\Windows\System32\wsl.exe", it will add a proper registry.

run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well.

(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 wsl --update (both install wsl from Windows Store):

You are using wsl2 from windows store, so please specify the file path of wsl2 store app("C:\Program Files\WindowsApps\WSL_DIRNAME\wsl.exe") instead of default C:\Windows\System32\wsl.exe.

Firstly, you can obtain the WSL_DIRNAME by the following instruction in cmd(admin):
cd "C:\Program Files\WindowsApps\"
dir MicrosoftCorporationII.WindowsSubsystemForLinux_*
you will see WSL_DIRNAME, it seems like MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe. (different WSL_DIRNAME for different wsl2 versions.)

Next steps:

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\wsl.exe", it will add a proper registry.

run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\wslservice.exe", it will add a proper registry.
(Note: use your WSL_DIRNAME to modify the 1.2.5.0_x64__8wekyb3d8bbwe if you are using a different version.)

run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well. And be aware that path to WindowsApps change every time wsl update(so you will need to reconfig nolsp in the future)

(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\0A89E33B]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\\wsl.exe"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\3A1A96F3]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\\wslservice.exe"
(Note: modify the 1.2.5.0_x64__8wekyb3d8bbwe if you are using a different version. And modify the 0A89E33B&3A1A96F3 (yet I dont know how to get valid one if not use NoLSP.exe. so I recommand you use NoLSP.exe)

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 NoLSP.exe C:\Program Files\WSL\wsl.exe and NoLSP.exe C:\Program Files\WSL\wslservice.exe instead of NoLSP.exe "path of the WSL.exe from Microsoft Store".

FloeHetling · 2023-12-22T17:32:38Z

netsh winsock reset
then restarting my PC works for me
WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364
netsh winsock reset makes WSL2 works , but also make Proxifier(use winsock) broken. In fact, it is likely that the changes made to Winsock by Proxifier or similar software caused the 0x8007273d error in wsl2.
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 This solution disable proxifier in wsl2, so they can live together.
you can fix Error code: Wsl/Service/0x8007273d by the following steps:

Steps for early version (fresh system installation or install wsl from Windows Feature):

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

configure nolsp via NoLSP.exe "C:\Windows\System32\wsl.exe", it will add a proper registry.

run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well.

(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 wsl --update (both install wsl from Windows Store):

You are using wsl2 from windows store, so please specify the file path of wsl2 store app("C:\Program Files\WindowsApps\WSL_DIRNAME\wsl.exe") instead of default C:\Windows\System32\wsl.exe.
Firstly, you can obtain the WSL_DIRNAME by the following instruction in cmd(admin):
cd "C:\Program Files\WindowsApps\"
dir MicrosoftCorporationII.WindowsSubsystemForLinux_*
you will see WSL_DIRNAME, it seems like MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe. (different WSL_DIRNAME for different wsl2 versions.)
Next steps:

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\wsl.exe", it will add a proper registry.

run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\wslservice.exe", it will add a proper registry.
(Note: use your WSL_DIRNAME to modify the 1.2.5.0_x64__8wekyb3d8bbwe if you are using a different version.)

run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well. And be aware that path to WindowsApps change every time wsl update(so you will need to reconfig nolsp in the future)

(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\0A89E33B]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\\wsl.exe"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\3A1A96F3]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\\wslservice.exe"
(Note: modify the 1.2.5.0_x64__8wekyb3d8bbwe if you are using a different version. And modify the 0A89E33B&3A1A96F3 (yet I dont know how to get valid one if not use NoLSP.exe. so I recommand you use NoLSP.exe)
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 NoLSP.exe C:\Program Files\WSL\wsl.exe and NoLSP.exe C:\Program Files\WSL\wslservice.exe instead of NoLSP.exe "path of the WSL.exe from Microsoft Store".

dunno why this solution is so damn hard to find. It is single solution that worked for me.

xoner · 2024-01-24T09:06:13Z

netsh winsock reset
then restarting my PC works for me
WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2364
netsh winsock reset makes WSL2 works , but also make Proxifier(use winsock) broken. In fact, it is likely that the changes made to Winsock by Proxifier or similar software caused the 0x8007273d error in wsl2.

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 This solution disable proxifier in wsl2, so they can live together.

you can fix Error code: Wsl/Service/0x8007273d by the following steps:

Steps for early version (fresh system installation or install wsl from Windows Feature):

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

configure nolsp via NoLSP.exe "C:\Windows\System32\wsl.exe", it will add a proper registry.

run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well.

(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 wsl --update (both install wsl from Windows Store):

You are using wsl2 from windows store, so please specify the file path of wsl2 store app("C:\Program Files\WindowsApps\WSL_DIRNAME\wsl.exe") instead of default C:\Windows\System32\wsl.exe.

Firstly, you can obtain the WSL_DIRNAME by the following instruction in cmd(admin):
cd "C:\Program Files\WindowsApps\"
dir MicrosoftCorporationII.WindowsSubsystemForLinux_*
you will see WSL_DIRNAME, it seems like MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe. (different WSL_DIRNAME for different wsl2 versions.)

Next steps:

Download Nolsp.exe: http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\wsl.exe", it will add a proper registry.

run NoLSP.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\wslservice.exe", it will add a proper registry.
(Note: use your WSL_DIRNAME to modify the 1.2.5.0_x64__8wekyb3d8bbwe if you are using a different version.)

run wsl --shutdown && net stop WslService && net start WslService, close all wsl terminal and reopen wsl
Now, wsl2 can work well. And be aware that path to WindowsApps change every time wsl update(so you will need to reconfig nolsp in the future)

(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\0A89E33B]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\\wsl.exe"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\3A1A96F3]
"PermittedLspCategories"=dword:80000000
"AppFullPath"="C:\\Program Files\\WindowsApps\\MicrosoftCorporationII.WindowsSubsystemForLinux_1.2.5.0_x64__8wekyb3d8bbwe\\wslservice.exe"
(Note: modify the 1.2.5.0_x64__8wekyb3d8bbwe if you are using a different version. And modify the 0A89E33B&3A1A96F3 (yet I dont know how to get valid one if not use NoLSP.exe. so I recommand you use NoLSP.exe)

This worked for me but with the following paths for wsl and wslservice:

nolsp.exe "C:\Program Files\WSL\wsl.exe"
nolsp.exe "C:\Program Files\WSL\wslservice.exe"

ghost · 2024-02-04T13:01:16Z

I was able to "fix" this issue by doing the following:

in Add or remove programs: uninstall first "Windows Subsystem for Linux Update" and then "Windows Subsystem for Linux"

try to start your distribution again and it will point you to: https://aka.ms/wsl2kernel

from there download the wsl_update_x64.msi file and run it, install the WSL kernel

start your distribution again

Which seems like what @qzmlgfj did as well.

This solution does not work for me

YusufKenanTurak mentioned this issue Jan 24, 2023

Upgraded from 4.15.0 to 4.16.1 docker stuck in starting mode forever docker/for-win#13165

Closed

3 tasks

p1-0tr mentioned this issue Jan 25, 2023

Docker Desktop Will Not Start docker/for-win#13184

Closed

3 tasks

github-actions bot mentioned this issue Nov 17, 2023

The specified service does not exist as an installed service. Error code: Wsl/0x80070424 [process exited with code 4294967295 (0xffffffff)] #10779

Closed

2 tasks

timadye mentioned this issue Dec 22, 2023

All WSL commands hang (including wsl --shutdown) but WSL is constantly using 30-40% CPU #8529

Open

2 tasks

github-actions bot mentioned this issue Mar 17, 2024

Error code: Wsl/Service/AttachDisk/E_INVALIDARG #11317

Closed

2 tasks

Error code: Wsl/Service/0x8007273d #9331

Error code: Wsl/Service/0x8007273d #9331

Comments

ffainelli commented Dec 14, 2022

Version

WSL Version

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

zysun commented Dec 16, 2022

qzmlgfj commented Dec 16, 2022

ffainelli commented Dec 16, 2022

Tyromancer commented Dec 17, 2022

ffainelli commented Dec 17, 2022

Tyromancer commented Dec 17, 2022

timadye commented Dec 17, 2022

qzmlgfj commented Dec 18, 2022

nurhasyim354 commented Dec 18, 2022

timadye commented Dec 18, 2022

timadye commented Dec 18, 2022

HAAZZZEEEE commented Dec 19, 2022

arcayi commented Dec 27, 2022

yywing commented Jan 1, 2023

marcosrosse commented Jan 9, 2023

hycinth22 commented Jan 22, 2023 • edited Loading

Steps for early version (fresh system installation or install wsl from Windows Feature):

Steps for windows store users or you once run wsl --update (both install wsl from Windows Store):

muhammadelmogy commented Feb 4, 2023

BodhiHu commented Feb 23, 2023

ffainelli commented Mar 12, 2023

adeiming commented Mar 30, 2023

lesleyrs commented Mar 30, 2023

tonycoc commented Mar 30, 2023 • edited Loading

sistek commented Mar 30, 2023

jdstone commented Apr 16, 2023 • edited Loading

Screenshots:

bazilxp commented May 7, 2023

ihaveonesun commented Jul 3, 2023

hycinth22 commented Jul 4, 2023 • edited Loading

balokolos commented Aug 4, 2023 • edited Loading

parcox commented Dec 15, 2023 • edited Loading

Steps for early version (fresh system installation or install wsl from Windows Feature):

Steps for windows store users or you once run wsl --update (both install wsl from Windows Store):

FloeHetling commented Dec 22, 2023

Steps for early version (fresh system installation or install wsl from Windows Feature):

Steps for windows store users or you once run wsl --update (both install wsl from Windows Store):

xoner commented Jan 24, 2024

Steps for early version (fresh system installation or install wsl from Windows Feature):

Steps for windows store users or you once run wsl --update (both install wsl from Windows Store):

ghost commented Feb 4, 2024

hycinth22 commented Jan 22, 2023 •

edited

Loading

Steps for windows store users or you once run `wsl --update` (both install wsl from Windows Store):

tonycoc commented Mar 30, 2023 •

edited

Loading

jdstone commented Apr 16, 2023 •

edited

Loading

hycinth22 commented Jul 4, 2023 •

edited

Loading

balokolos commented Aug 4, 2023 •

edited

Loading

parcox commented Dec 15, 2023 •

edited

Loading

Steps for windows store users or you once run `wsl --update` (both install wsl from Windows Store):

Steps for windows store users or you once run `wsl --update` (both install wsl from Windows Store):

Steps for windows store users or you once run `wsl --update` (both install wsl from Windows Store):