Windows 10, Version 1809. Network does not show computers

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.

BenoitWard, 

I think the purpose of the trigger was to increase security by making the PC discoverable only if the network is set to Private.

C:\WINDOWS\system32>sc qtriggerinfo FDResPub

[SC] QueryServiceConfig2 SUCCESS

SERVICE_NAME: FDResPub

        START SERVICE

          CUSTOM                       : fbcfac3f-8460-419f-8e48-1f0b49cdb85e [ETW PROVIDER UUID]

            DATA                       : PROFILE_CHANGED_TO_PRIVATE

C:\WINDOWS\system32>

Deleting that trigger and setting FDResPub to Automatic eliminates the problem occurring in some machines, but also allows to turn on network discovery when the network adapter is set to Guest or Public.

Perhaps that may not be the desired result ?  

The workaround that stops and starts the FDResPub service in the task scheduler may still be a better option until a proper fix is released.

"Deleting that trigger and setting FDResPub to Automatic eliminates the problem occurring in some machines, but also allows to turn on network discovery when the network adapter is set to Guest or Public." 

That works anyway, whether the trigger is set or not.

Considering that FDResPub was set to Automatic without any trigger prior to Version 1809, i think there's no harm in deleting the trigger for the time being. All Network PCs being visible is what matters to me.

I've set up the FDResPub stop/start in Task Scheduler (page 5) on 2 PCs and both get a 0x2 error after booting the systems. What am I doing wrong?

incredible this is still a thing.  Tried it again since its been years.   Still fails.  Im stuck with the task to restart the service.  At least thats foolproof thus far.

I've set up the FDResPub stop/start in Task Scheduler (page 5) on 2 PCs and both get a 0x2 error after booting the systems. What am I doing wrong?

There are 2 slightly different procedures described in page 5, both work if you follow the instructions correctly. 

What version of windows are you using ? What is the Build level ? 

Current public release is v 1909 Build 18363.752. 

If you have Windows 10 Professional x64 with the latest build you don't even need the stop/start of FDResPub.

Out of 5 machines in my home network only 2 were failing,  I tried 2 different workarounds to the problem and either one worked fine for me.

1. Stop/Start FDResPub as described in page 5, either with a script or with the direct cmd issued with the task scheduler.
2. Just enabling Remote Desktop was also a good workaround to the problem. 

    (This still works fine with current public release 18363.752 or even with the Insider builds 19041.172 and 19592.1001)  

I don't have any older version of windows anymore, but the same methods worked when I had  Version  1809.