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

Hi TheRafeSCV

If you have a problem seeing other PC's in the Network Section in File Explorer:

Click your Start Button, type Services and hit Enter

When the Services app opens, scroll down to find the following services, then double click each one in turn, set their startup type to Automatic and start the service if necessary

1. Function Discovery Provider Host
2. Function Discovery Resource Publication
3. SSDP Discovery
4. UPnP Device Host

Save that and close the Services app

Answer 2

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

2. Save the script at a convenient location. I used C:\Scripts\FDResPub.cmd.
3. 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.

Good temporary solution until MS gets around to fixing this.  I had done a bare metal install of W10 V1809 on a new Intel NUC and fought with the new machine not showing in File Explorer's "Network".  After searching, I came across this thread and the above approach to "kicking" the FDResPub service by doing a restart.  This approach works flawlessly form me.  Admittedly, this is a temporary workaround - but nonetheless, it "is" a functional workaround.

My preference is never to utilize Task Scheduler in a way that requires referencing a user supplied external script file.  Primarily because such script files can get lost and thus break whatever the Task Scheduler is being used for.  My preference is to provide all of the task definition within the task itself.

And, this can be achieved without a script file by defining the task as follows in Task Scheduler:

Name:  FDResPub

Description:  Restart the FDResPub service.

Run whether user is logged on or not - Do not store password.

Configure for:  Windows 10

Trigger:  At Startup

Actions:  (here is the magic for no script)

    - Action:  Start a program

    - Program/script:  cmd

    - Add arguments:  /c net stop FDResPub && net start FDResPub

    - Start in:  (leave empty)

Conditions:  start only if the following network connection is available - Any connection

Settings:  (leave defaults)

...et voila...a self contained task that restarts FDResPub which can be exported for use in future Win 10 re-installs.  This worked perfectly for my machine.  Hopefully, this will provide another approach to a temporary workaround for those who also have this network issue.

galileo

Answer 3

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.

Answer 4

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

2. Save the script at a convenient location. I used C:\Scripts\FDResPub.cmd.
3. 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.

Answer 5

You can also use command line (cmd) to delete the trigger of Function Discovery Resource Publication

Just type

sc triggerinfo FDResPub delete

Enter, and the trigger is gone.

If you want to add it again, type (copy/paste)

sc triggerinfo FDResPub start/strcustom/FBCFAC3F-8460-419F-8E48-1F0B49CDB85E/PROFILE_CHANGED_TO_PRIVATE

To sum up the problem, the trigger caused all the trouble. Once it's deleted everything works fine.

Again, thanks a lot to BenoitHuard, who found the weak spot.

I wonder why Microsoft set the trigger at all, I think it was introduced with Version 1809. Doesn't make any sense.