Home network discovery not working after latest W10 Update

FYI another major issue with Threshold 2 Upgrade apparently breaking encryption and other things.

Microsoft has removed TH 2 ISO's from further distribution.

More Bugs: Windows 10 Threshold 2 Breaks Down BitLocker Encryption

Back to my original problem - one computer on the home network that is not being recognized.

I thought that turning off the firewall and rebooting had fixed the problem...and...it did for a day. This morning the computer is no longer visible again! I don't know if it had anything to do with the temporary fix failing but for some reason while the computer was visible the auto logon setup using "netplwiz" stopped working. I reset the auto logon using netplwiz and declared victory. Now auto log on is working but Discovery is not. I have the other six systems on the network set up for auto log on and I used netplwiz to do it. Probably not related but strange. It looks like I'll end up doing a fresh install since I'm not getting a lot of help determining the root cause of the Discovery problem.

DITTO! I spent THREE DAYS trying to figure this out, googling, installing 10586, rolling back to 10242 , reinstalling the updated 10586.11 which was supposed to have "cured" the corrupted NETWORK, WINSOCK and HOMEGROUP system files, resulting a SECOND TIME in computers not being able to see each other on NETWORK folder, and not being able to access their own computer "PUBLIC" files on NW; Then a SECOND rollback to 10240 to get NETWORK functioning back to normal (albeit Homegroup Map lost forever even after rollback).

FAILURES IN SUCH BASIC FUNCTIONS AS ABILITY TO NETWORK HOME/OFFICE COMPUTERS AND SHARE FILES IS UNACCEPTABLE.

Again, who cares about "Cortana" and "200 other new bells and whistles" when in order to get the gingerbread you LOSE NETWORK!

WE WANT FLAWLESS NETWORK CAPABILITIES AND ABILITY TO SHARE FILES. IT IS THE NO 1 ISSUE IN ANY OPERATING SYSTEM.

Hear, hear. This is a major fail by MS and should have been fixed by now.

@Ken429

Did the latest update (KB3120677) solve your problems?

Nope, I was hoping it would but nothing changed that I can tell. I even tried turning off the firewall and turning it back on again after a reboot but that had no effect either. Sure wish someone could shed some light on what the heck I did the other day that had it working for a few hours.

If someone only could shed some light on what is "fixed" in 10586 compared to 10240 re. the network . Just to point in the right direction. Sometimes my shares show up but then they disappear again. For no other reason than it's another time, another day. I'm still on 10240 where all is well but occasionally test new leads on my 10586 image. So far, nothing

It's weird that a lot of people don't have this problem yet I have 5 out of 5 comps on my network all with this problem. Perhaps it indicates it has something to do with the network itself? A Vista comp sees all shares just fine!

There is a good thread here:-
Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586

I have tried ShareEnum from Sysinternals and I get the 'no domain or workgroup found' response.

I, too, hoped that the latest cumulative update would have fixed this but it didn't.

I just can't believe this hasn't been fixed by now - major boo boo, MS.

@DoltJust - yes, weird how it can come right for a short while then revert.

I have a networked wifi printer and due to such problems I was unable to use it most of the time. But till the latest update printing is going on fine but network discovery of computers is still not working!

Re visit the link I gave two posts up as there is some more info. I am pretty sure I can see where the problem lies but I can't fix it.