Windows 10, Version 1809. Network does not show computers

I hadn't paid much attention to this, since I seldom had two machines up at the same time. So, I only tried booting to use WIFI this once for testing. After the Auto delayed start, it worked fine on WIFI.

I wonder if having a "very fast" i7 CPU makes some initialization processes finish faster than planned and messes up the timing. On the other hand, wouldn't a Resource Publishing service broadcast or update every once in a while, in case of local changes and new hosts coming on? Since service is running it would update at some point again.

I hadn't paid much attention to this, since I seldom had two machines up at the same time. So, I only tried booting to use WIFI this once for testing. After the Auto delayed start, it worked fine on WIFI.

I wonder if having a "very fast" i7 CPU makes some initialization processes finish faster than planned and messes up the timing. On the other hand, wouldn't a Resource Publishing service broadcast or update every once in a while, in case of local changes and new hosts coming on? Since service is running it would update at some point again.

@IvanTorres,

The fastest machine I have has i9 Processors and yes it fails easier on that one, it is a time race between the network adapter being up and ready and when the FDResPub is started, unfortunately it only tries to publish the computer name and resources when it first start up. So if it fails the 1st time that is it, it doesn't seem to have any retry built in, and that seems silly. Anyway that is why restarting that service at start up or when the computer wakes up fixes the problem.

There was another workaround by eliminating the trigger and changing the start of the service to automatic.

But this workaround works fine for me, I've been using it for a long time. Also I don't have this problem with Windows insider Build 21322.1000, at least not now, but this problem has been changing on and off with various Windows Builds. :-(.

Your W-Fi adapter seems to be one that supports both 2.4 and 5Ghz going to speeds up to 1.5Gbit, but you would need a similar compatible adapter on the router. What about your Ethernet adapter Brand and Driver ?

Intel® Wi-Fi 6 AX201 (Gig+) Product Specifications

Had problem on WIFI too, changing "Function Discovery Provider Host" and "Function Discovery Resource Publication" Startup Type to "Automatic (Delayed Start)" fixed problem on WIFI, but not on ETH.

Implemented Task Scheduler Job as described on p18, reboot and problem gone. Expect it will stay gone.

Thanks.

Glad it worked for you too.

In my case I've never seen this happening with Wi-Fi, but I think some other users reported it also with Wi-Fi.

It is really a timing issue. The problem with Delayed Start is that you cannot specify how much to delay :-)

What is the Brand and model of the Wi-Fi card ? And what is the driver level and date ?

About the Delayed start...I read the delay is those services start after the last Auto start service starts.

I looked around and found this old article https://answers.microsoft.com/en-us/windows/forum/all/win10-function-discovery-resources-publication/864f3f5d-ff49-4941-a0c5-b76d17d88d17 where MS describes a workaround by having some services start automatically. They apparently are services disabled on that last update, related to Homegroup and Peer to Peer networking.

Out of the services mentioned, Computer Browser was not shown in my system. Started Net Man and the three "Peer" related services. Those Peer services are described as related to Remote Assistance, which is a cousin to Remote Desktop which suggests to me some of these services get activated when you enable Remote Desktop, thus solving the problem.

As I did that, machine appeared on Network Explorer😵. However, I set services to Auto Delayed start and reboot and it didn't work. But, it would be interesting to look at the angle of what services are enabled when Remote Desktop is enabled on the machine.

@IvanTorres,

Some of those articles may be old.

The workarounds for v 1803 were no longer valid on 1809 and all after that.

1803 was the 1st version were they failed to start FDResPub completely and just changing it to automatic was enough to fix the problem.

Starting with 1809 they added a trigger to start the service manually and changing to automatic was not working anymore.

The problem has been the same from 1809 to todays 20H2 and also insider builds.

They never fixed the timing problem they have when starting the service.

Really all they need to do is check if the network is up and ready before they start FDResPub.

Also all my machines are Win 10 Pro and when I enable Remote Desktop everything works fine without restarting FDResPub, I just think remote desktop is just adding another variable to the time the service is started.

All the settings in my machines are the MS defaults that you get with a new clean install.

You are absolutely right. The problem is the trigger they added. I have two machines connected through Ethernet that had this problem. I removed the trigger and changed the startup of FdResPub to Automatic. The problem disappeared and never came back regardless of the build.