This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
In Win10, v 1809 I go to "Network" in file explorer and no computers are showing - neither my computer nor other computers on the network.
I was able to find the ip address of the computer I was searching for and successfully ping it via command prompt.
Any ideas?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
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
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,
Perhaps this is what you are looking for ?
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>
