Windows 10, Version 1809. Network does not show computers

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

All my four PC's are installed with default settings with 'Network discovery' and 'File and printer sharing' turned on and Network is set to 'Private'. On each restart FDResPub is running as shown in fg2001 screenshot. Some cases PC's are visible under File Explorer Netwok, but not allways. It isn't depend on if FDResPub is set 'Manual (triggered)' or 'Automatic'

• Dell Latitude: No network issue    Intel Ethernet Connection I218-LM
• Dell Precision: Network issue        Intel Ethernet Connection I219-LM 
• Dell T5500: No network issue       Broadcom NetXtreme 57xx Gb
• Asus CM6330: Network issue       Realtek PCIe Gb Family Controller (Onboard)   
• Asus CM6330: No network issue  Intel Gigabit CT Desktop adapter (NIC card)

Pay attention to ASUS: Same PC, same settings, different network adapter and different outcome with networking.

I had the same problem and here is how I solved it.

The problem with FDResPub is the trigger. What you need to do is to remove the trigger and set the startup as Automatic. You can do that using the sc.exe command. I prefer using a small app named Service Trigger Editor. Just type it up in Google and you will easily find where to download it from. When you start the app you just find the FDResPub service and remove the trigger. Then open your services, find FDResPub and set the startup type to automatic. Reboot the computer. You can remove the task in Task Scheduler, you won't need it anymore.

I am not sure why Microsoft added this trigger to FDResPub. The trigger is supposed to start the FDResPub service when your network is changed to Private. The problem is if your network is already Private the trigger is not activated and FDResPub is not started. (Not true)

I hope this will help you.

@BenoitHuard,

I know that removing the trigger and setting the FDResPub to start up Automatic is also another workaround.

The trigger was set on purpose for safety to limit the publishing of the computer names only on the Private network.  The question is why does it fail only on some Ethernet connections and not on every build of windows 10 ? The problem has been going on and off depending on the Build level and the Cumulative updates added. It is a timing issue, it fails when the service is started up before the network is up and ready, that is why simply restarting FDResPub fixes the problem.

It only fails on some machines and only on Ethernet, never seen a failure with Wi-Fi. Also it never fails if I use an external USB Ethernet Gbe adapter on any of the affected machines. (I have 6 machines in my network and can reproduce the bug on 5 of them with Build 19042.746 and also with Insider Build 21292.1010).

Here are the information to remove and/or add back the trigger, but that is not a workaround I want to use, nor recommend.

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

sc triggerinfo FDResPub delete

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

I had the same problem and here is how I solved it.

The problem with FDResPub is the trigger. What you need to do is to remove the trigger and set the startup as Automatic. You can do that using the sc.exe command. I prefer using a small app named Service Trigger Editor. Just type it up in Google and you will easily find where to download it from. When you start the app you just find the FDResPub service and remove the trigger. Then open your services, find FDResPub and set the startup type to automatic. Reboot the computer. You can remove the task in Task Scheduler, you won't need it anymore.

I am not sure why Microsoft added this trigger to FDResPub. The trigger is supposed to start the FDResPub service when your network is changed to Private. The problem is if your network is already Private the trigger is not activated and FDResPub is not started.

I hope this will help you.

mputer which has the identical problem is connected via wifi.

>> FDResPub <<

I appreciate your info on the FDFResPub

It took me a while, but as posted, I was able to get the FDResPub task scheduled (and run it) on the original Win10 machine, but, it did not work to allow connecting to a share... I was still unable to connect to the Win8.1 machine even after rebooting the Win10 machine.

It's not clear if you are telling me to do create the same FDResPub task on the Win8.1 machine.

>> Bottom Line <<

There is still a problem with Win10 connecting to other shares on the LAN.  It seems to be related to the rights of the current user logged into the Win8.1 machine.

Thanks again for your info,

Beverly Howard

@BeveHoward, 

Restarting FDResPub is only a remedy for Win 10 in the case that your own PC is not visible on the network.

To see this problem you can turn off all the other machines and just leave one on, if that only machine does not show on the network after a restart then you have this specific bug, otherwise you are facing a completely different issue that has nothing to do with this thread or the workarounds mentioned here.

Problems with a mix of Windows 10 and other older versions 8.1 or 7 may be in other discussions. 

This thread is just addressing one particular problem of Windows 10 that seems to affect only some types of Ethernet adapters.

I was just mentioning that to test if FDResPub restart has any effect, you can just restart it manually as shown here in this snapshot,  no need to set up a task just to see if has any effect.

Another simple way to test this is by issuing the 2 commands below from an elevated command prompt.

C:\WINDOWS\system32>net stop fdrespub

The Function Discovery Resource Publication service is stopping.

The Function Discovery Resource Publication service was stopped successfully.

C:\WINDOWS\system32>net start fdrespub

The Function Discovery Resource Publication service is starting.

The Function Discovery Resource Publication service was started successfully.

C:\WINDOWS\system32>

What is the startup type of the FDResPub service on your problematic machine?

@BenoitHuard, 

The startup for FDResPub is just the default Manual with trigger.

It fails the same if set for Automatic or Automatic Delay Start.

The failure is only with specific Ethernet adapters, never failed with Wi-Fi.

1. Restarting FDResPub always fixes the problem, that is why I restart it through a set up Task in Task Scheduler.
2. As a second remedy, if I enable Remote Desktop in Windows 10 Pro, it never fails either. 

So I have 2 possible remedies for the bug. I use # 1 if I don't want to enable Remote Desktop.