Windows 10, Version 1809. Network does not show computers

Galileo1564 and @mhanor, 

This is what I see with my machines:

Microsoft Windows [Version 10.0.18362.239]

(c) 2019 Microsoft Corporation. All rights reserved.

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>

As I said earlier I have 5 machines all at 1903 build 18362.239 and only 2 of them used to fail with 1809,

Now with 1903 the 2 that were failing with 1809 are no longer failing and I can confirm that it is a timing issue.

I assume that the trigger used does not insure that the network adapter is up and ready when the FDResPub is started.

The 2 failing machines were the following:

1. Dell XPS 8700 with Realtek PCIe GbE Family Controller , Driver  10.28.615.2018 Dated 6/15/2018
2. MSI GT70-0NC, with Killer E2200 Gigabit Ethernet Controller , Driver 9.0.0.48 Dated 8/31/2018

Currently if all 5 machines are running 1903 Build 18362.239 none fail.

But when I change one of the 5 machines in the same network to the preview Build 18941, then the Dell XPS 8700 fails intermittently after a restart even if it is running 1903 build 18362.239 .

The MSI GT70-0NC with Killer E2200 has now a newer driver 9.0.0.49 Dated 9/20/2018 and I cannot make it fail anymore.

Probably the newer driver is faster to get the adapter up and ready.

I think MS may not be using the correct trigger to start the service, just by luck it may work depending on the network adapter being up and ready before the service FDResPub is started on the trigger.

3 out of 5 of my machines never failed even with 1809, now just one fails intermittently after a restart, while the other 4 seems to work fine every time. 

B.T.W.

I just saw that there is a newer driver for Realtek dated 05/10/2019,  I installed it and tried a few restarts, I could not make it fail yet, we'll see if it is consistent.

@fg2001

This is an erratic problem.  Timing issues are frequently at the root of erratic behaviors...ipso facto, timing is most likely "a" if not "the" probable culprit.  Different hardware configurations frequently lead to variations in timing.  This issue cannot be solved by the users.  It is an issue that must be addressed within the Windows network plumbing which only MS can do.

The best that can be accomplished for now is to "kick" the FDResPub service whenever a machine logs on or wakes up.  Hence, the workaround.

As a side note:  It would be very interesting to know if networks that contain/utilize a WINS server exhibit this issue.  I do not have access to a Windows Server (Windows 10 Pro does not provide the WINS service) and cannot test against this.  If anyone out there does have a WINS server on their network...it would be at least interesting to hear if this issue occurs on a server based network.

Galileo1564, 

Hi,

I'd like to have your opinion on another subject that I posted, but did not get any answer yet.

Could you please look at the link below and post your comments on that thread. I also submitted feedback to MS, but they just seem to ignore the issue.

Thanks, 

https://answers.microsoft.com/en-us/windows/forum/all/windows-10-1903-or-higher-duplicate-usb-devices/dfdb015c-8bc5-46f0-923c-cfdf8bfd7b4f

@fg2001

...see that thread...

Agree. Timing seems to the issue. After 1903 update changing FDRP to delayed auto start seems to have made one of my x299 machines happier. ... at least for now. Network neighborhood does load a little slower the first time after a boot.

No. It got cranky again.