Windows 10: Windows 10 64bit unable to folder search NAS drives

I just upgraded to windows 10 64bit (from win7 64bit) it's a brand new computer.

I'm having issue searching files in NAS mapped drives. I'm using the search box on the top right of the windows folder screen. It finds some of the files, but often misses a lot of files in the search results.

I've tried a lot of different fixes to no avail, this is driving me nuts.

This simple search use to work very well in windows 7.

Any ideas guys?

:)

 

Cannot reconnect to network shared drive with Windows 10

After months of trouble in getting the NAS drives mapped, all was well until a reboot or a logoff. After a reboot, a popup message briefly appeared just above the lower right corner of the taskbar indicating network drives could not be reconnected.

I have searched and searched for a possible fix or a method to resolve the mystery of reconnecting the NAS shared drive.

Anyone else have this issue with Windows 10?

Topology:

-> NAS 3 Shared folder

-> NAS 2 Shared folder

-> NAS 1 Shared folder

Cable modem -> Router -> 1Gb Network Hub /

\

-> Windows 10 Pro x64 (Windows Firewall NAS ports opened - AVG Antivirus shared access allowed)

If anyone has a viable solution, please consider sharing.

BTW, this is the message that I get when attempting to open the shared NAS link

 

Why is Windows 10 networking so unreliable?

My home network connects to three Windows 10 PCs, 3 Android mobile phones, a NAS drive and various TVs, DVDs etc. The mobile phones always see all other devices on the network. The Windows 10 PCs will sometimes see all the devices but more often than not
do register the NAS drive. Sometime they see each other on the Homegroup, sometimes not even when you can access a folder of another PC using the Network section of Explorer. Sometimes you can see a NAS drive folder by searching for it, other time the Windows
10 PC state that the NAS drive is not connected.

Now this could be because one or more of the Windows 10 PCs is having a "bad hair day" or sulking but it's far more likely to be a coding or timing error. Are these bugs going to be resolved in the new Creative Update or are they just going to continue
to fester and annoy users?