Windows 10, Version 1809. Network does not show computers

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

Hi skvenus99, 

Strange, I'm not sure what the difference can be, perhaps you have a different issue.

The bug was solid on 2 PC's with 1809 and all the insider previews of 19H1 or 20H1, but the same 2 machines upgraded to released 1903 build 18362.116  work fine without using the workaround that restarts FDResPub . 

I have 5 PC's upgraded to the same 1903 level and none show the bug.

Go figure ?

They will probably fail again on some future update, I guess I'll have to wait and see what happens :(.

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

Hi Galileo1564, 

The problem appears to be fixed in the new Window 10 V 1903 build 18362.116 just released to general users on 5/21/2019.

I upgraded all my PC's from  v 1809 build 17763.529 to v 1903 build 18362.116 and the PC's that were previously failing with 1809 are now working fine with the workaround disabled in Task Scheduler.

All my PC's are showing up in the network and keep showing up normally after PC restart.

Unfortunately the bug is still present with Windows 10 preview 20H1 build 18898.1000.

Since it appears to be fixed with 1903 I hope they add the same fix in the next 20H1 insider preview.

@TCatHF &  @LeonardEllis1

Sadly, it is true, Win 1903 has not fixed this bug.  Interestingly, I have two Win 1809 installations (upgrades from 1703>1709>1803) that do NOT exhibit this problem - network discovery functions correctly.  I also have a 1903 Build 18362 that was a bare metal install which DOES exhibit this problem.  In fact each of the last 4 builds (18358, 18359, 18361, 18362) that I have installed have exhibited the problem.

So, go figure... I would surmise that the dev team has been splashing around in the deep dark plumbing and still has some issues that are not yet resolved.  Perhaps the first 1903 CU may offer some relief...

In short, you still need the FDResPub restart workaround.

It looks to me that the problem shows up on some machines and not on others depending on some combination of hardware and network adapters. 

With 1809 or 1903 In my case I have 2 machines that exhibit the bug and 3 that do not.

With 1803 none of the 5 machines had this issue.

@TCatHF &  @LeonardEllis1

Sadly, it is true, Win 1903 has not fixed this bug.  Interestingly, I have two Win 1809 installations (upgrades from 1703>1709>1803) that do NOT exhibit this problem - network discovery functions correctly.  I also have a 1903 Build 18362 that was a bare metal install which DOES exhibit this problem.  In fact each of the last 4 builds (18358, 18359, 18361, 18362) that I have installed have exhibited the problem.

So, go figure... I would surmise that the dev team has been splashing around in the deep dark plumbing and still has some issues that are not yet resolved.  Perhaps the first 1903 CU may offer some relief...

In short, you still need the FDResPub restart workaround.