Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quick Access pins broken after 24H2 update #12173

Open
1 of 2 tasks
conan opened this issue Oct 16, 2024 · 15 comments
Open
1 of 2 tasks

Quick Access pins broken after 24H2 update #12173

conan opened this issue Oct 16, 2024 · 15 comments

Comments

@conan
Copy link

conan commented Oct 16, 2024

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

Copy link

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:

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

@conan
Copy link
Author

conan commented Oct 16, 2024

See relevant comment: #11252 (comment)

Copy link

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
Copy link

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
Copy link

JoanGi commented Oct 22, 2024

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
Copy link

GillesJ commented Oct 23, 2024

Exact same issue here after updating.

@conan
Copy link
Author

conan commented Oct 23, 2024

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
Copy link

christian-at-sevenlab commented Oct 23, 2024

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
Copy link

fiathux commented Oct 25, 2024

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.

@ashkanr65
Copy link

ashkanr65 commented Oct 25, 2024

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

@conan
Copy link
Author

conan commented Oct 29, 2024

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
Copy link

Same problem for me with WSL quick access dissapeared.

@fiathux
Copy link

fiathux commented Oct 30, 2024

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

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
Copy link

Hofundur commented Nov 13, 2024

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants