Windows 10, Version 1809. Network does not show computers

@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.

Hallo LeonardEllis1

No matter what I tried, I could not get my network operating properly, with all pcs showing in file explorer, until I'd set up that FDResPub task as explained in the galileo1564 thread.

I also have my router set up to issue ip addresses based on the pc MAC address.  I think it's called MAC binding on some routers.  That way each pc is always given the same ip address.  I found that on another thread, and it's easier than setting up each pc with a manual ip address, but that alone did not solve the problem.

As to why Microsoft keep taking a  working operating system, and then upgrading/improving it to one that no longer works properly, is completely beyond me.

I have tried every suggestion that I found without consistent success.  I have noticed that if I know the IP address of a Windows 10 version 1809 machine, I can see its shares in file explorer by addressing it such: \192.168.1.xxx where "xxx" is the low order 8 bits of the ip address I want to access.  I can then access shared folders and files on that machine but never is the "name" of the machine shown.  A major pain unless I configure static IP addresses on all machines which host shares.  Is this strange behavior intentional on the part of Microsoft or did they simply fail to test their software in the environments in which it is used?

For Years now I have been providing network support to a church with 11 computers networked in a P2P network.  Yes I've had problems with another update, this one being 1809 and then having to find out why we are having network problems.   My question is why are we the ginnie pigs to test your software updates?  Microsoft should be ashamed of themselves and having your users go thru hell researching your terrible revision updates. Did I figure out the problems I've had, yes!  Why do your updates, change network sharing settings for us to find? Getting tired of this game.

Right on!