Network Devices invisible after Windows Update to Build 16299.125

Eagle51 said:

Hey lolcocks,
Sometimes on that update, network stuff gets reset. You've already set network profile back to private, have you double checked all the other network settings ??? If so, can you still access the network shares in File Explorer > Address Bar by using \\THE_PC_NAME or \\PC_INTERNAL_IP_ADDRESS ???

If you can access the network shares using the above ...
1. Start the following Services and set Startup Type to Auto to see if the network shares show up in File Explorer > Networking. It may take a couple minutes or even a reboot.
a. Function Discovery Provider Host
b. Function Discovery Resource Publication
2. You can map network share - Map Network Drive in Windows 10 Network Sharing Tutorials
3. It could be a SMBv1 issue, where SMBv1 (Server or Client or Both) got uninstalled - https://support.microsoft.com/en-us/...r-version-1709

Eagle51 said:

Hey storageman,
Depending on what SMB version your Netgear router uses (older ones use SMBv1), you need to check your Pro system and make sure SMBv1 is still installed ... Control Panel > Program and Features > Turn Windows Features On or Off > SMB 1.0/CIFS File Sharing Support. Also, Win10 1709 added a SMB 1.0/CIFS Automatic Removal, so you can either uncheck the box or go to Task Scheduler > Microsoft > Windows > SMB and disable the 2 tasks it adds.

Note: I have an older Netgear WNDR4000 Router and use ReadyShare USB File Sharing. It uses SMBv1 (Server), so I have to have SMBv1 installed, but I only need the Client part. I have the Server part disabled. Check this thread, post #11 Win7 PC not seeing online Win10 PC after boot - Page 2 - Windows 10 Forums

For more info on 1709 and SMBv1 - https://support.microsoft.com/en-us/...r-version-1709

Samuria said:

There is a video tofollow with good walk throught on this How to fix Network Discovery in Windows 10 - YouTube

I followed each instruction on all my computers.
On about 50% of the machines it worked, on 50% of the machines it didn't.
I double checked on the PCs it didn't work on, redid everything, nothing changed on the PCs it didn't work on. Still unable to view devices in network.

Any other solutions?

Bump.

In settings > Network> Status > at the bottom > Network Reset. PC will restart in 5 minuets. When it comes back up, there will be a box asking do you want this PC to be discovered. Check yes. That fixed mine.

Hi there

Hope you all had a good Xmas and wish a happy New year and enjoying holidays for those that get an extended break (e.g me till 03 Jan !!)

Still have the problem THE OTHER WAY AROUND with regard to NAS servers -- W10 machine can see other Windows (various versions from XP to W10) and connect to shares - however W10 with latest update can't be accessed FROM the NAS servers (I have 2 of them). I can see the W10 computer from the NAS network browse (SAMBA) but won't connect -- always times out. No problems with other Windows machines.

I've temporarily removed latest update and connection is fine again -- all other suggestions posted on this board have failed to work.

Note connecting TO Windows FROM a NAS might for most be unimportant - however I do need it as I run automated backups on the NAS servers which backs up users data on the client windows machines. I Image the OS on the client's machines themselves but I need also to backup the local data on these machines regularly -- running rsync on the NAS server simply updates users files that have changed during the day -- very simple, and Free -- standard Linux cmd every NAS server will have built in.

I feel that ms doesn't test their Network scenarios before letting releases and updates out of the door. Connectivity BOTH WAYS in any network should work 100% of the time -- and if one way is to be restricted then documentation on that fact should be published.

The CIF feature fixes problems with W10 connecting TO other systems but not connecting TO W10 FROM some Linux / NAS servers. SAMBA on my servers is up to date as are the kernels etc - all working 100% before last W10 update. !!!!

Cheers
jimbo