Windows 10, Version 1809. Network does not show computers

I have Win 10 Home installed and I've been using the workaround that restarts FDResPub for a long time.

I recently installed a fresh copy (from scratch) of Win 10 v.1909. I was delighted upon the install to see the problem was gone, so I thought. I then proceeded to update my fresh install using Windows Update and I was really disappointed to see the problem coming back as before. I made sure all the appropriate services were running and starting automatically and they were.

I was intrigued by the fact FDResPub was using a trigger start, regardless if it was set to Manual or Automatic. I did not understand what it really was doing. After some research on Google, I was starting to understand the concept. I found a free software ("Service Trigger Editor") which allows to see what the trigger is for every service. In the case of FDResPub, the trigger is based on the network becoming "Private".

The software also allows to add or remove any trigger for any service. I was curious to see what would happen if I removed the trigger for FDResPub. I removed it and rebooted. I could not believe it but the problem was gone and it did not come back up to now. It is still a bit of a mystery to me why this solved my problem.

In any case, I am sharing my experience hoping it could help others that had to cope with this issue for so long.

You can download Service Trigger Editor from this link "https://www.coretechnologies.com/products/ServiceTriggerEditor/".

>"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

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

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.