Windows 10, Version 1809. Network does not show computers

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.

Hi TcatHF, 

The bad news is that Microsoft still did not fix this bug even on the new Win 10 1903 (19H1) Build 18362.1.

You still need the workaround to restart FDResPub for the PC's to show up in the network.

The same PC's that were failing with  Win 1809 still fail with Win 1903,  after a year that this bug has been reported  I wonder if Microsoft even looks at the user's feedbacks ?

Out of 5 PC's I have 2 that fail with  1809 and the same 2 machines fail the same way with 1903, the other 3 PC's do not exhibit the bug with either 1809 or 1903.

Keep in mind that all 5 PC's worked fine with older Windows 1803 without this 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!

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.