Windows 10, Version 1809. Network does not show computers

Anonymous
2018-10-19T21:34:40+00:00

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?

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

243 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-10-29T16:28:42+00:00

    "I don't have this issue on the same machines if I use Win 10 1803, but the bug is solid with 1809."

    I have seen this same thing happening: Work well with v1803, v1809 doesn't show all computers, preview 19H1 doesn't show any computer. There is certain direction in development: down.

    At least "\PC_name" on file explorer address bar is still working with all versions on those rare cases I need to use shared resources. I have default share of C:\Users -folders and also drive D:\ is shared.

    Hi Pauli O, 

    This problem started with 1809, then it was intermittent with 1903, now it was solid again with 20H1.

    I used the workaround in task scheduler to stop and restart FDResPub and it has worked fine with that.

    Yesterday I saw another suggestion and I tried it out.

    See my recent reply to Galileo1564 above.

    I disabled the workaround that restarts FDResPub.

    Enabled Remote Desktop and after that I cannot make it fail it anymore on either 1903 or 20H1.

    I did many restarts with both 1903 and 20H1 and never failed to show the PC's on the network.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2019-10-29T19:46:24+00:00

    Sorry to rain on your parade, fg2001, since you've done a lot of good in here, but...

    ...I think your latest cure is only half a miracle, if it won't work for Home Edition. But I do believe I never actually had the problem, myself, going by the limited testing I could do (not being on a Network).

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-10-29T20:38:22+00:00

    ...I think your latest cure is only half a miracle, if it won't work for Home Edition. But I do believe I never actually had the problem, myself, going by the limited testing I could do (not being on a Network).

    PCR, 

    All my PC's use Windows 10 Pro.

    The suggestion about Enabling Remote Desktop is from another thread as I mentioned above.

    It is just another workaround to the problem that fixes all my PC's that exhibit the issue with 1903 or 20H1. 

    I have no idea why it changes the behavior, that is a question for MS that never bothered fixing this bug.

    Good for you that you never had the issue. In my case it failed on 3 out of 5 machines connected via ethernet.

    I have never seen the problem if I connect using wi-fi, but some other users reported the bug also with Wi-Fi.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-10-29T21:10:06+00:00

    OK. You, plarini, Pauli O & galileo1564 are doing great in here. I just meant to say the stop/start of FedResPub method is the only one that will work for Home Edition - if afflicted. I think I showed on pages 2 & 3 of this thread I don't personally have the problem whether on Wi-Fi or Ethernet. But I'm not positive my tests were conclusive since I'm the only computer on my Network.

    Was this answer helpful?

    0 comments