Loss of interoperability between wsl and windows #7754
Comments
|
Yes, guess I'm also affected by this bug. I can't open |
|
So happy that I am not the only one! I am experiencing exactly this issue. Most basic reproducer is to run
|
|
Can confirm the problem, after a computer restart With |
|
Same issue here, I've reinstalled Windows 11 recently and installed WSL normally from the Windows features and I didn't get that problem, it seems to be only for the Windows store version. |
2 tasks
|
/logs There might also be some info in dmesg, could you share the output? |
|
Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it. Thank you! |
ghost
added
the
|
I don't have anything under /logs, but the output from dmesg is the following: Is this helpful to find the problem ? Currently WSL is completely unusable unfortunately :/ |
|
Here's my |
|
And here is what the |
|
I have this exact same problem on windows 11! I installed kali-linux and setup git-for-windows aswell as git in kali. Usually, if I use git within the first 10 minutes or so after booting my computer, everything works normally. But seemingly at random, git cannot access the credential-helper anymore and I cannot push/pull anything from within linux. Whenever this happens, access from explorer to the kali directory does not work anymore (explorer attempts to load but nothing happens). Strangely, running the WSL enabled nvidia-driver, I can access it from kali without issues, even if the problem occured. Here is what I noticed so far:
|
|
Same issue: #7782 ? |
Looks like the same to me. We resolved it by uninstalling the Windows Subsystem Linux Preview app from the Microsoft Store and using the "native" one (enabled via the features) and it started working without any issues so far. |
This unfortunately breaks graphical apps working out of the box, as well as the nvidia wsl-ready driver. |
Not quite true. |
|
Can confirm, that uninstalling the store version seems to fix the problem for the time being. |
|
Here is the command for people who end up looking here. You need to run this in an elevated PowerShell prompt. |
2 tasks
Does this keep the distros and their files? |
|
Yes, it does. |
|
Removing the store version and installing the newer version of WSL via |
|
When I try I have had to go and enable the WSL option in the features panel
then restart, but it looks like the WSL app reinstalls itself?? |
|
Ignore this, I didn't know that the WSL app wouldn't respect the default distro selected for the terminal! |
|
You can always take a look at Though I don't think that is related to the issue here. |
Oh, well, this is interesting!
Even though I have Fedora set as the default, Ubuntu is what's opened, so it is in fact two different filesystems 🤦 Ok, I can work with Ubuntu! |
Do you have the Windows Subsystem for Linux, Windows feature turned on for this fix? |
Yes, it has to be enabled. |
|
I'm not sure this is entirely a WSL2 issue. I'm noticing launching apps via powershell is also intermittently failing, and sometimes cmd.exe and pwsh.exe refuse to finish launching inside windows terminal. Here's an example of trying to launch vscode from powershell core on Windows: I've noticed that whenever the failures occur on Windows side that WSLInterop has also broken. There are Warning messages about DCOM that coincide with each attempted invokation of a failing app in the Event Viewer but searching Google suggests that they're normal behaviour for Windows (I'm not convinced): And the immediately preceeding log message from 50 seconds earlier: |
|
It happens to me only with the store version. I discovered that looks like the service that expose the Linux file system to Windows breaks but one distribution at time. After that every time that you execute any Windows command from WSL where the working directory is in the Linux file system it halts forever. If you instead execute the command from a working directory that is located in Windows like /mnt/c it starts without problem. Hope it helps |
The Windows Subsystem for Linux Preview will get installed when your machine is subscribed as Windows Insider: https://docs.microsoft.com/en-us/windows/wsl/install#want-to-try-the-latest-wsl-preview-features The The related message you get in WSL when you spin up the non-store version: |
2 tasks
|
So, it looks like someone managed to get some logs for this issue. 😊 This happened to me on my Win 11 laptop that's not on an insiders build, so looks like it's not just insiders that are experiencing this. |
|
I'm having absolutely the same behavior reported by @diddledani #7754 (comment) |
|
I just ran into this again with the latest release of WSL, 0.51.0 released on January 14. Many of my WSL workflows rely on being able to call Windows binaries from the WSL side. This bug breaks all of them, so I will have to revert to the old system (non-store) WSL. |
|
Sadly I am experiencing that issue quite often. After a number of opening and closing files using vscode from WSL, the interop between Windows and WSL fails. At this time the Ubuntu 20.04 distro, installed from Microsoft Store, can't be accessed from Windows. However, it can access /mnt/c/ mount. Obviously, vscode is not working in that distro. However, this is quite interesting, I also have the latest daily distro of Ubuntu 22.04 for WSL. I don't have any problem there. At this time, from Windows PowerShell I can do:
But when doing this, powershell hangs:
Same behavior happens when trying to access those locations with explorer.exe
|
|
Similar Issue ##7506? |
|
The discussion there and in the JetBrains bug report https://youtrack.jetbrains.com/issue/IDEA-276250 is fascinating. Next time I have the blocking windows command issue, I'm going to try and clear out |
|
Great reference to the Jetbrains thread @cpbotha !
|
I already tried, but removing outdated, or even all, entries in /run/WSL doesn't fix the loss of access to the WSL filesystem from Windows. So far the only option is to restart Windows as |
|
I've switched to using the WSL Windows feature over the Windows App, haven't had an issue since. There doesn't seem to be any identification of what is causing this or how to fix it so far so (for me at least) switching back to the none app version works. |
|
I might be wrong and I might be too optimistic, but i tried upgrading again to the store version with the latest insider build 22557.ni_release.220210-1445 and the problem hasn't happend to me since. The installed store version is 0.51.3.0. |
|
I agree that this version seems to be working again. |
After two days running, the problem hasn't happened. |
|
Does this only apply to a Windows 11 insider build or also if you are running the release version? |
|
I think 22000.527 is the official released version. So it seems it works for all versions (of W11 at least) |
I have duplicated it in Windows 11 22557.ni_release.220210-1445. In my case, 2 computers one using this build and the other using the official release behave the same. When the issue happens, it affects only the failing distro, other distros installed on the same computer retain interoperability in both directions. In my case, it fails only when using the MS Store version of WSL Preview, and works fine when uninstalling it and using the WSL bundled as part of the Windows Feature set. |
That's what I've been using for the past couple of months. At every new release of a store version and every new release of an Insider build I checked if the problems still persisted. And then uninstalled the store version as if failed on me shortly afterwards. But this time that wasn't necessary. I don't know what the main factor was, but I've been running the store version for a couple of days now and didn't face any issues with it anymore. If you're still having the problems, than I might just have been extremely lucky with it. |
|
Here we go again. I'm facing the issues with the store build again in the latest Insider Build 22563.ni_release.220219-1637. |
|
Thanks a lot to everyone who posted logs and helped with this investigation. We have identified the root cause in #7883, so I'll close this as duplicate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Version
Microsoft Windows [Version 10.0.22000.348]
WSL Version
Kernel Version
5.10.74.3
Distro Version
Ubuntu 20.04.3 LTS
Other Software
Visual Studio Code 1.62.3, Remote WSL v0.58.5
Repro Steps
It's quite complicated as it only happens every now and then, but only since updating to the latest store preview version. Everything runs fine at first, but after a while it may happen that the interoperability between WSL and windows stops working. If I then want to open a code window in a current WSL folder nothing happens until I completely restart the machine.
code .Expected Behavior
VS Code opens a new window with the files of the current folder
Actual Behavior
Nothing happens. It just sits there.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: