Windows 10, Version 1809. Network does not show computers

Some of my mysterious network problems were fixed when I deleted my Windows User/Sign In account on my laptop and created a new User account.  Yes, it's a bit of a hassle to rebuild/reload everything, but, it did fix some things seemingly permanently for almost a year now.  Instead, you might try just adding a clean, new user account and see if that account has similar problems or not.  Might be worth a try depending upon how desperate/frustrated you are.  Good Luck!   

Are we still talking about Windows Ver 1809 or Ver 2004 ?

I have 5 Computers with windows 10 Pro v 2004 (Build 19041.450) in my home private network and only 2 exhibited the problem intermittently because it is a timing issue with some network adapters and network discovery service. 

All I had to do to work around the problems was to enable Remote Desktop on the failing machines.

After that I had not had a failure in over 2 years with V 1903, 1909, 2004 and Insider Beta and Development builds.

It looks like the problem occurs when the service Function Discovery Resource Publication is starting before the network adapter is ready.

When I had the problems it was v. 1809 timeframe.  My 1809 era problems went away with the New User account in v. 1809 and have not come back.  I'm now at Win 10 Home x64 v. 1909 Build 18363.1016.  Maybe it's time to retire this "Windows 10, Version 1809. Network does not show computers" thread and move on to more current versions.

I'm on version 2004 now but still experiencing these issues.

I have this issue on multiple machines. Dell machines, Lenovo machines, EVGA  motherboard self built machines. This is an issue that Microsoft is ignoring.

BUT, attention K-Mart shoppers, this is the best fix because it is self contained and fixed all of the issues on all of the machines that I have. It is simple and minimal. Since it is self contained it is easy to remove. Credit goes to an earlier poster. I have needed this on multiple windows versions up to current release.

Add the following to Task Scheduler.

Name:  FDResPub

Description:  Restart the FDResPub service.

Run whether user is logged on or not - Do not store password.

Configure for:  Windows 10

Trigger:  At Startup

Actions:  (here is the magic for no script)

    - Action:  Start a program

    - Program/script:  cmd

    - Add arguments:  /c net stop FDResPub && net start FDResPub

    - Start in:  (leave empty)

Conditions:  start only if the following network connection is available - Any connection

Settings:  (leave defaults)

I have this issue on multiple machines. Dell machines, Lenovo machines, EVGA  motherboard self built machines. This is an issue that Microsoft is ignoring.

BUT, attention K-Mart shoppers, this is the best fix because it is self contained and fixed all of the issues on all of the machines that I have. It is simple and minimal. Since it is self contained it is easy to remove. Credit goes to an earlier poster. I have needed this on multiple windows versions up to current release.

Add the following to Task Scheduler.

Name:  FDResPub

Description:  Restart the FDResPub service.

Run whether user is logged on or not - Do not store password.

Configure for:  Windows 10

Trigger:  At Startup

Actions:  (here is the magic for no script)

    - Action:  Start a program

    - Program/script:  cmd

    - Add arguments:  /c net stop FDResPub && net start FDResPub

    - Start in:  (leave empty)

Conditions:  start only if the following network connection is available - Any connection

Settings:  (leave defaults)

Yes,  that is another workaround that works, restarting FDResPub service takes care of the problem.

Still waiting for MS to fix this bug properly :-(