Windows 10: I cant connect to network drives

I'm on build 9926 using a WD My Cloud which works perfectly on W7. I installed KB3032323, 3049508 and 3035132. Now the mapped drives prior to the WUP are red X'd and W10TP goes into a endless try to populate the system. If I close Explorer, it won't open again, IE, Chrome and MS Outlook won't open either.

This has been verified twice by restoring an image. I may try once more but removing the mapped drives first.

 

That sounds pretty drastic. Wonder why IE, Chrome and Outlook are failing?

I don't map drives. I use the //name convention. You could try that?

 

That might be because Explorer gets stuck during populating. It either hangs or takes forever to reboot after that also but I never waited it out but just force a powered down.

Didn't know there was another option. Any problem with apps that you use your NAS with that way or don't they care?

 

That works, but they should be seen automatically like in previous builds. Got mine fixed by clean install (10041 to 10049).
Not hope to fix that with 10056.

 

Can't use anything past build 9926 because WUP registry patch to hide an item breaks WUP. The forced AMD update breaks my apps.

 

Removing the network drives mapped by letter first, installed the three updates and remapped the drives seemed to work even held after a reboot.

 

Great. Now you have to see if it works with 10061!!

 

Upgraded from 10049, works great!

 

All good here as well. AND we can change NIC properties!

 

I just finished upgrading to 10061 and still had the same issue "the network path was not found" etc. After clicking the Diagnose button I received the same message about not being able to find the DNS server. I went into my properties for the wireless connection, opened the TCP/IP4 properties and under Advanced-Wins-Netbios Setting I selected "Enable NetBIOS over TCP/IP". After making this change I can once again add mapped drives on my Synology NAS.

I still don't know why this made a difference, or why my wired connection, which does work, doesn't require this explicit setting. For now, I'm just happy it's working and I hope this helps anyone who has the same issue I have.

 

That's interesting, cipher. We have never needed to explicitly enable it before, relying on the default. Also weird that it only seems to affect the wireless link.

I'll get 10061 onto my test laptop and see whether that mirrors your experience.

 

No. Our problem before is not "how to fix it". The problem is we "can't fix it".
The option to change the properties was not available to us that's why we mostly rely on clean install.

This is how it was before Build 10061 (10049). The "Properties" is greyed-out.







On this latest build (10061), the option is now available to us:





This solution always works.
Just the same, thanks to @cipher7 for posting it. It will help a lot of members here.
And also, Welcome to Ten Forums! *Smile

 

Not sure why I am being quoted above. I know all about the greyed out Properties in 10049. See my earlier posts.

 

I didn't say you didn't know. This forum is for everybody who may find this new development helpful.

 

i just upgraded to 10061 and i still cant connect to network drives, proprieties are not grey anymore thought, what am i supposed to do in there again? something to do with netbios?

Edit Ha!! it worked! thanks cipher7*Wink