wsl settings app: The feature you are trying to use is on a network resource that is unavailable.

[YUUUCC]

Windows Version

10.0.26100.2605

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Debian 12

Other Software

No response

Repro Steps

• update windows11 to 24h2 from 23h2
• click wsl settings icon
• The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'wsl.2.3.26.0.x64.msi' in the box below.

Expected Behavior

• can open wsl settings
• can directly see WSL from windows file manager

Actual Behavior

• show The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package 'wsl.2.3.26.0.x64.msi' in the box below. after click icon
• Unable to see wsl in the windows file manager
• can start debian under WSL, and run wsl -- update in cmd, which can show that it is the latest version

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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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 [email protected] 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'.

View similar issues

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!

Open similar issues:

• open wsl app issue (#11969), similarity score: 0.75
• Can't access Linux filesystem through the Linux menu in File Explorer (#7541), similarity score: 0.71

Closed similar issues:

• can't access my distribution on win11 (#8232), similarity score: 0.71
• Windows 11 22H2 WSL error - Windows cannot access \wsl.localhost (#8983), similarity score: 0.71
• [Bug] Can not install WSL on the latest Windows Version (#11200), similarity score: 0.70

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

[YUUUCC]

WslLogs-2024-12-17_16-52-47.zip

and when I click the pinned folder of wsl in win file manager, the explore.exe show: can not find element (Translated from Chinese)

[github-actions]

Failed to parse logs. Unexpected file: .wslconfig
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Found no WSL traces in the logs

[YUUUCC]

I'm sure I reproduced the problem.

[YUUUCC]

I have tried all solutions in relevant issues, but they have not been able to solve this problem. It seems that although WSL is here, VSCode, WSL2-Distro-Manager and other software can find it, but Windows11 cann't. In the windows-setting-installed software, I can't find the Windows Subsystem for Linux.

[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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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 [email protected] 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'.

View similar issues

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!

Open similar issues:

• wsl settings show: The feature you are trying to use is on a network resource that is unavailable. (#12391), similarity score: 0.99
• open wsl app issue (#11969), similarity score: 0.77
• Can't access Linux filesystem through the Linux menu in File Explorer (#7541), similarity score: 0.72

Closed similar issues:

• can't access my distribution on win11 (#8232), similarity score: 0.72
• Windows 11 22H2 WSL error - Windows cannot access \wsl.localhost (#8983), similarity score: 0.71

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

[YUUUCC]

I have uploaded logs before.

[shaunho57]

I have the same issue
Unable to access wsl folder that Pin to Quick Access, while desktop shortcut is still accessible

Attached Eng version of the screenshot error