Windows 10, Version 1809. Network does not show computers

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 ? :(

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. :(

>"I disabled the workaround that restarts FDResPub."

>"Enabled Remote Desktop and after that I cannot make it fail it anymore on either 1903 or 20H1."

I did this same test with two PC's which run 20H1 (build 19013.1000) and one run 19H2 (build 18363.449)

and I get same result that you have.

Sharing was working and File Explorer show all 3 connected PC's under 'Network' when workaround was disabled and RDP enabled.

I leave these settings on to see how it work on everyday usage.

Pauli O, 

Thanks for confirming, no idea why the behavior changes.

This works with Win10 Pro, the Home version does not have Remote Desktop so when they have the same issue they can use the FDResPub restart workaround, until MS comes out with a proper fix,  I added a feedback. 

https://aka.ms/AA6eq5z

OK. You, plarini, Pauli O & galileo1564 are doing great in here. I just meant to say the stop/start of FedResPub method is the only one that will work for Home Edition - if afflicted. I think I showed on pages 2 & 3 of this thread I don't personally have the problem whether on Wi-Fi or Ethernet. But I'm not positive my tests were conclusive since I'm the only computer on my Network.

...I think your latest cure is only half a miracle, if it won't work for Home Edition. But I do believe I never actually had the problem, myself, going by the limited testing I could do (not being on a Network).

PCR, 

All my PC's use Windows 10 Pro.

The suggestion about Enabling Remote Desktop is from another thread as I mentioned above.

It is just another workaround to the problem that fixes all my PC's that exhibit the issue with 1903 or 20H1. 

I have no idea why it changes the behavior, that is a question for MS that never bothered fixing this bug.

Good for you that you never had the issue. In my case it failed on 3 out of 5 machines connected via ethernet.

I have never seen the problem if I connect using wi-fi, but some other users reported the bug also with Wi-Fi.