Home network discovery not working after latest W10 Update

Well Ken, their is one guy of many great computer geeks we have on here that really knows his stuff. He is pretty good with networking, along with lots of other problems. @topgundcp if we could maybe get his attention on your problem, he might have a lot more idea's then we have tried already. This is Christmas thou, so most are not on today. But check out some of your drivers, in device manager. I know for a fact Windows will replace NEW drivers, with older MS drivers!! Also factory installed drivers, with again MS drivers. I am not saying that's the problem, but could be worth checking out.
Mike...

Mike,
Bring him on! I'm not the only one with this issue. It is driving me nuts. The system we just repaired (and backed up) ran for several days with Network Discovery still broken. Yesterday, I looked and Network Discovery was working again. This is the third or fourth time it has "Fixed Itself". On the other hand, an old GA-EP45-UD3P system that had been OK decided to turn off Network Discovery. The only machines that seem to be stable when it comes to Network Discovery are the three Z97 based systems. This issue is not a show stopper on my home network since I can manually map the drives on the systems not showing under Network in File Manager. But...it sure ain't right MS.

Well you could send Topgundcp a private msg asking for his thoughts on your problem. When I put the @ sign in front of his name that lets him know about this thread. Have you tried some of the basics like running SFC / Scannow or Dism commands?? just to check for system problems.

Update: If this is just a Microsoft problem, then you might have to wait for a fix for this in a future update.

I can totally relate to this problem,

I just got a budget Tablet from Santa and it runs Win10, of course it worked perfectly, no problems just some minor irritations which are common with using Microsoft, but most seems to work.

Wifi is always reconnecting to my wlan with some problem, because I need to bounce it a few times before I have internet.
Some action centre tiles are sometimes active when actually inactive and vice versa... but bouncing this will resolve that and I can live with that.

That said... it works.... until....I did the (I believe 1511) update.

Before the update, it nicely showed all my other PC's with some share enabled, on the network.

Now after the update, it only shows the tablet itself, however when entering the \\computer-name in the address bar, it navigates nicely to the network computer and shows me all shared folders which are accessible.

But, I just let the tablet go to standby and woke it up and pushed the refresh network several times, and now suddenly it shows the network-computer.

But when I now close the tablet (power off) and open it again, same problem, no other computers to see, it however does detect the TV-set top box and the router always...

My workaround is for now to "pin" a quick access in explorer for all network computers, because after navigating to it they do appear in the list in explorer under network, just not in the window. Windows became just doors I guess

This sure strengthens the idea that this has something to do with the network discovery (timing) not working properly after the update. Sadly I already erased the original Win10 installation so I cannot roll back.. (only a 32GB drive in the tablet )

For sure will keep an eye on this thread, it seems the most active thread with this problem. I just wonder when (or if) we will get a patch for this.

I am still considering the switch to Linux Mint for the tablet (if I can get around the secure boot problem).

Happy new year to you all

Happened to check today and my problem machine is visible again on the network again. This is the third or fourth time it has reappeared since updating to W10 v1511. Hopefully, MSFT did something and it will stay fixed this time?!

I solved the network discovery bug on the 3 computers on my network that had the problem.
To solve it I did the following

Code:

Run services.msc and disable homegroup provider

Run powershell as admin and disable samba 2/3 with the following commands:

Code:

Set-SmbServerConfiguration -EnableSMB2Protocol $false
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi 
sc.exe config mrxsmb20 start= disabled

I had to make sure all accounts were local accounts otherwise I couldn't access any PCs that had local accounts, and then finally, run:

Code:

netcfg -d

And reboot.

If winsock is corrupted, run

Code:

netsh winsock reset

After doing all of that after the 10586 update, I finally have network discovery back.

But can they see Linux devices or Insider preview comps?

I applied the update KB3140743. After reboot Linux server shows in network.

Yay!!

Is the comp the master browser? Discovery works on the MB.