Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL - server execution failed after windows update KB5012592 (OS Build 22000.613) #8384

Closed
2 tasks done
sohgaura opened this issue May 7, 2022 · 3 comments
Closed
2 tasks done

Comments

@sohgaura
Copy link

sohgaura commented May 7, 2022

Version

Microsoft Windows 11 21H2 build 22000.613

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

wsl command does not execute

Distro Version

Ubuntu 19 default

Other Software

Docker Desktop 4.7.0
MiniKube
STS 4.14.1

Repro Steps

wsl --list --running
wsl --status

Expected Behavior

WSL commands should work.
WSL --install should install given distribution.

Actual Behavior

PS C:\Windows\system32> wsl --install ubuntu
Server execution failed

WSL stopped working after windows security update KB5012592 (OS Build 22000.613).
Any WSL command output after 2-3 minutes - "server execution failed"
Uninstalled wsl from control panel and restarted the system, still WSL command does not work at all.

Diagnostic Logs

No response

@benhillis
Copy link
Member

Could you submit a feedback hub bug so I can check for crashdumps from your system?

/logs

@ghost
Copy link

ghost commented May 10, 2022

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

@ghost ghost closed this as completed May 17, 2022
@ghost
Copy link

ghost commented May 17, 2022

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants