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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-05-28T19:40:38+00:00

    Hmm, it would seem then that the probability that the network adapter hardware is the issue is rather low.  The behavior of you systems is more probably an OS issue rather than a hardware issue per se.  MS has been re-plumbing the black box of Windows for many reasons and boot-up timing could well be changing across various builds as their development work moves along.  Thus, differing versions may be triggering different behaviors - especially where timing sensitive events are occurring...

    This issue is ultimately for MS to triage...and end users to...wait for....

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-05-28T18:39:50+00:00

    Are all of your machines exactly identical hardware configurations?

    Yes, the machines hardware is exactly the same, I also checked the network adapters drivers and they did not change from 1809 to 1903 or 20H1.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-05-28T12:21:08+00:00

    Are all of your machines exactly identical hardware configurations?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-05-28T04:25:04+00:00

    Not so for me. Upgraded 1809 - 1903 last night and the issue still persists! 

    Hi skvenus99,

    I did a few more checks and I verified that when all my five machines on my home network are at level 1903 build 18362.116 they all worked without using the workaround, but when I have a mixed environment with one machine at different level (like 20H1 build 18898.1000 or  back to 1809 build 17763.529) the other machines in the network may fail too even if they are running 1903.

    Apparently the mixed level environment brings back the original bug consistently. 

    I had to enable the workaround to get the failing ones to show up in the network.

    It looks like the results are deceiving, with all the computers at 1903 it seems to work, but very intermittently I managed to get one of the PC's to fail and not show up after a restart.

    With mixed environment they fail every time after a restart.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-05-27T08:13:19+00:00

    galileo1564,

    I believe that Microsoft could fix this bug for any network adapter combination by checking that the network adapter is ready before starting the service Function Discovery Resource Publication.

    That would take care of the problem regardless of how long it takes for the different adapters and drivers to be up and running. Unfortunately MS never fixed the bug that was reported over a year ago with the release of 1809.

    The fact that it seems to work with 1903 could be just a coincidence and the service FDResPub may be starting when the network is actually already up.

    Since the bug is still present with Preview 20H1 build 18898 it means that the bug was never really fixed.

    Was this answer helpful?

    0 comments