Proxifier doesn't work with Docker Desktop on Win11

[TacBur]

I have a problem running docker for windows after installing PROXIFIER software.
I used to have exactly the same issue on Windows 10 months ago but then I read this:
#7420
and it solved the issue.
Few weeks ago I moved to Win11 and even tho I tried to reinstall docker/wsl/proxifier multiple times...it is always stopping working each time I install proxifier (even if proxifier is turned off the same issue appears)

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: A24FCB2A-50F2-4C83-BAFA-99872853CFA5/20230527003457

Actual behavior

Expected behavior

Information

• Windows Version: Windows 11, 22H2
• Docker Desktop Version: Docker Desktop.exe shows the version 4.19.0.0 (or 4.19.0.16363)
• WSL2 or Hyper-V backend? WSL2 installed
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: no. it's my home PC

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

`[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[FAIL] DD0002: does the bootloader have virtualization enabled? failed to ping com.docker.service with error: Get "http://ipc/ping": open \.\pipe\dockerBackendV2: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:51.275810700Z][com.docker.diagnose.exe][I] ipc.NewClient: 050ddae2-com.docker.diagnose -> \.\pipe\dockerBackendV2 com.docker.service
[2023-05-27T00:40:51.275810700Z][com.docker.diagnose.exe][I] (12f5723f) 050ddae2-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-27T00:40:51.276329300Z][com.docker.diagnose.exe][W] (12f5723f) 050ddae2-com.docker.diagnose C<-S NoResponse GET /ping (518.6µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: Nie można odnaleźć określonego pliku.

[SKIP] DD0018: does the host support virtualization?
[FAIL] DD0001: is the application running? Docker is not running
[FAIL] DD0022: is the Virtual Machine Platform Windows Feature enabled? failed to ping com.docker.service with error: Get "http://ipc/ping": open \.\pipe\dockerBackendV2: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:51.287226500Z][com.docker.diagnose.exe][I] ipc.NewClient: 8629207b-com.docker.diagnose -> \.\pipe\dockerBackendV2 com.docker.service
[2023-05-27T00:40:51.287743800Z][com.docker.diagnose.exe][I] (e760dd0c) 8629207b-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-27T00:40:51.287743800Z][com.docker.diagnose.exe][W] (e760dd0c) 8629207b-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: Nie można odnaleźć określonego pliku.

[FAIL] DD0021: is the WSL 2 Windows Feature enabled? failed to ping com.docker.service with error: Get "http://ipc/ping": open \.\pipe\dockerBackendV2: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:51.288774000Z][com.docker.diagnose.exe][I] ipc.NewClient: f3deebb5-com.docker.diagnose -> \.\pipe\dockerBackendV2 com.docker.service
[2023-05-27T00:40:51.289289400Z][com.docker.diagnose.exe][I] (5c61ff45) f3deebb5-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-27T00:40:51.289289400Z][com.docker.diagnose.exe][W] (5c61ff45) f3deebb5-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: Nie można odnaleźć określonego pliku.

[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? exit status 1
[FAIL] DD0035: is the VM time synchronized? exit status 0xffffffff
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:53.990904300Z][com.docker.diagnose.exe][I] ipc.NewClient: b6725c05-diagnose -> \.\pipe\dockerDiagnosticd diagnosticsd
[2023-05-27T00:40:53.990904300Z][com.docker.diagnose.exe][I] (09caca23) b6725c05-diagnose C->S diagnosticsd GET /ping
[2023-05-27T00:40:53.991432100Z][com.docker.diagnose.exe][W] (09caca23) b6725c05-diagnose C<-S NoResponse GET /ping (527.8µs): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: Nie można odnaleźć określonego pliku.

[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:53.992476800Z][com.docker.diagnose.exe][I] ipc.NewClient: 32aa71f0-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI
[2023-05-27T00:40:53.992476800Z][com.docker.diagnose.exe][I] (57cc3b8b) 32aa71f0-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-05-27T00:40:53.993000400Z][com.docker.diagnose.exe][W] (57cc3b8b) 32aa71f0-com.docker.diagnose C<-S NoResponse GET /docker (523.6µs): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:53.993000400Z][com.docker.diagnose.exe][I] (57cc3b8b-1) 32aa71f0-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-27T00:40:53.993523800Z][com.docker.diagnose.exe][W] (57cc3b8b-1) 32aa71f0-com.docker.diagnose C<-S NoResponse GET /ping (523.4µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:54.995277800Z][com.docker.diagnose.exe][I] (57cc3b8b-2) 32aa71f0-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-27T00:40:54.995277800Z][com.docker.diagnose.exe][W] (57cc3b8b-2) 32aa71f0-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:55.999781200Z][com.docker.diagnose.exe][I] (57cc3b8b-3) 32aa71f0-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-27T00:40:56.000314200Z][com.docker.diagnose.exe][W] (57cc3b8b-3) 32aa71f0-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:57.000504900Z][com.docker.diagnose.exe][I] (57cc3b8b-4) 32aa71f0-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-27T00:40:57.001010900Z][com.docker.diagnose.exe][W] (57cc3b8b-4) 32aa71f0-com.docker.diagnose C<-S NoResponse GET /ping (506µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:58.007177000Z][com.docker.diagnose.exe][I] (57cc3b8b-5) 32aa71f0-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-27T00:40:58.007177000Z][com.docker.diagnose.exe][W] (57cc3b8b-5) 32aa71f0-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:40:59.015085100Z][com.docker.diagnose.exe][I] (57cc3b8b-6) 32aa71f0-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-27T00:40:59.015590300Z][com.docker.diagnose.exe][W] (57cc3b8b-6) 32aa71f0-com.docker.diagnose C<-S NoResponse GET /ping (586.6µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:41:00.021048300Z][com.docker.diagnose.exe][I] (57cc3b8b-7) 32aa71f0-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-27T00:41:00.021048300Z][com.docker.diagnose.exe][W] (57cc3b8b-7) 32aa71f0-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:41:01.028275200Z][com.docker.diagnose.exe][I] (57cc3b8b-8) 32aa71f0-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-27T00:41:01.028275200Z][com.docker.diagnose.exe][W] (57cc3b8b-8) 32aa71f0-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: Nie można odnaleźć określonego pliku.

[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json": open //./pipe/docker_engine_linux: Nie można odnaleźć określonego pliku.
[PASS] DD0013: is the $PATH ok?
error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: Nie można odnaleźć określonego pliku.
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0005: is the user in the docker-users group?
[FAIL] DD0038: is the connection to Docker working? HTTP GET https://login.docker.com: Get "https://login.docker.com": proxyconnect tcp: open \.\pipe\dockerHTTPProxy: Nie można odnaleźć określonego pliku.
[FAIL] DD0014: are the backend processes running? 3 errors occurred:
* com.docker.vpnkit.exe is not running
* com.docker.proxy.exe is not running
* com.docker.backend.exe is not running

[FAIL] DD0007: is the backend responding? failed to ping com.docker.backend with error: Get "http://ipc/ping": open \.\pipe\dockerBackendApiServer: Nie można odnaleźć określonego pliku.
[2023-05-27T00:41:01.239239400Z][com.docker.diagnose.exe][I] ipc.NewClient: aaf7f3af-diagnose -> \.\pipe\dockerBackendApiServer BackendAPI`

Steps to reproduce the behavior

1. Install docker, wsl2 etc
2. Instal proxifier
3. It works as expected until first Windows restart. After that it's not working anymore

[TacBur]

after many hours of trying to fix the issue I finally found this.

microsoft/WSL#4177 (comment)

How I managed to solve the problem:

> cd "C:\Program Files\WindowsApps\"

Search for some folder that looks like "MicrosoftCorporationII.WindowsSubsystemForLinux ... x64 ...". For me, it was "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.0.0_x64__8wekyb3d8bbwe"

Go in and list its files. It should contain "wsl.exe" and "wslservice.exe".

Download https://web.archive.org/web/20220728095911/http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

Open a windows terminal with admin priviledge.

Kill WSL with
> taskkill -IM "wslservice.exe" /F

Run NoLsp.exe on both "wsl.exe" and "wslservice.exe". For me, it was like
> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.0.0_x64__8wekyb3d8bbwe\wsl.exe"

> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.0.0_x64__8wekyb3d8bbwe\wslservice.exe"

fixed!

[mizzcode]

after many hours of trying to fix the issue I finally found this.

microsoft/WSL#4177 (comment)

How I managed to solve the problem:

> cd "C:\Program Files\WindowsApps\"

Search for some folder that looks like "MicrosoftCorporationII.WindowsSubsystemForLinux ... x64 ...". For me, it was "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.0.0_x64__8wekyb3d8bbwe"

Go in and list its files. It should contain "wsl.exe" and "wslservice.exe".

Download https://web.archive.org/web/20220728095911/http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

Open a windows terminal with admin priviledge.

Kill WSL with
> taskkill -IM "wslservice.exe" /F

Run NoLsp.exe on both "wsl.exe" and "wslservice.exe". For me, it was like
> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.0.0_x64__8wekyb3d8bbwe\wsl.exe"

> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.0.0_x64__8wekyb3d8bbwe\wslservice.exe"

fixed!

but why i not found folder MicrosoftCorportationII.WindowsSubsystemForLinux

[viccP]

after many hours of trying to fix the issue I finally found this.

microsoft/WSL#4177 (comment)

How I managed to solve the problem:

> cd "C:\Program Files\WindowsApps\"

Search for some folder that looks like "MicrosoftCorporationII.WindowsSubsystemForLinux ... x64 ...". For me, it was "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.0.0_x64__8wekyb3d8bbwe"

Go in and list its files. It should contain "wsl.exe" and "wslservice.exe".

Download https://web.archive.org/web/20220728095911/http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

Open a windows terminal with admin priviledge.

Kill WSL with
> taskkill -IM "wslservice.exe" /F

Run NoLsp.exe on both "wsl.exe" and "wslservice.exe". For me, it was like
> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.0.0_x64__8wekyb3d8bbwe\wsl.exe"

> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.0.0.0_x64__8wekyb3d8bbwe\wslservice.exe"

fixed!

This works well, but for some users, the wsl.exe may not be located there. To confirm the locations of wsl.exe and wslservice.exe, it is recommended to open the Windows Task Manager, find the wslservice.exe process, and check the directory where these two executable files are located.