Windows 10, Version 1809. Network does not show computers

19041.508   May 2020 install on all machines.  Yes, I'm aware of the remote desktop option but....MS should inform/disclose this **** when they make changes on a network item that makes this large of a change.

@Garth Clark, 

Just keep filing Feed Back Hub reports and complaints for the bug with MS.

Doing it just in this thread doesn't do anything unfortunately.

:-(

@Johnb3030,

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.  

I think you are correct that it is a timing issue. One of my systems is a Dell Inspiron 11-3167 Tablet, which is extremely slow. I never should have bought it! Anyway, the FdResPub restart is not working reliably, and I think it is because it needs to be delayed until the system has gotten farther along in the boot-up process.

Windows Task Scheduler has two settings that I need to explore:

1.  On the General tab, there is an option to run with highest privileges.

2.  On the Trigger tab, Edit Trigger, there is an option to delay the task for 30 seconds, 1 minute, 15 minutes, and more. I wish there was a setting between 1 minute and 15 minutes but there isn't.

I'm hoping that I can get it to work reliably on this system with some combination of these settings.

Others have also reported that enabling remote desktop is a fix. However, I'm reluctant to enable this and leave it running, because I've read elsewhere that it is a security risk because it is easily hacked into.

My router has a hardware firewall, and I also have MAC address filtering enabled for the systems that are connected over Wi-Fi. I'm wondering if that is enough protection against this type of hack?

Others have also reported that enabling remote desktop is a fix. However, I'm reluctant to enable this and leave it running, because I've read elsewhere that it is a security risk because it is easily hacked into.

My router has a hardware firewall, and I also have MAC address filtering enabled for the systems that are connected over Wi-Fi. I'm wondering if that is enough protection against this type of hack?

@Johnb3030, 

1. If restarting FdResPub manually makes your computer show up, that confirms that it is a timing problem.

Not showing user in this sample:

2. As for Remote Desktop enabled:

I think for security reason the discovery is set and triggered for private network only, also they would need a computer name and password the get into the remote connection, assuming you set it up that way.

Network Discovery is disabled for public networks. 

I know hackers are resourceful, but I never had a problem yet :-)

Anyway before I tried enabling Remote Desktop I used Task Scheduler to restart FdResPub, that was the first workaround that always worked fine for my affected machines too.

Good luck !

https://blog.netop.com/what-to-know-about-rdp-security

Here is an experiment I just tried which yielded a result which I don't understand:

I had an explorer window open to Network on one of my systems. It was showing all of the computers which were currently running.

Leaving everything else running, I turned off my router, a Synology RT2600ac. Within seconds, all the computers disappeared from the explorer window, as would be expected.

I turned the router back on. After it finished re-booting, some of the computers re-appeared in the explorer window, but others did not, even an hour later. Why?

This could be key to understanding this issue, because it suggests that a brief loss of network connectivity causes some systems to stop Function Discovery Resource Publication, even though services.msc shows it is still running, while other systems continue to operate correctly.