-
Notifications
You must be signed in to change notification settings - Fork 822
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
when installing with wsl --install, linux icon in windows explorer is missing #10872
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. 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. Thank you! Open similar issues:
Closed similar issues:
|
I installed WSL2 via the Windows Store and I just coincidentally noticed that the "Linux" item was missing from the Explorer sidebar. I could've sworn it was there before, for the last year or so I only ever installed WSL2 via the Windows Store. However, I can confirm that the item is displayed after installing the Windows Subsystem for Linux Windows Feature. Also, it doesn't seem to affect the ability to do stuff like open an Explorer window in a WSL filesystem (i.e. |
This is happening to me, installed using wsl --install on Windows 11 |
this is happening to me as well, I've checked the registry and make sure that WSL in optional features is checked and correct. |
This might be the same issue as #11026 See my comment on this issue: #11026 (comment)
@uishon @fitrarhm @WinkelCode @trolledbypro As a workaround, you can try installing version 2.1.1 from here: https://github.com/microsoft/WSL/releases/tag/2.1.1 (simply download |
It didn't work for me actually. |
Which versions did you try? I edited my comment since I tried a few versions. 2.0.14 (latest stable release) and 2.1.1 work for me without the explorer issue. Edit: I have not done any registry tweaks to WSL and have not activated the optional Windows feature for WSL. |
I've tried version 2.1.1.0. It didn't actually work for me, the only things I've changed since uninstalling it previously was double checking if the registry was '0/1', editing that, and turning on/off WSL in optional features. I've installed WSL about a year ago, then, I still have the Linux icon, I've uninstalled it since and reinstalled it this year, and the icon didn't appear for me. |
Try version 2.0.14 which is the latest stable release. This worked for me. Since 2.1.1 did not work for you, I'm not sure how 2.0.14 will behave. |
2.1.1 and 2.0.14 didn't work for me:
And the Linux icon is still missing. I just closed and reopened Explorer, but didn't reboot the machine. |
It seems quite difficult to pinpoint the problem. For me, the latest version 2.1.4 does also have this issue. Reverted back to 2.1.1 for me, icons appear again. |
Guide to get the icon in windows 11, but the process should be somewhat similar to windows 10 as well. |
Thanks! This is just a temporary workaround though. |
Yeah the shortcut in the left panel disappeared for me too, since then using the one mentioned above. |
Fixed in 2.2.1 |
True, I installed the latest version of WSL (https://github.com/microsoft/WSL/releases/tag/2.2.1) and that helped - now there is a "linux" section in explorer If suddenly someone gets an error when installing the |
Windows Version
Microsoft Windows (Version 10.0.22631.2715)
WSL Version
2.0.12.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Install Windows Subsystem for Linux using
wsl --install
(fresh install). Linux icon does not show up in Windows Explorer. Not even after reboot. Wsl itself working well.To work around this, go to add windows feature from Settings and check the Windows Subsystem for Linux checkbox, reboot and then it showed up.
Expected Behavior
Linux icon should show up in Windows Explorer side bar after running
wsl --install
.Actual Behavior
No linux icon.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: