From 010ed909ec756b1bbffb97f57a970998acdaf886 Mon Sep 17 00:00:00 2001 From: Bill Zissimopoulos Date: Mon, 12 Jun 2017 12:54:06 -0700 Subject: [PATCH] doc: update faq --- doc/Frequently-Asked-Questions.asciidoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/Frequently-Asked-Questions.asciidoc b/doc/Frequently-Asked-Questions.asciidoc index bbf49385..7ea0069b 100644 --- a/doc/Frequently-Asked-Questions.asciidoc +++ b/doc/Frequently-Asked-Questions.asciidoc @@ -10,6 +10,11 @@ I am running Windows 7 and I am finding that the installed driver is not signed. https://technet.microsoft.com/en-us/library/security/3033929.aspx +Disconnecting (unmapping) a network drive does not work. [@carlreinke]:: + + You may have Dokany installed. Dokany installs its own Network Provider DLL that unfortunately interferes with the WinFsp handling of network drives. The solution is to change your system's Network Provider order and ensure that the WinFsp Network Provider runs before the Dokany one. Instructions on how to change the Network Provider order can be found in this http://blogs.interfacett.com/changing-the-network-provider-order-in-windows-10[article]. + + Why is the DLL not installed in the Windows system directories? [@netheril96]:: It is true that this would make it convenient to load the DLL, because the Windows loader looks into the Windows system directories when it loads DLL's. However, in the opinion of the WinFsp author, software that does not ship with the OS should not be installing components in the system directories.