Windows 10: Home network discovery not working after latest W10 Update

My father worked with British Machine Company? during the War. He was in Letchworth in England where some work was done on the Enigma Machine. Do you think I could get info from him? Snowden would not have been able to.

I remember seeing a punched card machine as big as a car. All it did was print what the holes meant.

 

I miss those days. Green /amber screens and purity. Old circuit boards from early computers and phone systems are like art too me.

 

Ditto! The early days of computing were innovation, originality and creativity at it's finest. Having the opportunity to be a part of that era makes you so much appreciate how far we've come from the days when components were so massive. I look at my LG smart phone now and just shake my head how so much computing and storage power fits so marvelously in that slim small device.

 

Even worse is that I worked in it every day for my state job. My wife deals with it in her job, because her company keeps stating that it costs too much to move their stuff from the AS/400 to a SQL database and Gui Frontend.

 

Same here. I could stare all day at the boards from a H-89 or S100 system.

The great thing is that you can still get the schematics and parts list to build a S100 if you wanted.

 

I've got this problem as well. Net view produces an error 1231.

Got four comps all on 10586.11 and I have had no share problems for many months with standard network setup so it sure points to the latest updates. All of a sudden, all four comps with the problem.

There are other fora reporting this as well so we are not alone.

Funny thing, my main comp came right but reverted later.

I have tried uninstalling network adapter and uninstalling Client for MS and File and Printer sharing to no avail.

This is crazy and such a waste of our time.

 

This is exactly why Microsoft needs to toss out this ridiculous new "users don't need to know the details of cumulative updates" policy. That might be fine for the people that don't have tech minds, and those who could care less what's happening in their PC's, but for the kind of knowledgable minds on this forum, it's so totally frustrating being kept in the dark and making us have to scour in a thousand directions that wastes so much of our time trying to figure out the nature of what caused a problem from an update.

So I agree 100% this is crazy crazy crazy. We deserve to know what is in every update and there needs to be better communication from Microsoft with details when things go wrong so we the users can all compare notes and help resolve issues collaboratively instantly instead of this hokey way where you have to go on a hunt to forums all over the place to search for info.

 

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

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

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.

 

Perhaps this isn't a priority issue for Microsoft because out of a Billion users the majority probably only have 1 PC so they don't use Networking and aren't even aware of the problem.

 

Yes, the vast majority won't notice but, hey, it is still a bad look to mess up networking. It should also be an embarrassment.

 

Not usually in a position to be a Microsoft defender but technically "networking" is not broken.

I can access all of the machines on my network as long as I connect to them by name - as in \\hostname.

If anything Win10 has finally entered into the modern era and now can communicate with dns-sd so I can access a Linux or OSX box with a:
Code: \\linux-host-name.local \\osx-host-name.local[/quote] You can even access another Win10 machine that way if you open the appropriate port on it's firewall with a:
Code: \\win10-host-name.local[/quote] I also don't think it's a SMB version issue. When I connect to a Linux box for example it's connecting via SMB3.

The problem appears to be network discovery as it is displayed under "Network" in explorer. All of this appears to point to an issue with the "Function Discovery" process.

I work mostly with small networks ( less than 10 hosts ) so accessing by name is really not an issue. I also don't use Homegroups since I have no idea what that is and as most of the other hosts on my network are either Linux or OSX machines a Homegroup is irrelevant.

 

Admittedly I haven't tried, but are you forced to use homegroup if you're using MS Accounts?

 

From my observations not necessarily. I think the most important element of the puzzle is that we all have a wide variety of PC configurations and hardware/software components, pieces of which may or may not be contributory to the issues. That's always been the challenge for all the software developers out there. Every developer strives for a one size fits all objective as much as possible to save time, costs, and keeping things simple in a global diverse user environment, but inevitably some users will have a hardware/software configuration that doesn't sync with the universal fit and these kinds of problems arise.

Based on all the comments and varying solutions on the many threads, it's apparent that's what's at play.

 

No, I don't have any Homegroups on my network. I log in with a live ID on all my PC's. There is an option to "use user accounts and passwords to connect to other computers" under HomeGroup connections in Advanced sharing settings.