WSL: Quick Access pins broken after 24H2 update

Windows Version

Microsoft Windows [Version 10.0.26100.2033]

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

  1. Pin folder inside \\wsl$ to quick access in file explorer
  2. Click on pinned folder

Expected Behavior

  1. Pin folder inside \\wsl$ to quick access in file explorer
  2. Click on pinned folder
  3. Pinned folder opened in file explorer

Actual Behavior

  1. Pin folder inside \\wsl$ to quick access in file explorer
  2. Click on pinned folder
  3. “Element not found” error shown

Image

Diagnostic Logs

WslLogs-2024-10-16_11-25-44.zip

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 48
  • Comments: 42

Most upvoted comments

Windows update KB5048667 was installed on my PC overnight and it fixed the issue for me.

I must note that I also clicked WSL in the start menu by mistake (I almost never do that to start WSL) and it triggered the installation process of version 2.3.26.0 (the version I already had installed since weeks ago).

Anyway, all issues seem to be gone now.

Current configuration:

WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2605

Same issue here.

Slight workaround is to map your ‘\wsl.localhost’ to a network drive. Pinning folders from that mapped network drive works.

For those who have a non-working Pin in their explorer stuck, I was able to remove it with;

  • Workaround for removing/unpinning a folder that points to the ‘\wsl$’ is to navigate to that folder and right button click ‘Pin to quick access’

Same problem after latest Windows Update. WSL folder disappeared from Network folder in File Explorer, and can’t access pinned WSL folders from Quick Access in File Explorer. When I run wsl --update it says that the most recent version is already installed, and I also have all latest Windows Updates installed, so not sure what you guys mean by it’s fixed after updating.

Output of the test suggested by @zoliszabo:

PS Microsoft.PowerShell.Core\FileSystem::\\wsl.localhost\Ubuntu\home\naourass> Start .
Start : This command cannot be run due to the error: Element not found.
At line:1 char:1
+ Start .
+ ~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Start-Process], InvalidOperationException
    + FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand

Version:

WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.2454

Is it possible to re-open this issue please since it’s still occurring?

Same issue here. I tried to pin \wsl.localhost to the quick access. But when I click on it, this error appear: Image And now, I cannot even unpin it. It is stuck there. My windows updated to 24H2 W11. Edition Windows 11 Pro Version 24H2 Installed on ‎25/‎10/‎2024 OS build 26100.1742 Serial number 5XA29FFT800042H Experience Windows Feature Experience Pack 1000.26100.18.0 And My WSL is updated to the latest: Image

Another workaround method is add network location in ‘This PC’ and show ‘This PC’ tree in navgation pane.

Image

If use Network drive, it will failed path conversition when we open a WSL terminal from right click menu or you want start a WSL application from this location.

I can confirm that the trick mentioned by @zoliszabo about opening WSL app from start menu can indeed bing back the WSL folder in File Explorer by triggering some installation process and after rebooting the pc.

#12173 (comment)

^^^^

Windows update KB5048667 was installed on my PC overnight and it fixed the issue for me. I must note that I also clicked WSL in the start menu by mistake (I almost never do that to start WSL) and it triggered the installation process of version 2.3.26.0 (the version I already had installed since weeks ago). Anyway, all issues seem to be gone now. Current configuration:

WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2605

THIS IS THE WAY

Can confirm; had this issue for the last week or more - tried all kinds of solutions mentioned on other related issues to no avail, searched “wsl” in start menu, clicked it, and it fixed itself after some configuration dialog popped up.

Hover over file explorer icon on taskbar and right click, unpin wsl from quick access here by clicking the thumbtack icon on right side while hovering over it. This is only thing that worked for me. Incredibly annoying, hope this helps someone.

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:). The quick access pinning works with the local path !

Same on 24h2, linux icon missed.

I found a temporal solution, just updating to pre-release version:2.4.5.0

wsl.exe --update --pre-release

Then reboot the pc, linux icon will be displayed.

Same issue, after the update to win11 24h2 all the links are gone, if I add them again they don’t work with the error on explorer.exe “Element not found.” and actually I’m unable to remove that broken links. I tried both linking \wsl.localhost\path and \wsl$\path but doesn’t work.

I have all the components updated with the same version of the last comments but it doesn’t work

fixed in https://support.microsoft.com/pl-pl/topic/november-12-2024-kb5046617-os-build-26100-2314-1fa61a6d-a99a-47ca-a169-6974f08c3a0b. Now it works. I update WSL from Microsoft Store too, but i don’t know if it is necessary.

https://github.com/microsoft/WSL/issues/12173#issuecomment-2535134210

^^^^

Windows update KB5048667 was installed on my PC overnight and it fixed the issue for me.

I must note that I also clicked WSL in the start menu by mistake (I almost never do that to start WSL) and it triggered the installation process of version 2.3.26.0 (the version I already had installed since weeks ago).

Anyway, all issues seem to be gone now.

Current configuration:

WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2605


THIS IS THE WAY


I am seeing same issue with my home directory pinned to Quick Access. I can use \wsl$\ in address bar fine, but I cannot access or delete the Quick access. I tried reinstalling from the .msi but that did not fix anything. When will the fix be available in a non-pre-release build?

For me the update with --pre-release flag (and a reboot) fixed the issue

the issue look been fixed.

my system version:

WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2314