Winsock module breaks WSL2

[Librazy]

For an workaround provided by Proxifier, see #4177 (comment)

Please fill out the below information:

• Your Windows build number: 10.0.18917.1000

• What you're doing and what's happening:
  After updating from 1903 to 18917, I upgraded to WSL2 and it works fine. Later, I enabled https://www.proxifier.com/'s winsock module in its "System Setting 64-bit" app, and WSL2 starting to fail with The attempted operation is not supported for the type of object referenced..

⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl
The attempted operation is not supported for the type of object referenced.
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v
NAME            STATE           VERSION
* Ubuntu-18.04    Running         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl --shutdown 
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v 
NAME            STATE           VERSION
* Ubuntu-18.04    Stopped         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl
The attempted operation is not supported for the type of object referenced.
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v
NAME            STATE           VERSION
* Ubuntu-18.04    Running         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v
NAME            STATE           VERSION
* Ubuntu-18.04    Stopped         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl
The attempted operation is not supported for the type of object referenced.
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v
NAME            STATE           VERSION
* Ubuntu-18.04    Running         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl
The attempted operation is not supported for the type of object referenced.

After uninstalling the winsock module, WSL2 launches again. And installing the winsock module won't cause running WSL2 console to fail.

• What's wrong / what should be happening instead:

WSL2 should work even if there are other winsock modules installed.

• Strace of the failing command, if applicable: N/A

• For WSL launch issues, please collect detailed logs.

lxcore.zip

[benhillis]

Thanks for providing a trace, I will take a look.

[benhillis]

I took a look at the trace and I'm not seeing any relevant events in the service etl. If possible could you do the following?

wsl.exe --shutdown
start trace
launch distribution
stop trace

[Librazy]

Steps I take (In a Chinese environment)

⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl.exe --shutdown
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ cd 'C:\Users\Liqueur Librazy\OneDrive\桌面\'
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe create trace lxcore_kernel -p "{0CD1C309-0878-4515-83DB-749843B3F5C9}" -mode 0x00000008 -ft 10:00 -o .\lxcore_kernel.etl -ets                                                                       命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe create trace lxcore_user -p "{D90B9468-67F0-5B3B-42CC-82AC81FFD960}" -ft 1:00 -rt -o .\lxcore_user.etl -ets                                                                                         命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe create trace lxcore_service -p "{B99CDB5A-039C-5046-E672-1A0DE0A40211}" -ft 1:00 -rt -o .\lxcore_service.etl -ets                                                                                   命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ wsl                                                                                    参考的对象类型不支持尝试的操作。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe stop lxcore_kernel -ets
命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe stop lxcore_user -ets
命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe stop lxcore_service -ets
命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯

lxcore.zip

[xiaoqidun]

same question,proxifier winsock installation,wsl2 can not work.

[yeahnoob]

Same issue of WSL 2 on my Win10 laptop.

[sticnarf]

Sorry for a useless comment.
Developers in China highly rely on proxies due to poor network condition. I do hope this issue will be resolved soon.

[SwimmingTiger]

The same issue. After running a game speedup VPN (https://uu.163.com), WSL2 cannot running.
Reset winsock can fix it.

PS C:\WINDOWS\system32> wsl.exe --shutdown
PS C:\WINDOWS\system32> wsl.exe
The attempted operation is not supported for the type of object referenced.
PS C:\WINDOWS\system32> netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

PS C:\WINDOWS\system32> wsl.exe
root@TIGERHOMEPC /mnt/c/Windows/System32
  # exit

Build 18922.1000.

[infdahai]

The same issue. After running a game speedup VPN (https://uu.163.com), WSL2 cannot running.
Reset winsock can fix it.

PS C:\WINDOWS\system32> wsl.exe --shutdown
PS C:\WINDOWS\system32> wsl.exe
The attempted operation is not supported for the type of object referenced.
PS C:\WINDOWS\system32> netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

PS C:\WINDOWS\system32> wsl.exe
root@TIGERHOMEPC /mnt/c/Windows/System32
  # exit

Build 18922.1000.

I encounter this problem and use this method to solve. But my proxifier can't be used.

[nimocat]

So the problem is, after using any kinds of vpn (such as shadowsocks or whatever), wsl2 will crash when users try to start it. So I think it needs to be compatible with vpns in the future.

[Librazy]

Still reproducible on recent insider versions

[xiaoqidun]

windows10 18941.1001，this problem is still not fixed。