Windows 10, Version 1809. Network does not show computers

In short, they didn't know what they were doing at Microsoft. First, they set FDResPub to "manual", which made the network invisible because the necessary service didn't start automatically, then they added a useless trigger that waits for a custom event that has already been set (profile changed to private).  

I don't think it is that simple. There must be a reason why they tried to use a trigger. 

1)This service was never set to Automatic, we set it to Automatic in 1803 because when MS changed the home network they forgot they needed to start the service.

2. The trigger seems to work in most cases, it is only some specific machines that have this issue.
3. The service FDResPub is running when we check, but still does not publish the computer, why ?
4. Why stopping and restarting FDResPub fixes the problem given that the service is already running ?
5. Why does the problem go away when enabling Remote Desktop in Windows 10 Pro without ever setting FDResPub to Automatic ?

Would be nice to have a clear explanation of why the behavior changes, rather than just relying on yet another workaround.

If MS can explain why the behavior is inconsistent, then they can probably come up with the correct fix.

5. Why does the problem go away when enabling Remote Desktop in Windows 10 Pro without ever setting FDResPub to Automatic ?

In Settings, if you enable Remote Desktop, there is a checkbox that says "Make my PC discoverable on private networks". So i guess in that case, each time when Remote Desktop is initialized, there is a query if this checkbox is marked and if so, the trigger of FDResPub is activated, making the machines visible. And it fails to activate if Remote Desktop is disabled.

5. Why does the problem go away when enabling Remote Desktop in Windows 10 Pro without ever setting FDResPub to Automatic ?

In Settings, if you enable Remote Desktop, there is a checkbox that says "Make my PC discoverable on private networks". So i guess in that case, each time when Remote Desktop is initialized, there is a query if this checkbox is marked and if so, the trigger of FDResPub is activated, making the machines visible. And it fails to activate if Remote Desktop is disabled.

Again, not all machines are affected by this problem, I have 5 machines with the same default setting, only 2 of those machines exhibit the issue, ( Remote Desktop disabled on all 5 ).

Why would the same trigger work fine on 3 machines and fail just on 2 ?

From what I've seen it looks more like a timing issue of when the FDResPub is actually started.

Even on the 2 failing machines the problem is intermittent with windows 10 1903 and 1909, while it fails every time with 20H1 build 19033.1.

The setting is all the same and the triggerinfo for FDResPub is the same on all machines.

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>

Maybe this is all obsolete. I tried another configuration:

Function Discovery Resource Publication FDResPub: Automatic (Trigger start)

Network List Service netprofm: Automatic

All my PCs are suddenly visible with that setting. Have to wait and see if this is consistent.

Edit: Not reliable. I've rebooted several times, sometimes the PC appears, sometimes not. It really seems to be a timing issue.

Maybe this is all obsolete. I tried another configuration:

Function Discovery Resource Publication FDResPub: Automatic (Trigger start)

Network List Service netprofm: Automatic

All my PCs are suddenly visible with that setting. Have to wait and see if this is consistent.

That didn't make any difference on my failing machines.

Enabling Remote Desktop fixed the problem for me even with insider code 20H1 build 19033.1 .

Still waiting for a response from Microsoft to the insider feedback.