W10-32 explorer stops responding on mapped drive access.

WacoJohn · 12 Jan 2020

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.

W10-32 explorer stops responding on mapped drive access.-w32issue.png

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.

storageman · 13 Jan 2020

Just one caution. SMB 1.0 is known to have many security issues and can be easily exploited by Malware. It was turned off by Microsoft several W10 versions ago. It still resides in windows for support of older network attached appliances. Use it at your own risk.

WacoJohn · 13 Jan 2020

I vaguely recall you warning about this in the past. Thank you. Guess I will have to live with it since Netgear support gave me those instructions. Thank you again.

storageman · 14 Jan 2020

WacoJohn said:

I vaguely recall you warning about this in the past. Thank you. Guess I will have to live with it since Netgear support gave me those instructions. Thank you again.

I have some of the same trouble with Readyshare since I to have a Netgear router. It never wants to re-connect when reboot my system. It's kind of like the readyshare goes top sleep and I've written a short command file that will disconnect the network drive and then reconnect it. Your welcome to use it. Just copy the statements and paste them in a notepad document and save them to your desktop as a .cmd file. Just change the drive assignment ("J:") to what you want and change the "/USER:" statement to your Device name\User Logon name.

Net Use J: /Delete

echo off

:Start2
timeout /t 5 /nobreak >NUL
if exist J:\NUL goto End2
net use J: \\ReadyShare\R_Drive /USER

esktop-Z170\Roger SR /PERSISTENT:YES
if ERRORLEVEL 1 goto Start2

:End2

echo on ******** ReadyShare Mounted **********
echo off

timeout /t 10

WacoJohn · 14 Jan 2020

Very kind and considerate of you. The saga continues. With respect to your warning re: SMB, here is what I have done since.

1. WITH SMB on and the other instructions from Gearhead, the Readyshare device shows up in Explorer under NETWORK. From there, I map it to Drive M: That is the only way I can see it ... AT FIRST.

2. Leaving everything set per instructions and the mapping in effect (shortcut to it on Desktop), I went back and UNCHECKED SMB (all 3 options). Curious as to what would happen, rebooted machine.

3. To my surprise, booted up with a (still) live shortcut, and I took a look at Explorer. No Readyshare in NETWORK, but the mapped drive shows in THIS PC. Amazing ... as it seems I have a shortcut to a mapped drive that does not show in NETWORK.

4. Conclusion: Follow Gearhead's instructions, ... map the drive, and go back and turn off SMB. Seems to be working fine and (ultimately) without SMB active.

I GUESS I have found a good solution. You may have a different opinion. In any case, thank you (again) for your attention....