After Windows Update 24H2 cannot access WSL from File explorer

[Paoloncino]

Windows Version

24H2

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-microsoft-standard-WSL2 11.2.0

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Update to Windows 24H2.

Expected Behavior

Access WSL directories via quick access directories within File explorer. Access wsl.localhost network within File explorer.

Actual Behavior

After updating to Windows 24H2, I am unable to access WSL directories via quick access WSL directories within File explorer. additionally, within File explorer, "Network" does not show wsl.localhost, which can only be accessed via running "explorer.exe ." within WSL terminal.

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:

• wsl fails to start after 24H2 installed (#12355), similarity score: 0.75

Closed similar issues:

• Unable to access WSL filesystem from File Explorer after updated to Win11 Insider Preview 10.0.26058.1100 (#11171), similarity score: 0.79
• Quick Access pins broken after 24H2 update (#12173), similarity score: 0.79
• Windows 11 22H2 WSL error - Windows cannot access \wsl.localhost (#8983), similarity score: 0.76
• Can't access wsl in File Explorer + Possible Fix (#9010), similarity score: 0.76

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

[ctlila]

I've found a workaround.
Map your WSL network drive to a local drive in windows, following these instructions. WSL may not appear in the network browsed options, just type \\wsl.localhost\Ubuntu (or your corresponding distribution) in the 'Folder' field.
Then your WSL directory will be accessible from the local drive letter you've assigned to it (for instance W:).

[Cremesis]

I'm getting the same error: after the update to 24H2 my quick links for WSL folders in the windows 11 file explorer stopped working. I've found that I can still access the WSL file system by typing "\\wsl.localhost\<wsl_name>" in the address bar of the file explorer.

[kudlav]

Same here after upgrade to 24H2. Cannot access WSL directories from pinned quick access items throws an error: explorer.exe Element not found.

[edimax19830707]

How to Reset and Clear Quick Access Pinned Folders in Windows 11

Details

go to
%AppData%\Microsoft\Windows\Recent\AutomaticDestinations

delete
f01b4d95cf55d32a.automaticDestinations-ms

restart file explorer

https://www.tenforums.com/tutorials/175936-how-reset-clear-quick-access-pinned-folders-windows-10-a.html