Quick Access pins broken after 24H2 update #12173

conan · 2024-10-16T10:22:36Z

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

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

Expected Behavior

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

Actual Behavior

Pin folder inside \\wsl$ to quick access in file explorer
Click on pinned folder
"Element not found" error shown

Diagnostic Logs

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

The text was updated successfully, but these errors were encountered:

github-actions · 2024-10-16T10:23:20Z

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!

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.76
WSL2 file access not working (#7656), similarity score: 0.70

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

conan · 2024-10-16T10:24:20Z

See relevant comment: #11252 (comment)

github-actions · 2024-10-16T10:28:17Z

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

Issue was edited and new log file was found: https://github.com/user-attachments/files/17394115/WslLogs-2024-10-16_11-25-44.zip
.wslconfig found
Detected appx version: 2.3.24.0
Found no WSL traces in the logs

haraldger · 2024-10-22T13:45:07Z

I'm having the same issue as OP and in the other referenced thread. Running wsl --update and wsl --update --pre-release gives me back "The most recent version of Windows Subsystem for Linux is already installed." so no help there. I first noticed the issue yesterday (2024-10-21).

JoanGi · 2024-10-22T15:40:46Z

Same case here; just update to W11, and quick access has disappeared.

My version:
Versión de WSL: 2.3.24.0
Versión de kernel: 5.15.153.1-2
Versión de WSLg: 1.0.65
Versión de MSRDC: 1.2.5620
Versión de Direct3D: 1.611.1-81528511
Versión DXCore: 10.0.26100.1-240331-1435.ge-release
Versión de Windows: 10.0.26100.1742

GillesJ · 2024-10-23T08:46:36Z

Exact same issue here after updating.

conan · 2024-10-23T08:57:48Z

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

I did reproduce whilst the log collection was running. This seems like the kind of issue that would be logged in Windows logs (it being an issue with File Explorer) rather than WSL logs.

christian-at-sevenlab · 2024-10-23T09:36:39Z

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'

fiathux · 2024-10-25T11:56:39Z

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

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.

ashkanr65 · 2024-10-25T14:08:22Z

Same issue here.
I tried to pin \wsl.localhost to the quick access. But when I click on it, this error appear:

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:

conan · 2024-10-29T17:04:37Z

Some updates:

It hadn't occurred to me to try to unpin my WSL quick access options, I can confirm I am unable to
Can confirm the workaround of mapping \\wsl$\Ubuntu to a Network Drive worked for me

Ravenger2709 · 2024-10-29T20:25:28Z

Same problem for me with WSL quick access dissapeared.

fiathux · 2024-10-30T03:06:10Z

Same issue here. I tried to pin \wsl.localhost to the quick access. But when I click on it, this error appear: 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:

Same issue here.
You can remove file to reset quick access (will remove all your custiomize icon in quick access). C:\Users\sum\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations\f01b4d95cf55d32a.automaticDestinations-ms

If you really want add icon into quick access to open WSL path. try use network drive please. It's work to me.
However, you can not directly open WSL terminal in network drive location using right click in the Explorer. Only 'network locations' available it.

Hofundur · 2024-11-13T18:50:33Z

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.

haraldger · 2024-11-13T19:03:24Z

Automatically started working for me with the latest fix, thanks @Hofundur

fiathux · 2024-12-04T06:16:43Z

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

CameronGo · 2024-12-04T20:16:04Z

Same, updated wsl this morning and that resolved 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

txdFabio · 2024-12-04T23:32:28Z

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

zoliszabo · 2024-12-05T09:42:40Z

I have the same issue:

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

Installed 24H2 yesterday, the problems appeared right after.

Interestingly, I can access the files from File Explorer (quick links are gone from the sidebar, but directly accessing a folder from the address bar by \\wsl.localhost\... will open the folder), double-click on them works fine (i.e. opens files in assigned programs), but wslview gives the same Start : This command cannot be run due to the error: Element not found. error; also, double-clicking the same files from Total Commander raise the same "Element not found." error.

conan · 2024-12-05T10:06:28Z

Also seems to be working for me now, although I've been using the network drive workaround so I can't pinpoint exactly when.

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

zoliszabo · 2024-12-05T10:18:24Z

@conan Could you please test something for the rest of us?

Start PowerShell in a WSL folder or change directory to a WSL folder after starting PowerShell (e.g. cd \\wsl$\distro\some\existing\folder);
Type Start ., which should open the current folder in File Explorer.
Does it work? If yes, does it open the correct folder?

Thank you!

Falkenjack · 2024-12-06T12:15:45Z

I have the same WSL- and Windows versions as @conan but still have the issue with Quick Access pins to WSL directories not working. For comparison, I ran the test suggested by @zoliszabo with the following result:

PowerShell 7.4.6
PS Microsoft.PowerShell.Core\FileSystem::\wsl.localhost\Ubuntu-22.04\home\johsj47> Start .
Start-Process: This command cannot be run due to the error: An error occurred trying to start process '.' with working directory '\wsl.localhost\Ubuntu-22.04\home\johsj47'. Element not found.

And to affirm I am running the same version as @conan :

PS Microsoft.PowerShell.Core\FileSystem::\wsl.localhost\Ubuntu-22.04\home\johsj47> wsl --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

CameronGo · 2024-12-06T12:32:10Z

Maybe a dumb question, but did you reboot after updating wsl? I had to reboot after the update for mine to work.

I have the same WSL- and Windows versions as @conan but still have the issue with Quick Access pins to WSL directories not working. For comparison, I ran the test suggested by @zoliszabo with the following result:

PowerShell 7.4.6
PS Microsoft.PowerShell.Core\FileSystem::\wsl.localhost\Ubuntu-22.04\home\johsj47> Start .
Start-Process: This command cannot be run due to the error: An error occurred trying to start process '.' with working directory '\wsl.localhost\Ubuntu-22.04\home\johsj47'. Element not found.

And to affirm I am running the same version as @conan :

PS Microsoft.PowerShell.Core\FileSystem::\wsl.localhost\Ubuntu-22.04\home\johsj47> wsl --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

Falkenjack · 2024-12-08T11:48:22Z

@CameronGo I have rebooted multiple times, yes. Worth mentioning is perhaps that my computer is managed by my employer. While I have some local admin rights I have little to no control over which updates are pushed and when to install them, i.e. I am somewhat limited wrt what I can do to explore this issue as far as it entails installing and/or rolling back updates.

naourass · 2024-12-08T12:56:44Z

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?

CptnFizzbin · 2024-12-10T15:16:05Z

~~Can confirm that this is also still happening for me.~~

Nvm, needed to do a restart

WSL 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

zoliszabo · 2024-12-11T08:42:07Z

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

dif-engine · 2024-12-11T18:10:10Z

I've applied Windows update KB5048667 and wsl --version tells as same as zoliszabo's previous post.
But still my Quick Access pins for WSL region is broken. sad.

github-actions bot added the needs-author-feedback label Oct 16, 2024

conan mentioned this issue Oct 16, 2024

Linux not appearing in file explorer; cannot use wslview #11252

Closed

2 tasks

microsoft-github-policy-service bot removed the needs-author-feedback label Oct 16, 2024

github-actions bot added the needs-author-feedback label Oct 16, 2024

microsoft-github-policy-service bot removed the needs-author-feedback label Oct 23, 2024

conan closed this as completed Dec 5, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Quick Access pins broken after 24H2 update #12173

Quick Access pins broken after 24H2 update #12173

conan commented Oct 16, 2024 •

edited

Loading

github-actions bot commented Oct 16, 2024

conan commented Oct 16, 2024

github-actions bot commented Oct 16, 2024

haraldger commented Oct 22, 2024

JoanGi commented Oct 22, 2024

GillesJ commented Oct 23, 2024

conan commented Oct 23, 2024

christian-at-sevenlab commented Oct 23, 2024 •

edited

Loading

fiathux commented Oct 25, 2024 •

edited

Loading

ashkanr65 commented Oct 25, 2024 •

edited

Loading

conan commented Oct 29, 2024

Ravenger2709 commented Oct 29, 2024

fiathux commented Oct 30, 2024

Hofundur commented Nov 13, 2024 •

edited

Loading

haraldger commented Nov 13, 2024

fiathux commented Dec 4, 2024

CameronGo commented Dec 4, 2024

txdFabio commented Dec 4, 2024

zoliszabo commented Dec 5, 2024 •

edited

Loading

conan commented Dec 5, 2024

zoliszabo commented Dec 5, 2024

Falkenjack commented Dec 6, 2024 •

edited

Loading

CameronGo commented Dec 6, 2024

Falkenjack commented Dec 8, 2024

naourass commented Dec 8, 2024 •

edited

Loading

CptnFizzbin commented Dec 10, 2024 •

edited

Loading

zoliszabo commented Dec 11, 2024 •

edited

Loading

dif-engine commented Dec 11, 2024

Quick Access pins broken after 24H2 update #12173

Quick Access pins broken after 24H2 update #12173

Comments

conan commented Oct 16, 2024 • edited Loading

Windows Version

WSL Version

Are you using WSL 1 or WSL 2?

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

github-actions bot commented Oct 16, 2024

Logs are required for review from WSL team

View similar issues

Closed similar issues:

conan commented Oct 16, 2024

github-actions bot commented Oct 16, 2024

haraldger commented Oct 22, 2024

JoanGi commented Oct 22, 2024

GillesJ commented Oct 23, 2024

conan commented Oct 23, 2024

christian-at-sevenlab commented Oct 23, 2024 • edited Loading

fiathux commented Oct 25, 2024 • edited Loading

ashkanr65 commented Oct 25, 2024 • edited Loading

conan commented Oct 29, 2024

Ravenger2709 commented Oct 29, 2024

fiathux commented Oct 30, 2024

Hofundur commented Nov 13, 2024 • edited Loading

haraldger commented Nov 13, 2024

fiathux commented Dec 4, 2024

CameronGo commented Dec 4, 2024

txdFabio commented Dec 4, 2024

zoliszabo commented Dec 5, 2024 • edited Loading

conan commented Dec 5, 2024

zoliszabo commented Dec 5, 2024

Falkenjack commented Dec 6, 2024 • edited Loading

CameronGo commented Dec 6, 2024

Falkenjack commented Dec 8, 2024

naourass commented Dec 8, 2024 • edited Loading

CptnFizzbin commented Dec 10, 2024 • edited Loading

zoliszabo commented Dec 11, 2024 • edited Loading

dif-engine commented Dec 11, 2024

conan commented Oct 16, 2024 •

edited

Loading

christian-at-sevenlab commented Oct 23, 2024 •

edited

Loading

fiathux commented Oct 25, 2024 •

edited

Loading

ashkanr65 commented Oct 25, 2024 •

edited

Loading

Hofundur commented Nov 13, 2024 •

edited

Loading

zoliszabo commented Dec 5, 2024 •

edited

Loading

Falkenjack commented Dec 6, 2024 •

edited

Loading

naourass commented Dec 8, 2024 •

edited

Loading

CptnFizzbin commented Dec 10, 2024 •

edited

Loading

zoliszabo commented Dec 11, 2024 •

edited

Loading