wsl2 beth won't allow for lan connections or changes to the wsl.conf.

[malcolm-dane]

Windows Version

windows 10

WSL Version

2

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

Ubuntu 22.04 lts

Other Software

No response

Repro Steps

After a system restore wsl2 won't turn off or respond to conf changes and and the Linux host file system is mounted all the time.

It also constantly creates hyperv adapters that don't respond to network adapter changes like pia. It also won't allow for direct network access like the VMware adapter will do via lan.

This happened after a system restore failed.

Expected Behavior

The veth worked fine before

Actual Behavior

Terminal output and rebooting don't change the behavior. Removing the distro and unregistering it doesn't change it either.

Diagnostic Logs

No response

[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'.

[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!