Windows 10, Version 1809. Network does not show computers

Thanks to galileo1564 for the FDResPub "work around" solution.

As a Win 8.1 user until earlier this year I have always experienced this issue, migrated to Win 10 Home with a new build, Gigabyte MoBo, Ryzen-5 CPU desktop PC and had absolutely no issues for the first 2 months until Win update 1809 came along when I started to get random, local network disconnect issues with PC running, had to un-install MoBo, Realtek NIC and re-install to restore LAN comm's even though the network device showed completely health in Device Manager.

As there was recorded history of Realtek LAN driver conflict with Win 10, again believed to be associated with Win updates, decided to fit an Intel PCIe NIC, this worked very well for a week or so then returned to the same issue.

Have tried all combination of drivers on both the Realtek and Intel NIC's without success.

The local network device display issue in Win Explorer also comes and goes and appears to coinside with the random network disconnects.

The good news is the FDResPub, Scheduled Task work around restores both the NIC comm's and Win Explorer LAN device visibility with a re-boot, still annoying but a lot easier than previous requirements.

Perhaps MS will get around to supplying a fix at some stage but won't hold my breath on that one !

Hmm, it would seem then that the probability that the network adapter hardware is the issue is rather low.  The behavior of you systems is more probably an OS issue rather than a hardware issue per se.  MS has been re-plumbing the black box of Windows for many reasons and boot-up timing could well be changing across various builds as their development work moves along.  Thus, differing versions may be triggering different behaviors - especially where timing sensitive events are occurring...

This issue is ultimately for MS to triage...and end users to...wait for....

I agree that this looks like a timing issue.

Given that everything works when FDResPub is restarted after the system is up, I think they just need to check that the network is ready before they start the service. 

It is true that the boot-up timing is changing with each release of windows, but the start of the services should be triggered on precise events after the network is ready.

Right now it just works by luck based on timing of different machines.

Hmm, it would seem then that the probability that the network adapter hardware is the issue is rather low.  The behavior of you systems is more probably an OS issue rather than a hardware issue per se.  MS has been re-plumbing the black box of Windows for many reasons and boot-up timing could well be changing across various builds as their development work moves along.  Thus, differing versions may be triggering different behaviors - especially where timing sensitive events are occurring...

This issue is ultimately for MS to triage...and end users to...wait for....

Are all of your machines exactly identical hardware configurations?

Yes, the machines hardware is exactly the same, I also checked the network adapters drivers and they did not change from 1809 to 1903 or 20H1.

Are all of your machines exactly identical hardware configurations?