Closed MrBasset closed 1 year ago
Can you take a dump of wslservice? And send it to secure@microsoft.com along with a link to this bug?
Hi @pmartincic,
Our IT department have found that the issue is caused by the product Data Protection Agent by Safend Ltd. Removing this product restored the DrvFs functionality from WSL; so it appears that it is blocking something. We have raised a ticket with the vendor and believe that this will resolve the problem.
I'm going to close the ticket as I don't believe this is a WSL fault.
Windows Version
Microsoft Windows [Version 10.0.19045.3448]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubuntu 22.04 LTS
Other Software
No response
Repro Steps
When trying to start WSL, it will hang indefinitely with no error messages; the process will lock up.
wsl --shutdown
also hangs and the only way to "release" the service is by runningtaskkill /f /im wslservice.exe
.I was able to start WSL by editing the
.wslconfig
and enabling safemode, I then disabled features until it started. Disabling automount "fixed" the start up, but as soon as you try to mount the host disk, the entire wsl session (including any new terminals) lock up.I work on a corporate laptop; corp policy forced the install of the following yesterday - it was after these installs that this issue occurred. I am locked out from Windows Update and cannot revert these patches to test whether they are related or if some other corporate change could be responsible. I do have a team mate that has installed the updates without issue, so
Things I have tried:
I have read that
drvfs
uses P9 in the background to interface between the Host & WSL. It is as though the server isn't running as the WSL seems to stop waiting for a response. I have noted that the LxssManager server is set to manually start and itself doesn't start when WSL is starting. Explicitly starting this service doesn't help though.I am still able to browse the WSL disks from Windows Explorer though, and when doing this the linux kernel starts as does the LxssManagerUser_XXXXXX service.
Expected Behavior
WSL should start and the host disks mount.
Actual Behavior
The terminal locks up and becomes unresponsive.
Diagnostic Logs
strace
Dmesg (note: this is collected when automount is off, and the mount attempt was manual):
Logs
WslLogs-2023-09-26_15-31-21.zip