File Explorer may not detect other devices or perform file sharing on the local network when running Windows 10 version 1803

Anonymous
2018-06-22T02:04:41+00:00

After installing the Windows 10 April 2018 Update (Windows 10 version 1803), File Explorer cannot connect to other devices running version 1803.  When clicking the Network tab in File Explorer, other devices on the home network running version 1803 do not appear, and thus I’m not able to perform file sharing or access files on other devices on my home network.

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
Answer accepted by question author
Anonymous
2018-06-22T02:12:16+00:00

Microsoft is aware of reports that devices running Windows 10 version 1803 cannot connect to other devices on their home network and is investigating the issue.

You can resolve this problem by setting some services to Automatic (Delayed Start) and restarting Windows:

  1. Press the Windows Key and R at the same time to bring up the Run dialog.
  2. Type services.msc in the Run dialog and press Enter.
  3. For each of the following services, locate the service in list, right-click the service and select Properties.  Then set the Startup type to Automatic (Delayed Start) and select Apply.
    • Computer Browser (Browser)
    • Function Discovery Provider Host (FDPHost)
    • Function Discovery Resource Publication (FDResPub)
    • Network Connections (NetMan)
    • UPnP Device Host (UPnPHost)
    • Peer Name Resolution Protocol (PNRPSvc)
    • Peer Networking Grouping (P2PSvc)
    • Peer Networking Identity Manager (P2PIMSvc)
  4. Restart Windows.

Should you have any other concerns don't hesitate to post back.

Was this answer helpful?

200+ people found this answer helpful.
0 comments

240 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-07-23T20:01:51+00:00

    This thread represents was the first admission from Microsoft that file sharing was broken.  Nothing else had worked so for the services listed in the preferred solution below, I tried to change the service start state to 'Automatic (Delayed Start)'.  As noted, that wasn't possible on the following services

    Computer Browser service:

    The service seemed to stop and restart normally until I tried to "apply" the new settings, which prompts this error message:

    "The delayed auto-start flag could not be set.  Error 87:  The parameter is incorrect."

    This error is particularly egregious, because Microsoft is responsible for the

    C:\WINDOWS\System32\svchost.exe -k netsvcs -p

    command that is the source of the error!  The solution seems obvious.  I don't know what the right arguments might be, so I can't try them in the "You can specify the start parameters. . ." box at the bottom of the Service Properties window.

    Peer Name Resolution Protocol (PNRPSvc) service

    The service wouldn't start.  It whined that

    "Windows could not start the Peer Name Resolution Protocol service on Local Computer. Error 0x80630203:  Unable to access a key."

    The nimble wit who wrote the error message was too lazy to tell us which key was inaccessible.

    Peer Networking Grouping (P2PSvc) service

    The service wouldn't start, instead producing

    "Windows could not start the Peer Networking Grouping service on Local Computer.  Error 1068:  The dependency service or group failed to start."

    The Peer Name Resolution Protocol service depends on the Peer Name Resolution Protocol service, so it can't run until Error 2) is fixed. 

    From what I see in this thread, this problem has more than one root.  The Buddhists posit ten thousand paths to righteousness.  Microsoft spawned ten thousand bugs to smash up file sharing and remote desktop connection.  Hell has a new circle waiting for the incompetents who created this mess.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-07-23T20:19:24+00:00

    what really **** is that prior to the LAST update my network worked fine. now I can only see the computer I am on in the network.

    I have been a long, long time user of windows but now I am losing faith in the products.

    maybe since my network worked fine before the upgrade maybe Microsoft should give us the means to revert back to the state before the update.

    or better yet FIX THE PROBLEM YOU CAUSED.

    I cannot spend all the time to fix this.

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more