Windows 10, Version 1809. Network does not show computers

19041.508   May 2020 install on all machines.  Yes, I'm aware of the remote desktop option but....MS should inform/disclose this **** when they make changes on a network item that makes this large of achange.

None of these changes do anything for my 4 machines regarding explore the network for computers. My only access to them is to type in the computer name \forexample.  File explorer will not "browse" the network for computers without more detailed information.  Microsoft needs to fix this please.

@Garth Clark, 

What is the Windows 10 Version and Build on your machines ? Please type winver on a cmd prompt and show the results. Are all you 4 machine running the same Build level of windows ?

Microsoft seems to be ignoring this problem that has been going on for years.

Please file or upvote Feed Back Hub reports to push for a solution.

See one here:

https://aka.ms/AA8rxoj

I wish I could help you, but without seeing your setup and network, I don't have anything to suggest.

The workarounds described in this thread all worked for me, even if now I don't need any workaround, I just enabled the Remote Desktop (Not available on Windows Home) on the ones that had the issues and everything works fine. 

I have now 6 computers Running Windows 10 Professional on my private home network and they all show on the network and see each other without any problem.

I have Builds 19041.508, 19042,541, 20221.1000 all mixed in the same network.

None of these changes do anything for my 4 machines regarding explore the network for computers. My only access to them is to type in the computer name \forexample.  File explorer will not "browse" the network for computers without more detailed information.  Microsoft needs to fix this please.

@Johnb3030,

B.T.W.

The service FdResPub shows that is running even with that trigger PROFILE_CHANGED_TO_PRIVATE, that means the trigger is working or the service would not be running.

The problem seems to be a timing issue. If the service Starts before the network adapter is actually ready or not, apparently the publication only happens once when the service starts ? 

That is why restarting FdResPub after the system is up is a workaround that fixes the problem for many users that tried it.

If this is correct, and it looks to me like it probably is, my interpretation is that the only time the trigger is activated is if the network has first been set to public and then the setting is changed to private.

I have all my systems set to private as the default setting, so in the normal course of events I would never be *changing* it to private. Wouldn't this mean the event would never be triggered? Instead of PROFILE_CHANGED_TO_PRIVATE, I would think PROFILE_IS_SET_TO_PRIVATE is what might be needed here.

@Johnb3030, 

That has been my question some time ago, somebody just deleted the trigger and set the FdResPub to start automatically instead of manual and that seemed to work too. There must be a reason why MS added that trigger, but never got any answer to this ongoing issue.

On my Windows 10 Pro I just enabled Remote Desktop and that fixed the problem too without changing any settings or using any other workaround. Why that works is another mystery, I think it just changes the timing on when FdResPub is started. 

 :\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>

To delete the trigger:

sc triggerinfo FDResPub delete

To add the trigger back again:

sc triggerinfo FDResPub start/strcustom/FBCFAC3F-8460-419F-8E48-1F0B49CDB85E/PROFILE_CHANGED_TO_PRIVATE