Windows 10, Version 1809. Network does not show computers

No one has any successful fix for this concern. Some have made changes and said they fixed the issue however, an equal number or greater of people have said that fix did not help. There are many "fixes" out there for this concern but none of them are proven to work for everyone. 

A computer tech went so far as to say "its possible your network card drivers are out of date". I thought about that and responded "how would that have anything to do with it when network discovery worked fine with all previous versions of Windows including Windows 10 up until one of the Microsoft updates made this issue occur"?  

No one really knows what Microsoft did to turn off network discovery. It obviously has something to do with name resolution because anyone can type in the file browser \computer name and windows can then see that computer. Problem is, you cannot browse for computer or view the computers on the network, which is what everyone is concern about. I can see other network devices on the network but not computers with windows 10.

Microsoft should truly address this problem as lots of people have more than one computer on their home network and many businesses also. I use another computer as a file server which is usually always on yet, I have to type in the \computername to connect to it which is rather lame.

In Win10, v 1809 I go to "Network" in file explorer and no computers are showing - neither my computer nor other computers on the network.

I was able to find the ip address of the computer I was searching for and successfully ping it via command prompt.

Any ideas?

Even to this day June 9, 2020 and after the 2004 update, Network discovery does not work in the file browser.  If you know the computer name (\windows10Desktop) it will find it however, the name resolution feature still does not function with windows 10.

Seems to be a completely ridiculous bug that Microsoft must know about yet fails to address the fix.  Why is this feature not working?

The problem has been on and off intermittently through the various updates.

Now I have 5 PC's updated to Win 10 Pro,  version 2004, Build 19041.329 and the problem is still occurring on 2 machines connected via Ethernet,  unless I use the FDResPub restart workaround described earlier in the thread, or I enable Remote Desktop.

The feedback hub is full of reports about this bug, but MS seems to be ignoring it.

Even to this day June 9, 2020 and after the 2004 update, Network discovery does not work in the file browser.  If you know the computer name (\windows10Desktop) it will find it however, the name resolution feature still does not function with windows 10.

Seems to be a completely ridiculous bug that Microsoft must know about yet fails to address the fix.  Why is this feature not working?

What is this?