-
Notifications
You must be signed in to change notification settings - Fork 859
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
Comments
/logs This is interesting, you're saying WSLg still works but WSL does not? Can you do a repro of launching both, thanks! |
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:
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! |
Actually, this is /dupe #9866. Run |
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! |
Well,everything works fine.All Hyper-V components are functioning normally. |
Windows Version
Microsoft Windows [Version 10.0.22621.1413]
WSL Version
1.1.3.0
Are you using WSL 1 or WSL 2?
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.
The text was updated successfully, but these errors were encountered: