Windows 10, Version 1809. Network does not show computers

Question

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?

Answer 1

Hallo LeonardEllis1

No matter what I tried, I could not get my network operating properly, with all pcs showing in file explorer, until I'd set up that FDResPub task as explained in the galileo1564 thread.

I also have my router set up to issue ip addresses based on the pc MAC address.  I think it's called MAC binding on some routers.  That way each pc is always given the same ip address.  I found that on another thread, and it's easier than setting up each pc with a manual ip address, but that alone did not solve the problem.

As to why Microsoft keep taking a  working operating system, and then upgrading/improving it to one that no longer works properly, is completely beyond me.

Hi TcatHF, 

The bad news is that Microsoft still did not fix this bug even on the new Win 10 1903 (19H1) Build 18362.1.

You still need the workaround to restart FDResPub for the PC's to show up in the network.

The same PC's that were failing with  Win 1809 still fail with Win 1903,  after a year that this bug has been reported  I wonder if Microsoft even looks at the user's feedbacks ?

Out of 5 PC's I have 2 that fail with  1809 and the same 2 machines fail the same way with 1903, the other 3 PC's do not exhibit the bug with either 1809 or 1903.

Keep in mind that all 5 PC's worked fine with older Windows 1803 without this workaround.

Answer 2

Great, I'm glad it has helped another victim...LOL.  I'm afraid that there is no "specific" way to be notified if/when this issue is finally addressed by MS. 

I would suggest that after each monthly cumulative update (or the 19H1 upgrade) that you simply go to Task Scheduler, right click the task, click "Disable" (NOT "Delete"), reboot your system, and then check "Network" in File Explorer to see if things are working.  If not, then go back to Task Scheduler and "Enable" the task...and wait until the next month's CU and try this again, etc, etc, etc.  Yep, its clumsy, but I know of no other approach to explicitly validate that this/your issue is solved.

galileo

Answer 3

Great - its always good to hear that a solution is "robust" enough to work for more than just one's own machines!

galileo

Answer 4

Works only on first restart.  I use the scrpit to turn function discovery off then on.

Question will be should we keep this bug or after it is fixed deal with new ones.

CSAMD, 

The script to restart Function Discovery Resource Publication is just a workaround, the bug needs to be fixed properly.

It looks to me that the discovery services are initiated before the ethernet adapter is ready and for that reason the discovery fails. I think the Ethernet adapter needs to be ready before starting the discovery services.

Something is out of sync, given that this works fine with windows 10 v1803.

Answer 5

I am empty-headed & stomach-queasy pondering those questions. I tried Googling around, but there is little on the issue, & most is as old as Win 7 or earlier. Someone looked in Event Viewer for it, but found nothing useful. Do you see anything in it? I've got plenty of repetitive junk in mine, but nothing on this issue which I don't suffer. Look first in Administrative Events. If nothing is found, dig deeper under "Windows".

But the fix you developed looks sound to me. I would just check after each OS Build update whether it still is required.