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

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 2

incredible this is still a thing.  Tried it again since its been years.   Still fails.  Im stuck with the task to restart the service.  At least thats foolproof thus far.

Answer 3

I have Win 10 Home installed and I've been using the workaround that restarts FDResPub for a long time.

I recently installed a fresh copy (from scratch) of Win 10 v.1909. I was delighted upon the install to see the problem was gone, so I thought. I then proceeded to update my fresh install using Windows Update and I was really disappointed to see the problem coming back as before. I made sure all the appropriate services were running and starting automatically and they were.

I was intrigued by the fact FDResPub was using a trigger start, regardless if it was set to Manual or Automatic. I did not understand what it really was doing. After some research on Google, I was starting to understand the concept. I found a free software ("Service Trigger Editor") which allows to see what the trigger is for every service. In the case of FDResPub, the trigger is based on the network becoming "Private".

The software also allows to add or remove any trigger for any service. I was curious to see what would happen if I removed the trigger for FDResPub. I removed it and rebooted. I could not believe it but the problem was gone and it did not come back up to now. It is still a bit of a mystery to me why this solved my problem.

In any case, I am sharing my experience hoping it could help others that had to cope with this issue for so long.

You can download Service Trigger Editor from this link "https://www.coretechnologies.com/products/ServiceTriggerEditor/".

Answer 4

For Years now I have been providing network support to a church with 11 computers networked in a P2P network.  Yes I've had problems with another update, this one being 1809 and then having to find out why we are having network problems.   My question is why are we the ginnie pigs to test your software updates?  Microsoft should be ashamed of themselves and having your users go thru hell researching your terrible revision updates. Did I figure out the problems I've had, yes!  Why do your updates, change network sharing settings for us to find? Getting tired of this game.

Answer 5

Hi Albertk_77,

There is still a problem that is not fixed in the latest 17763.195.

The problem affects computers that have both the Ethernet and the wi-fi adapter and they are connected to the router via Ethernet.

For those cases the workaround is to restart the service Function Discovery Resource Publication.

There is a workaround procedure to make the restart automatically described in another thread by  

Plarini.

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.