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 No comments

243 answers

Sort by: Newest
  1. Anonymous
    2018-11-29T04:23:23+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?

    Is the network set for private ? Are all the computers in the same Work Group ?

    Make sure you turn on  network discovery on the advance sharing setting.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-11-29T04:06:39+00:00

    Hi fg2001,

    Thanks for this information. I have the exact same setup you describe and it acts the same way. A restart of the FDResPub service gets it working properly. I came up with a workaround to restart the service automatically at system startup. You may have already done this, but others may benefit.

    1. Create a command script named FDResPub.cmd with these two lines:

    cmd /c net stop FDResPub

    cmd /c net start FDResPub

    1. Save the script at a convenient location. I used C:\Scripts\FDResPub.cmd.
    2. Use Task Scheduler to create a new task:

    Name: FDResPub

    Description: Restart the FDResPub service.

    Run whether user is logged on or not.

    Run with highest privileges.

    Configure for: Windows 10

    Triggers: At Startup

    Actions: Start a program   C:\Scripts\FDResPub.cmd

    Optional start at: C:\Scripts

    This has worked for both restarts and shutdowns with Fast Start disabled.

    Hi Plarini, 

    Thanks for the workaround, I tried it on my MSI GT70-0NC and it worked every time, but when I tried on the DELL XPS 8700 it only worked intermittently after a PC restart.

    So I changed the task

    Triggers: At Logon        At logon of any user  

    That seems to work fine after every PC restart.

    The workaround is fine, but I hope the guys at Microsoft fix this specific issue affecting the machines with both Ethernet and Wi-Fi adapters.

    It appears that if the services Function Discovery Resource Publication is started too early it creates the problem for the machines connected through the Ethernet. 

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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-11-29T02:07:14+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?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-11-29T02:04:51+00:00

    Hi fg2001,

    Thanks for this information. I have the exact same setup you describe and it acts the same way. A restart of the FDResPub service gets it working properly. I came up with a workaround to restart the service automatically at system startup. You may have already done this, but others may benefit.

    1. Create a command script named FDResPub.cmd with these two lines:

    cmd /c net stop FDResPub

    cmd /c net start FDResPub

    1. Save the script at a convenient location. I used C:\Scripts\FDResPub.cmd.
    2. Use Task Scheduler to create a new task:

    Name: FDResPub

    Description: Restart the FDResPub service.

    Run whether user is logged on or not.

    Run with highest privileges.

    Configure for: Windows 10

    Triggers: At Startup

    Actions: Start a program   C:\Scripts\FDResPub.cmd

    Optional start at: C:\Scripts

    This has worked for both restarts and shutdowns with Fast Start disabled.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-11-22T08:45:34+00:00

    Hi TheRafeSCV,

    With Win 10 1809 build 17763.134, I have the problem not showing my computer, but only in the specific case when the PCs have both Ethernet and Wi-Fi adapters and the connection is done through the Ethernet. I gave the detailed description in another post, but for some reason they don't let me put the link to the other post in here.

    Clearly when it does not show my computer, it is also not visible from the other computers in the same network.  Restarting the service  "Function discovery resource publication"  makes my computer visible again. Also it keeps showing after a normal shutdown/power up if the power option for 'Fast Startup' is turned on, but my computer disappears again after a PC restart.

    To recover I need to restart the service  "Function discovery resource publication" again even if it is already running.

    All my computers are on the same workgroup al running the same Win 10 1809 Build 17763.134, network discovery is enabled and my network adapters are set for private network.

    Keep in mind that with Win 10 1803 everything works fine providing that "Function discovery resource publication" is set to start automatic, with 1803 there was a different bug and the service was not started at all unless it was changed to Automatic..

    One more detail for 1809, if I disable the Ethernet adapter and connect to the router with the Wi-Fi adapter I don't have the problem, my computer keeps showing up after any PC restart.

    If I re-enable the Ethernet adapter the bug returns after the PC restart.

    Note that if I issue a Network reset my  computer becomes visible after the first PC restart, but fails after that on every subsequent PC restart.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments