Windows 10, Version 1809. Network does not show computers

Enabling does "fix" the problem. I have the problem on a few machines with Oct 2018 update. I decided to use the startup script suggested by others in this thread. I used to have in enabled a while back and it will continue to be enabled on major semi-annual updates. It is still not recommended.  Oddly, my fast machines with i7 and i9.extreme chips, regardless of hardwire or wifi have the problem.

CSAMD, 

If you are referring to SMB version 1, it does not help this problem, the only way I get the PC to show up again is by restarting the service FDResPub even though is started and running. 

Again this does not fail with 1803, but only with 1809 using the same machines and the same hardware. 

All my machines have I7 processors, but only fail when using ethernet,  if I use the wi-fi and disconnect the ethernet I have no issue.

I can't explain it all. SMB version 1 did work but I prefer not to use it. As an aside, many peripherals only use that version with network attached devices.  I keep an antique that I use a gateway when I need access to such devices. My problem started with 1809. Solutions that I have come across suggest that FDRP should be started as delayed automatic.  That did work on the prior version. Perhaps on 18 core machines and other faster machines that's not enough of a "delay" and I am not going to go wifi in lieu of gigabit hardwire. Clearly, none of us should have this problem. It's not so much that there is a "bug" but more so the process in finding out that it is a bug and that we are not doing something "wrong". Unless I am incorrect, msft silence on the issue is deafening. 

I use the script from a prior post. which is essentially restarting Functional Discovery.as posted by fg2001 using the script (or if want batch file) 

cmd /c net stop FDResPub

cmd /c net start FDResPub

For now I did put it in Task Scheduler on one machine and may use it on others pay as you go as needed on others since traffic is usually only one way.

I don't expect a fix until April 2019 update.

Thanks for sharing your experience.

"I use the script from a prior post. which is essentially restarting Functional Discovery.as posted by fg2001 using the script (or if want batch file) 

cmd /c net stop FDResPub

cmd /c net start FDResPub

For now I did put it in Task Scheduler on one machine and may use it on others pay as you go as needed on others since traffic is usually only one way.

I don't expect a fix until April 2019 update."

 Hi CSAMD, 

With Win 10 1803 everything works fine by setting FDResPub service to start as Automatic (No need for Delay start at all), but with Win 10 1809 the service is already started Manually and setting it to Automatic or Automatic (Delay Start) does not help at all. 

I already put the restart in the task scheduler as suggested, with one machine it worked by doing it at Startup, but on another machine I had to do it at Login (Any User) because by doing it at Startup it was still failing intermittently.

As for a MS fix, I just hope they wake up and do some better testing. I have 2 other problems in different threads reported with 1809 feedback, but so far no answer or solution :(

I am empty-headed & stomach-queasy pondering those questions. I tried Googling around, but there is little on the issue, & most is as old as Win 7 or earlier. Someone looked in Event Viewer for it, but found nothing useful. Do you see anything in it? I've got plenty of repetitive junk in mine, but nothing on this issue which I don't suffer. Look first in Administrative Events. If nothing is found, dig deeper under "Windows".

But the fix you developed looks sound to me. I would just check after each OS Build update whether it still is required.

This reply is addressed to all of the people who have tried to solve this problem with not seeing networked PCs. I am 70+ and don't know as much as all of you. But I can see it's not just me trying to get my 2 PC's to see each other and share files It's nice to know that it could well be Microsoft - just trying to change things when it doesn't need changing. I've wasted so much time trying to "fix" the issue and hopefully it will work eventually. I'm not clever enough try some of the options that have been put forward. Need the KISS principle  :)