Windows 10, Version 1809. Network does not show computers

Removing the trigger has worked for me on my 2 computers. If your network is already private and stays private, removing the trigger does not add any risk. Your computer name will only be published on your private network.

If my statement is not true as you say, how do you explain that removing the trigger is a workaround that works?

@BonoitHuard,

Removing the trigger changes the timing the FDResPub is started, that may be why it works.

The same reason why Enabling Remote Desktop also works.

If you check, the service is started and it is up and running even when you have the problem, that means that the trigger is starting the service, but it is not publishing the computer name, it only tries to publish the name one time when the service starts up and there is no recovery when it fails.

As I said before and Pauli confirmed, the problem affects only some Ethernet adapters and it seems a timing issue, they should check that the network is up and ready before starting the service.

MS never investigated the root cause of this bug and they have ignored the feedbacks from the users.

According to what they write here they were supposed to hide the Computer when the profile is set to public, but instead you can still use printer and file sharing even when the profile is set to Public as long as you enable it in the advanced sharing settings.

It seems they never enforced this restriction as written here, perhaps that was the intention with that trigger, but it doesn't work correctly.

When first preview of 19042 (20H2) was release to insiders about year ago I did clean install of all systems and  give up all workarounds to get PC's to show in network section. I still test new workarounds occasionally, but normal I use only shortcuts \PCname in quick access list. It's fast and easy to create when needed to access some shared resource first time and it's working fine.

I agree that not everyone has to deal with this issue. It seems to depend on the ethernet adapter. But if you have to deal with this issue as I did, removing the trigger gets rid of it. Why would you not recommend this workaround. It is certainly better than activating remote desktop in terms of risk.

"The problem is if your network is already Private the trigger is not activated and FDResPub is not started."

As I said in my reply on page 20 I have for PC's (with nine installed Windows) and all of those network is set to Private and FDResPub (Manual, Triggered) start running when PC is started. Only some of those have that networking issue while others are working without issues.

On Asus desktop this issue is only with onboard ethernet adapter, when separate NIC card has no issues.

As already said in this thread, removing trigger and setting FDResPub to automatic is one workaround, but main thing is that those default settings are working with some PC's / network adapters, but not on all.

Removing the trigger has worked for me on my 2 computers. If your network is already private and stays private, removing the trigger does not add any risk. Your computer name will only be published on your private network.

If my statement is not true as you say, how do you explain that removing the trigger is a workaround that works?