Windows 10: Very slow access to mapped network drives in Explorer and Office Apps

I know this issue has been raised on many websites, many times. However, I still have not found a solution. I have tried every registry change and service verification, going so far as to doing a clean install of Windows.I have two very fast Synology NAS devices on my network Cisco managed gigabit backbone and truncated NICs in the NAS devices. There is very little network traffic as I am the only one accessing these devices at any time. I have a newer box with Windows Server 2012 running my domain.The problem I see is that anytime I open Explorer and select one of the mapped drives or

:)

 

Mapped drives not showing up on Explorer

Wanted to mention that I'm experiencing this same issue. Environment here is a Windows Server 2012 R2 domain with network shares and printers mapped by GPO. GPO drive mappings are not on a per-user basis and instead are global for all users.

Affected user can not access mapped drives via explorer, yet NET USE shows drives mapped as expected. Attempting to remap network drives via explorer results in a prompt stating that the connection is already mapped to that drive letter, do I want to disconnect and reconnect it?

Oddly, using applications that provide an 'open document' dialogue can see and access mapped network drives normally. For example, open Word, file -> open -> browse: Left pane shows network shares, clicking on network share shows share contents. Clicking on 'This PC' shows all mapped drives which are navigable and documents can be opened normally. Doing this does not correct the issue with Explorer. Similarly, a command prompt also operates as expected, so it's possible to change to a mapped network drive by the associated letter and to list / copy / delete files normally.

Issue appears to be limited to a single user profile on the workstation displaying the described symptoms. Logging in as another user results in the drives being mapped and accessible as usual. Symptoms persist through reboot. User account with symptoms does not have admin access locally or on the domain.

 

Windows Explorer is too slow when having mapped network drive

Hello,

I got an issue with my Windows Explorer.

I have NAS which is working on demand, not 24/7. It's mapped as network drive in my Win10 machines. Mapping way was the standard one - right-click on This PC -> Map Network Drive.

When NAS is up and running - no issues. When it's off - Explorer starts working extremely slow and laggy. Few examples:

1. When opening This PC, it takes around 2-3 mins to get the list of all drives (physically installed in this particular machine) with size and so on.

2. When creating a folder - Explorer get stuck for 10-20 sec

3. Sometimes Explorer is not refreshing itself - as example, I've created a folder on desktop, but it won't be shown until I right-click on desktop and select Refresh. Same goes for folder renaming, deleting, etc.

Seems that Explorer is trying to reach mapped drive every time I'm opening Explorer, awaiting for connection timeout - then then runs normally.

If there's a way to get it fixed somehow?

many thanks for your help in advance!

Artem

 

W10-32 explorer stops responding on mapped drive access.

If I wait long enough ... several minutes, it seems to access ... finally. Copying files from mapped drive ... same thing ... stops responding but wait long enough and it happens. No such problems with other machines on network. No such problem in the past (worked fine at one time).

W10-32 v. 1909 Build 18363.535
Network drive mapped to M:
DISM and SFC routines to not reveal any problems.

Now, it gets really weird. UNmap drive. Open Explorer. Network drive not found under NETWORK, but still shows as a mapped drive. See screenshot.





I really don't think this is right. If UNMAPPED .. should not show this way. It should show in NETWORK since it is shared. If I click on it as shows AS mapped, Explorer opens it, and it does not stop responding. Access to the drive works perfectly.

Any help is appreciated in advance.

EDIT: Fixed it.

1. Correct file corruption with chkdsk /f
2. Follow the steps below:

Go to gpedit.msc
Under Group policy editor access the following :-
->Computer configuration\administrative templates\network\Lanman Workstation
->"Enable insecure guest logons"


#Go to services.msc
The following should to set to Automatic[Delayed Start]
->Function Discovery Provider Host
->Function Discovery Resource Publication


#Go to Programs and features
Under Turn on Windows Features
->SMB-1.0 File sharing and support all three items should be enabled.

Thank you Netgear Gearhead support.