Windows 10, Version 1809. Network does not show computers

Hi Dave M121

I Sanna day thank you for your help,  on the latest update 1903 , windows was uninstalled func. Discovery hosts, and the other three were manual, 

Now everything works fine.

Hi Galileo1564, 

The problem appears to be fixed in the new Window 10 V 1903 build 18362.116 just released to general users on 5/21/2019.

I upgraded all my PC's from  v 1809 build 17763.529 to v 1903 build 18362.116 and the PC's that were previously failing with 1809 are now working fine with the workaround disabled in Task Scheduler.

All my PC's are showing up in the network and keep showing up normally after PC restart.

Unfortunately the bug is still present with Windows 10 preview 20H1 build 18898.1000.

Since it appears to be fixed with 1903 I hope they add the same fix in the next 20H1 insider preview.

As you can see, I have not checked my Outlook Email account in a very long time.   I am not supporting the church network that was having that problem.  But I am now supporting a different church P2P network and they are still having the same problem.  I will look at the suggested problem bandaid on the new network.  The workaround for the employee users is to type in the search box the computer they are trying to access.  Doing that it immedily brings up the compter on the network.  I then showed the user how to right click and pin the network computer they are try to access to QUICK ACCESS.  This bandaid is a quick fix for the problem.  So the problem has not been fixed even up to the latest 1909 verson.    But thank you for responding and giving me another workaround.

Pauli O, 

The problem was intermittent and time dependent and also depending on the level of the Build installed. In my case only 3 out of 5 computers failed and only the ones connected via Ethernet, I never had any issue with Wi-Fi.

On Dell XPS 8300 with build 19603.1000 or 18363.753 it never fails now and I don't use any workaround, but the same machine used to fail solid with some older builds.

The MSI GT70 Laptop with build 18363.753 or 19041.173 is not failing anymore without any workaround, but used to fail on every restart with older builds.

On Dell XPS 8700 with build 18363.753 I still have Remote Desktop Enabled, I will try to disable it again to see if it still fails, perhaps with latest builds they fixed the original bug ?

Edit:

My XPS 8700 with 18363.753 still failed after a restart when I disabled Remote Desktop.

So I did another network reset and restarted a few times again,  it worked fine each time, we'll see if it lasts...

It did not last, when I booted the other computer with a different code level (19603) the XPS 8700 with 18363.753 started failing again.

I re-enabled remote desktop again to work around the bug.

@fg2001

Today I update my router to 1 Gbits LAN / WiFi 2,4/5 GHz and reset my home network.

When I did this update I disconnect one by one all PC's from network (LAN/WiFi), disable FDResPub script and RDP, run Network reset for all of OS before connecting back to router.

When this was done I didn't enable RDP or FDResPub scritp and all networking between all 3 PC's with different combinations of  builds 18363, 19041 and 19603 was working.

So far after some restarts File manager populate Network environment and shortcuts to other PC's are still working.

I've set up the FDResPub stop/start in Task Scheduler (page 5) on 2 PCs and both get a 0x2 error after booting the systems. What am I doing wrong?

There are 2 slightly different procedures described in page 5, both work if you follow the instructions correctly. 

What version of windows are you using ? What is the Build level ? 

Current public release is v 1909 Build 18363.752. 

If you have Windows 10 Professional x64 with the latest build you don't even need the stop/start of FDResPub.

Out of 5 machines in my home network only 2 were failing,  I tried 2 different workarounds to the problem and either one worked fine for me.

1. Stop/Start FDResPub as described in page 5, either with a script or with the direct cmd issued with the task scheduler.
2. Just enabling Remote Desktop was also a good workaround to the problem. 

    (This still works fine with current public release 18363.752 or even with the Insider builds 19041.172 and 19592.1001)  

I don't have any older version of windows anymore, but the same methods worked when I had  Version  1809.