Windows 10, Version 1809. Network does not show computers

Mostly prompted by a recent issue with MS Office Pro + 2016 which I can only attribute to a V.1809 update, periodically, no office application would open and an on line repair, re-registration had to be carried out to restore, I decided to finally apply the V.1909 feature upgrade to my V.1809 desktop PC..

Took close to 2 hours to fully upgrade but to date it would appear to have cured the issue with MS Office.

I'am running Win 10 Home and have previously implemented the FDResPub fix as outlined in this thread, however, in my case I also had to disable "fast start-up" to ensure the local network was recognised at first boot, have now re-enabled "fast start-up" under V.1909 without any recorded network issues.

I have still left the FDResPub scheduled task routine active, just in case, a few days on have not experienced any explorer network recognition or display issues, time will tell !

I'm happy to see this worked for you also.

BenoitHuard, 

I just tried out removing the trigger to verify that it worked, I really did not need this because with Win 10 Pro the problem can be fixed simply by enabling Remote Desktop.

It is not clear why enabling Remote Desktop fixes the bug, but it does. (Probably changes the time when it starts FDResPub ?)

Unfortunately the Home version does not have Remote Desktop and different work around fixes have to be used.  Personally I like to leave all the default settings if possible. 

Maybe in the next 10 years MS will get this fixed correctly ? :(

Finally! All Network Computers are now visible in Explorer. Thank you so much!

I'm happy to see this worked for you also. The services are set are set as follows on my PC:

1. Function Discovery Provider Host: Manual start, not running
2. Function Discovery Resource Publication: Automatic, running
3. SSDP Discovery: Manual, running (I don't know why it is running if it is set to manual start without a trigger)
4. UPnP Device Host: Manual, not running

I've set my network profile as private while configuring Windows after install.

Hopefully, the trigger will not reappear in future updates. At least, we know what to do if it does.

I agree with you, MS should have fixed this a long time ago.

The network profile is set to private, so if that is what it is looking for, the service should trigger every time, but apparently it is not working even when it says FDResPub is running.

Perhaps that is not the right trigger ? 

I assume that if you eliminated the trigger you set FDResPub to run Automatic , or it would not start at all.

Also it is not clear why restarting the service fixes the problem when it fails.

Anyway I tried eliminating the trigger as you suggested and set it to Automatic and it seems to work. 

It is like going back to 1803 :)

(Perhaps till the next update breaks it again ?)

After over 2 years MS still did not fix this bug. :(