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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-01-30T22:42:28+00:00

    I've set up the FDResPub stop/start in Task Scheduler (page 5) on 2 PCs and both get a 0x2 error after booting the systems. What am I doing wrong?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-12-02T07:58:09+00:00

    "Deleting that trigger and setting FDResPub to Automatic eliminates the problem occurring in some machines, but also allows to turn on network discovery when the network adapter is set to Guest or Public." 

    That works anyway, whether the trigger is set or not.

    Considering that FDResPub was set to Automatic without any trigger prior to Version 1809, i think there's no harm in deleting the trigger for the time being. All Network PCs being visible is what matters to me.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-12-02T01:45:48+00:00

    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.

    BenoitWard, 

    I think the purpose of the trigger was to increase security by making the PC discoverable only if the network is set to Private.

    C:\WINDOWS\system32>sc qtriggerinfo FDResPub

    [SC] QueryServiceConfig2 SUCCESS

    SERVICE_NAME: FDResPub

            START SERVICE

              CUSTOM                       : fbcfac3f-8460-419f-8e48-1f0b49cdb85e [ETW PROVIDER UUID]

                DATA                       : PROFILE_CHANGED_TO_PRIVATE

    C:\WINDOWS\system32>

    Deleting that trigger and setting FDResPub to Automatic eliminates the problem occurring in some machines, but also allows to turn on network discovery when the network adapter is set to Guest or Public.

    Perhaps that may not be the desired result ?  

    The workaround that stops and starts the FDResPub service in the task scheduler may still be a better option until a proper fix is released.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-12-01T20:16:37+00:00

    Maybe this is all obsolete. I tried another configuration:

    Function Discovery Resource Publication FDResPub: Automatic (Trigger start)

    Network List Service netprofm: Automatic

    All my PCs are suddenly visible with that setting. Have to wait and see if this is consistent.

    That didn't make any difference on my failing machines.

    Enabling Remote Desktop fixed the problem for me even with insider code 20H1 build 19033.1 .

    Still waiting for a response from Microsoft to the insider feedback.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-12-01T19:37:28+00:00

    Maybe this is all obsolete. I tried another configuration:

    Function Discovery Resource Publication FDResPub: Automatic (Trigger start)

    Network List Service netprofm: Automatic

    All my PCs are suddenly visible with that setting. Have to wait and see if this is consistent.

    Edit: Not reliable. I've rebooted several times, sometimes the PC appears, sometimes not. It really seems to be a timing issue.

    Was this answer helpful?

    0 comments