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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-11-30T02:58:31+00:00

    Please see this article about activating SMB v1.0/CIFS File Sharing Support published in September 2016 - https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Stop-using-SMB1/ba-p/425858. In short, SMB v1.0 isn't safe. It is not activated on my computer and it does not need to be activated to solve the issue of Windows 10 Network Computers Not Showing in Explorer.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-11-30T09:05:50+00:00

    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.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2019-11-30T09:32:42+00:00

    cao s haaaaa

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-11-30T20:29:21+00:00

    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.

    Still leaves a lot of unanswered questions.

    With 1803, they had no trigger at all, so you had to set it automatic for the service to function.

    With 1809 they added the trigger, but apparently it is just the wrong trigger, the results are inconsistent, some machines have the problem while other machines do not.

    I'm sure there must be a better trigger that will work for all cases.

    When looking at the service FDResPub it says it is running, so why is it not working and then it works if you restart it ?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-12-01T08:39:46+00:00

    In short, they didn't know what they were doing at Microsoft. First, they set FDResPub to "manual", which made the network invisible because the necessary service didn't start automatically, then they added a useless trigger that waits for a custom event that has already been set (profile changed to private).

    Was this answer helpful?

    0 comments