Disconnecting drives through Windows Explorer doesn't get a message
See original GitHub issueI’m trying to get an event when a dokan connected drive gets disconnected through Windows Explorer directly (right click -> disconnect). I’ve tried setting several flags, but wasn’t able to get anywhere, even with the mirror.exe from dokany v1.1.0 and v1.3.1.1. I’m not seeing any events via WndProc, at least not for dokan mounted drives. Is this something that’s not passed through on purpose, or am I doing something wrong?
Here’s a simple drive that I mounted and tried to disconnect:
mirror.exe /r C: /l x /n /u \x\u
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
How to remove disconnected drives from Windows Explorer
Open command prompt as admin · Type: net use /persistent:no · Hit Enter · Then open Task Manager (on details for Windows 8+)...
Read more >Unable to Open/Disconnect a Mapped Drive in Windows 10
"net use" in a command window, shows both Z: and Tablet. Both are shown as "Disconnected" and no drive letter is assigned to...
Read more >Mapped drive is disconnected - Windows Client
This article provides solutions to an issue where the mapped drive may be disconnected if you map a drive to a network share....
Read more >Mapped network drive may fail to reconnect in Windows 10 ...
An article provides a workaround to resolve mapped network drives not working in Windows 10, version 1809.
Read more >[Solved] Could Not Reconnect All Network Drives Windows ...
Just right-click on a target network drive in Windows Explorer and select Disconnect. Disconnect Network Drive Method 1. Or, double-click This ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have not changed it. That was my thought too, but the only xml is the .wxs file which I have not changed. I’ll disect the light command and see if there’s something useful there. We tried to build the wix project on several machines, independent from one another, but they all get the same error. Maybe it’s something with the latest wix toolset after all. Thank you for your assistance!
Hi @phobeus , Am sorry I haven’t ever faced this error message. Searching the error seems to be a xml issue, have you changed it ?