Debugging no longer possible after updating WSL to version 2.0.9.0

[JustAnotherLars]

Windows Version

Microsoft Windows [Version 10.0.22631.3155]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04

Other Software

Docker Desktop Windows (v4.28.0)
WSL-Version: 2.0.9.0
Kernelversion: 5.15.133.1-1
WSLg-Version: 1.0.59
MSRDC-Version: 1.2.4677
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows-Version: 10.0.22631.3155

Visual Studio 2022 Professional (17.9.1)

Repro Steps

• Update WSL-Version from 1.2.5 to 2.0.9 with wsl.exe --install
• Create a new vs project (with docker compatibility)
• select windows docker container
• Add this to the docker arguments: --network="WSL"
• start debugging
• notice that the network is not found
• Check which Hyper V switches exist and find the following: WSL (Hyper-V firewall)
• customize docker arguments with the existing network
• start debugging again

Expected Behavior

VS compiles the project and will start the debugging process.
Among other things, Docker uses the Hyper v virtual switch with the name "WSL".

Actual Behavior

The project is not compiled.
VS reports that the remote debugging service is not available and cancels the process.
The following switch appears in the Hyper v virtual switches list:
WSL (Hyper-V firewall)

VS gives the following error:

---

Microsoft Visual Studio

Debugging cannot be started.

Visual Studio Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because communication with the remote computer is prevented by a firewall. Information on configuring remote debugging can be found in the help.

OK

I have already switched off all firewalls. The behavior persists.
Even reinstalling my computer did not solve the problem.

Diagnostic Logs

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• [WSL1] Cannot debug anything after upgrading to 22.04 (#8356), similarity score: 0.80

Closed similar issues:

• wsl --debug-shell not working (#9518), similarity score: 0.77
• WSL hang up after upgrade to version 2.0.0 (#10534), similarity score: 0.77
• Cannot run WSL after update to 2.0.0 (#10530), similarity score: 0.76
• WSL version 2 Stopped Working (#6080), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Denarius33]

I have exactly the same issue and can't find a solution for it.

[OneBlue]

/logs

[microsoft-github-policy-service]

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

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.

Thank you!

[microsoft-github-policy-service]

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-file it as a new issue.

Thank you!

[benhillis]

I think I have an idea what's going on here... When we introduced support for Hyper-V Firewall, the name of the network we create is now "WSL (Hyper-V firewall)".

[benhillis]

Try passing that instead.

[microsoft-github-policy-service]

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-file it as a new issue.

Thank you!