Windows 10, Version 1809. Network does not show computers

You may well be right in that some network adapters make their network connections faster than others.  And, if this is a timing issue, the hardware response times could be the culprit(s).  A test to see if this is the issue is to find two machines: one that has never exhibited the network connection issue and another that has exhibited the issue - and then perform clean installs of each version of Windows from...say 1703 through 1903...on each machine and monitor the network connection following cold boots and sleep resumes.  This will yield some insight as to whether or not this is a Windows issue or a hardware issue. 

This is not a perfect test though.  The acid test would be taking a given machine and repeating the installs - and - performing this install regimen for different network adapters on the same machine - using adapters that have exhibited the issue and that have not.

That's is a lot of effort for an end user, and frankly, not an end user's responsibility.  This is the type of A:B testing across various versions of Windows that is - or should be - conducted in house by MS prior to release of any Windows version.  That effort is what it takes to tease out these kinds of issues.  Regardless of what one would discover in doing this triage effort, the end user cannot fix this issue if it really is an OS "plumbing" problem.

Hence, for end users, a simple work around and reporting the issue to MS are the best courses of action.

galileo1564,

I believe that Microsoft could fix this bug for any network adapter combination by checking that the network adapter is ready before starting the service Function Discovery Resource Publication.

That would take care of the problem regardless of how long it takes for the different adapters and drivers to be up and running. Unfortunately MS never fixed the bug that was reported over a year ago with the release of 1809.

The fact that it seems to work with 1903 could be just a coincidence and the service FDResPub may be starting when the network is actually already up.

Since the bug is still present with Preview 20H1 build 18898 it means that the bug was never really fixed.

Not so for me. Upgraded 1809 - 1903 last night and the issue still persists! 

Hi skvenus99,

I did a few more checks and I verified that when all my five machines on my home network are at level 1903 build 18362.116 they all worked without using the workaround, but when I have a mixed environment with one machine at different level (like 20H1 build 18898.1000 or  back to 1809 build 17763.529) the other machines in the network may fail too even if they are running 1903.

Apparently the mixed level environment brings back the original bug consistently. 

I had to enable the workaround to get the failing ones to show up in the network.

It looks like the results are deceiving, with all the computers at 1903 it seems to work, but very intermittently I managed to get one of the PC's to fail and not show up after a restart.

With mixed environment they fail every time after a restart.

Are all of your machines exactly identical hardware configurations?

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.