Probably the main reason you don't encounter this random shit on 'proper' networks, is that the domain controllers are always on, and get extra votes in the subnet master browser elections, so they will always be "it", rather than random computers going to sleep, rebooting, turning back on again all the time, so constant changes of what knows about what.
Additionally they act as internal DNS/WINS servers, but I think it's the browse lists that help most.
Don't you remember Microsoft Notworks? Windows (ok older version) just hanging at around 3pm in offices because memory leaks used up all available RAM. Windows Update stopped SQL server from running - that was fun with an office full of people trying to run the office based SQL management system. Or was it the other way around, SQL server updated stopped Windows server? Doesn't matter really.
When was it they promised to start testing again before releasing updates?
How about the Win10 roll-out? Burnt up machines on the fly. What about those poacher hunters in Africa. All running some Windows laptops and used all their funding on download costs over expensive satellite links and in the meantime lost track of the poachers.
Still, they are matched by aircraft software engineers who think Miss = young girl, ie less heavy than a Mrs or Ms and then the crew wonder whiy the dialled in take off power is a bit low.
You can delay ingestion of patches, using the Advanced Options in Windows Update, on Windows 10. This allows the more-eager users to test the patches for you, Microsoft to pull them and re-release them, before the next Patch Tuesday shows up.
Indeed I already do. The wushowhide utility is another tool to stop selective updates until ready. Depending on the update I might like to ensure I've got a partition backup ready, using Clonezilla.
HomeOwnersHub website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.