wsl blocked visual studio 2022 cmake project

[vsdownloader]

Windows Version

Microsoft Windows [Version 10.0.26100.1]

WSL Version

not installed

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

not installed

Distro Version

no distro

Other Software

No response

Repro Steps

wsl-hangup-vs2022.mp4

new windows system , install visual studio 2022 17.9.6

disable wsl on system

then run wsl.exe -l -v ， it will wait 60 seconds to exit

use vs2022 to create cmake project ,then vs2022 will block because it will launch 'wsl -l -v' to enum distributions installed on the system , but wsl will not exit in 60 seconds .

C:\Users\bob>wsl -l -v
The Windows Subsystem for Linux is not installed. You can install by running 'wsl.exe --install'.
For more information please visit https://aka.ms/wslinstall

Press any key to install Windows Subsystem for Linux.
Press CTRL-C or close this window to cancel.
This prompt will time out in 60 seconds.

Expected Behavior

when no distributions installed on system , run wsl -l -v exit as soon as possible, not block visual studio

Actual Behavior

C:\Users\vsdow>wsl -l -v
The Windows Subsystem for Linux is not installed. You can install by running 'wsl.exe --install'.
For more information please visit https://aka.ms/wslinstall

Press any key to install Windows Subsystem for Linux.
Press CTRL-C or close this window to cancel.
This prompt will time out in 60 seconds.

Diagnostic Logs

C:\Users\vsdow>wsl -l -v
The Windows Subsystem for Linux is not installed. You can install by running 'wsl.exe --install'.
For more information please visit https://aka.ms/wslinstall

Press any key to install Windows Subsystem for Linux.
Press CTRL-C or close this window to cancel.
This prompt will time out in 60 seconds.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How 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
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[vsdownloader]

/question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[OneBlue]

Thank you @vsdownloader: This is by design since WSL is not part of the Windows image anymore. Running wsl --install should solve the issue for you.

[vsdownloader]

but i do not need wsl ,because it will affect my vmware workstation

wsl needs hyperv which conflict with vmware workstation , and hyperv can't satisfy my usage

[benhillis]

Thanks for posting. I've contacted the Visual Studio team and they are looking at a fix for this behavior. This is due to the new WSL UX around prompting the user to install WSL that is present in new Windows builds.