Docker desktop version 4.17.1.101757 fails to start on Windows 11 64-bit

[CrafterNova]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: BE14838B-9E5A-43B3-85B9-8C0B2E15D5FF/20230404070345

Actual behavior

Expected behavior

Information

• Windows Version: 22H2 version10.0.22623 Build 22623

• Docker Desktop Version: 4.17.1.101757

• WSL2 or Hyper-V backend? WSL2

• Diagnostics zip file:
  20230404070345.zip

• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: running on a virtual machine

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

C:\Program Files\Docker\Docker\resources>com.docker.diagnose.exe check
[2023-04-04T06:44:46.547375800Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[FAIL] DD0001: is the application running? Docker is not running
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[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? [ 49.350989] EXT4-fs error (device sdf): ext4_journal_check_start:83: comm ext4lazyinit: Detected aborted journal
[PASS] DD0035: is the VM time synchronized?
[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: The system cannot find the file specified.
[2023-04-04T06:44:53.058625300Z][com.docker.diagnose.exe][I] ipc.NewClient: b3a63c9b-diagnose -> \.\pipe\dockerDiagnosticd diagnosticsd
[2023-04-04T06:44:53.059345700Z][com.docker.diagnose.exe][I] (62693790) b3a63c9b-diagnose C->S diagnosticsd GET /ping
[2023-04-04T06:44:53.059928000Z][com.docker.diagnose.exe][W] (62693790) b3a63c9b-diagnose C<-S NoResponse GET /ping (582.3µs): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.

[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-04T06:44:53.064671600Z][com.docker.diagnose.exe][I] ipc.NewClient: a94b5945-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI
[2023-04-04T06:44:53.065323900Z][com.docker.diagnose.exe][I] (12b3fec9) a94b5945-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-04-04T06:44:53.065952900Z][com.docker.diagnose.exe][W] (12b3fec9) a94b5945-com.docker.diagnose C<-S NoResponse GET /docker (629µs): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-04T06:44:53.065952900Z][com.docker.diagnose.exe][I] (12b3fec9-1) a94b5945-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-04T06:44:53.066545400Z][com.docker.diagnose.exe][W] (12b3fec9-1) a94b5945-com.docker.diagnose C<-S NoResponse GET /ping (592.5µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-04T06:44:54.072755500Z][com.docker.diagnose.exe][I] (12b3fec9-2) a94b5945-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-04T06:44:54.073271300Z][com.docker.diagnose.exe][W] (12b3fec9-2) a94b5945-com.docker.diagnose C<-S NoResponse GET /ping (515.8µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-04T06:44:55.077484900Z][com.docker.diagnose.exe][I] (12b3fec9-3) a94b5945-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-04T06:44:55.079493400Z][com.docker.diagnose.exe][W] (12b3fec9-3) a94b5945-com.docker.diagnose C<-S NoResponse GET /ping (2.3331ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-04T06:44:56.093069400Z][com.docker.diagnose.exe][I] (12b3fec9-4) a94b5945-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-04T06:44:56.094496000Z][com.docker.diagnose.exe][W] (12b3fec9-4) a94b5945-com.docker.diagnose C<-S NoResponse GET /ping (1.4266ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-04T06:44:57.108433100Z][com.docker.diagnose.exe][I] (12b3fec9-5) a94b5945-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-04T06:44:57.109628100Z][com.docker.diagnose.exe][W] (12b3fec9-5) a94b5945-com.docker.diagnose C<-S NoResponse GET /ping (1.195ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-04T06:44:58.125150200Z][com.docker.diagnose.exe][I] (12b3fec9-6) a94b5945-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-04T06:44:58.126316100Z][com.docker.diagnose.exe][W] (12b3fec9-6) a94b5945-com.docker.diagnose C<-S NoResponse GET /ping (1.1659ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-04T06:44:59.141151600Z][com.docker.diagnose.exe][I] (12b3fec9-7) a94b5945-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-04T06:44:59.141702900Z][com.docker.diagnose.exe][W] (12b3fec9-7) a94b5945-com.docker.diagnose C<-S NoResponse GET /ping (551.3µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-04T06:45:00.143320600Z][com.docker.diagnose.exe][I] (12b3fec9-8) a94b5945-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-04T06:45:00.143990700Z][com.docker.diagnose.exe][W] (12b3fec9-8) a94b5945-com.docker.diagnose C<-S NoResponse GET /ping (670.1µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.

[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0013: is the $PATH ok?
error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: The system cannot find the file specified.
* com.docker.vpnkit.exe is not running
* 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: The system cannot find the file specified.[2023-04-04T06:45:02.592002100Z][com.docker.diagnose.exe][I] ipc.NewClient: 3b62a2b6-diagnose -> \.\pipe\dockerBackendApiServer BackendAPI

Steps to reproduce the behavior

1. I opened Docker desktop 4.17.1.101757 with administrator privileges.

2. I was not able to interact with the application after that. Docker ran for ~30 seconds then showed the following error:
   An unexpected error occurred

   1 error occurred:
   *starting WSL integration service: synchronising agents: synchronising agent list: checking if desired distros are responsive:
   1 error occurred:
   running uname in "salad-enterprise-linux" distro: running WSL command "wsl.exe -d salad-enterprise-linux uname" failed with output "This account is currently not available.\n": exit status 1