Windows 10, Version 1809. Network does not show computers

The only thing that I can think of is to turn the network discovery service off manually then to restart in manually.

One last effort would be to clear the network map on your router. This will clear up conflicts or mismatched ip addresses and computer names. (For most people, they will have have to reset the router.)

Running the test batchfile in an elevated CMD prompt on an offending computer to show up in the network then it disappears 20 to 30 minutes later.

Router has been powered off and recently upgraded. This issue has been ongoing since SMB 1.0 was deprecated due to security issues and as someone else indicated activating Remote Access is also a security issue which had gapping holes that MS patched recently

Running the test batchfile in an elevated CMD prompt on an offending computer to show up in the network then it disappears 20 to 30 minutes later.

Router has been powered off and recently upgraded. This issue has been ongoing since SMB 1.0 was deprecated due to security issues and as someone else indicated activating Remote Access is also a security issue which had gapping holes that MS patched recently

I've been using the workaround to restart FDResPub for 3 years from v 1809 and up now v 20H2 and also insider builds 20251.1 , no SMB of any type is running, sharing and discovery enabled on private network,  it works fine on my 6 computers.

If the network drops it could be when the computers go to sleep and comes back,  a second condition has been added in the task scheduler for that situation.

Here are the settings I use on the machines that are exhibiting the problem. 

Edit:

Note that to avoid the Credential Manager problem that clears the credentials after a reboot you should use a user password to start the task, leave "Do not store password" option unchecked and enter the password when asked.

This new problem about Credential Manager clearing credentials on reboot showed up recently with latest Cumulative updates of windows 2004 and 20H2. 

(I got the Credential issue with build 19042.685 and I unchecked "Do not store password" option to avoid the problem)

I have a Windows10 1909 system that does not show up on a 2004 system. Run the batch file and 1909 shows up on the 2004 system. Insert the task scheduler on the 1909 systtem and reboot. The 1909 shows up on the 2004 system.  Reload/refresh the Network view on the 2004 and the 1909 computer disappears.

 This system is not going to sleep and I even disabled the Power management on the wired NIC port.

I have a Windows10 1909 system that does not show up on a 2004 system. Run the batch file and 1909 shows up on the 2004 system. Insert the task scheduler on the 1909 systtem and reboot. The 1909 shows up on the 2004 system.  Reload/refresh the Network view on the 2004 and the 1909 computer disappears.

 This system is not going to sleep and I even disabled the Power management on the wired NIC port.

The question is, does each computer shows itself up after a PC restart ?

If it show itself, but it doesn't show on another machine you are looking at a different issue.

I had a mixture of 1909 and 2004 before and worked fine with this workaround, now all my machines run 20H2 and Insider Development Builds.

The workaround always worked fine and still works for me now.

I can also work fine fine without this workaround if I enable Remote Desktop on the affected machines.

The problem is a timing issue due to the FDResPub starting up before the actual network adapters are ready to connect.

Here are 4 20H2 19042.610 plus one Development Build 20251.1