Windows 10: File Explorer crashes or freezes while accessing Mapped Network Drives

​

If File Explorer crashes or freezes while accessing Mapped Network Drives on your Windows 11/10 system, this post may help you fix it. This issue prevents users from accessing the data inside the mapped network drives because every time users try to access them, File Explorer either freezes for a long time or crashes. Explorer crashes […]

This article File Explorer crashes or freezes while accessing Mapped Network Drives first appeared on TheWindowsClub.com.

read more...

 

Mapped Drives Issues

To clarify .... the issue is the Windows 10 OS. It is with Windows File Explorer. The Mapped drives used to appear in File Explorer's left panel list of drives and folders. Two days ago File explorer stopped show the mapped drives. so not they don;t appear in the list of Drives and folders.

- - - Updated - - -

I did, it has no effect. I also check the NAS devices they support SMB 2.0. Also I have several other computers on my home network they work fine with the mapped drives and They do not have SMB 1 turned on. So it is something that happened to the computer in question.

 

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.

 

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.