Windows 10, Version 1809. Network does not show computers

I have seen those 'old style' USB-A to Ethernet adapters, but I don't fancy any extra device hanging on PC's. There is already all kind of things attached to desktops and I would like to keep laptop as 'free' as possible: With wireless mouse only power supply is connected.

At work I have USB-C doc so which make it easy to take that laptop (that's also Dell) to carry if when needed. Extra power and mouse (can't use AutoCAD with touch pad) are always on backpack.

This USB-A to USB-C adapter may have usable some times and it's not so expensive.

"This USB-C to Ethernet adapter"

That's too new technology for my devices w/o USB-C connector.

I just update my previous post with adapter info.

Hi Pauli, 

They have another model with standard USB 3.0 plugs. 

I have that one  in the 1st picture with the USB-C for the Lenovo Yoga 920 laptop, dual use USB 3.0 hub + Ethernet.

Also I can use a small adapter from USB-C (female) to USB 3.0 (male) on machines that do not have USB-C. That is what I used to check it out on all my old machines.  😉

"This USB-C to Ethernet adapter"

That's too new technology for my devices w/o USB-C connector.

I just update my previous post with adapter info.

@Pauli O, 

This USB-C to Ethernet adapter never fails on any of my computers with any Windows 10 Build  19042.746 or 21292.1010. It Always shows the PC in the network correctly without using any workaround. 😉

It uses a Realtek Driver 10.34.6303.2019 

USB GbE Family Controller

Connects to my Router Ethernet ports or Cisco Hub at 1Gb.

The problems only happen with my Internal Ethernet controllers as I mentioned in another thread, some fail solid, some intermittent and may not fail with some specific builds:

1. Realtek PCIe GbE Family Controller              Dell XPS 8700        Desktop
2. Killer E2200 Gigabit Ethernet Controller       MSI GT70-0NC      Laptop
3. Killer E2400 Gigabit Ethernet Controller       Dell XPS 8930        Desktop
4. Broadcom NetLink (TM) Gigabit Ethernet    Dell XPS 8300         Desktop
5. Broadcom NetLink (TM) Gigabit Ethernet    Dell Optiplex 380    Desktop

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