WSL2 和 Proxifier 冲突的解决方案

最新推荐文章于 2024-10-11 16:44:52 发布

Bpazy

最新推荐文章于 2024-10-11 16:44:52 发布

阅读量4.3k

点赞数 2

分类专栏： common 文章标签： wsl2 proxifier

本文链接：https://blog.csdn.net/hanziyuan08/article/details/105930248

版权

common 专栏收录该内容

41 篇文章 1 订阅

订阅专栏

解决方案

下载 www.proxifier.com/tmp/Test20200228/NoLsp.exe;
使用管理员权限运行：NoLsp.exe c:\windows\system32\wsl.exe

方案来源

https://github.com/microsoft/WSL/issues/4177#issuecomment-597736482

Thanks for the info.

We have reproduced this issue. Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.

The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this. Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog This tells Windows not to load LSP DLLs into wsl.exe process.

We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe

Please just run as admin with the full path to wsl.exe as the parameter: NoLsp.exe c:\windows\system32\wsl.exe

This has fixed the problem in my case.

Please let me know how it works for you.