Windows 10, Version 1809. Network does not show computers

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

Hi Galileo1564, 

I tried your workaround method instead of the previous script on 2 of my computers and it works fine too.

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

galileo

galileo1564 - Thank You, your workaround method seems to be working well for me.  I wonder if there is some way to get notified when MS fixes the problem so we will know when to remove the Scheduled workaround Task.

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