WSL: [WLS2] Network share not accessible after boot/resume from standby
Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\
See our contributing instructions for assistance.
Please fill out the below information:
-
Your Windows build number: Microsoft Windows [Version 10.0.19041.172]
-
What you’re doing and what’s happening:
- Map WSL as a network drive via 9P.
- Open Explorer Windows to that network drive, browse some folders
- Restart your PC / put it to sleep and wake again
- What’s wrong / what should be happening instead:
Windows should restore those explorer folders on login, instead if errors with "could not reconnect all network drives and closes your explorer windows.
-
Strace of the failing command, if applicable: (If
some_commandis failing, then runstrace -o some_command.strace -f some_command some_args, and link the contents ofsome_command.stracein a gist here). -
For WSL launch issues, please collect detailed logs.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 5
- Comments: 17 (2 by maintainers)
I get this after restarting Windows. The mapped drive is inaccessible. I either have to restart again or from cmd do a
wsl --shutdownthenwslto start it again.