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

I agree, this is a workaround and ultimately the problem lies with Microsoft.

After my Reply last night, I, too, noticed that new File Explorer windows lacked the items in the Navigation pane. By luck, however, I'd previously left a shortcut to a folder on one of the other networked machines on my Desktop, and even though the computer was no longer listed in the Navigation pane, the shortcut to it still worked! Not only that, but I could even climb back up the breadcrumbs chain to get to higher levels on the other machine, once I'd accessed it via the shortcut. It seems that if in any File Explorer window you manage to get to the other machine, it will reappear in the Navigation pane - at least for awhile. Next thing I then tried was to create a formal Mapped Drive to that other machine (click on "This PC" and you should have a "Map network drive" should be an option up in the toolbar ribbon, and the "browse" feature seems to now work since the other computer is back on the network, even though you may not see it in Navigation pane). Once I'd created the mapped drive, the other machine always seems to be present even in new File Explorer windows. I'm guessing you could also create shortcuts to the other machine and leave them on your desktop (like I was lucky enough to have done), and the "workaround" is a bit less tedious. One other option would be to add frequently used folders of the remote machine into a Library (for instance, I have a master photos folder on one machine, and I've added it to the "Pictures" library on every machine in my network and now that I've done that "Automatic (Delayed Start)" services adjustment in the original post, I can always get to the other machines via the Pictures Library even when they don't show up in the Navigation pane. So, in summary, to improve the workaround, you might try some or all of these possibilities:

1. Map network drive" to the remote machine - may solve the problem for all File Explorer windows
2. Add frequently used folders of the remote machine to a Library - seems to work even then the remote computer doesn't appear under Network
3. Create shortcut(s) on Desktop to avoid having to go through Navigation pane in the first place

Maybe one of these options will work for you and ease the pain of the "workaround" nature of the problem while Microsoft figures out to fix the problem for real.

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.

I tried this method and funny thing I could not change the everything else I was changed and its now showing my local computer on the networks but not my other PC on my network which seems to be the browsing is still broken so how can I fix that as well?

The error is "The delayed auto startup can not start error 87 the parameter is not correct" 

• Computer Browser (Browser)
• Computer Browser (Browser)

In reply to RO

RogerSMTSpost on 1, July 2018

Hello,

thanks for the help!

"To actually then make the connection to another computer on the local network WHICH YOU KNOW IS ACTUALLY THERE, try typing the computer name in the "Run" window, e.g. \othercomputer.

It worked fine. But for my opinion this is not a solution for the problem. It is something like a workaround.

So I am waiting for the next patch from Windows.

Greetings HPN

In addition 2 remarks:

1. You have to repeat this after a new start.
2. It works only for the used File Explorer Window, not for all.

I have 3 PCs in my LAN. The MasterPC works with Win 10 Pro and the others with Win Home. The Pro PC can not see the LAN-network, but the ohers can see all PCs. I have found out, that the service Computerbrowser is not installed on the ProPC, but on the others.

How can i install this service on the ProPC?

Greetings HPN

In reply to RO

RogerSMTSpost on 1, July 2018

Hello,

thanks for the help!

"To actually then make the connection to another computer on the local network WHICH YOU KNOW IS ACTUALLY THERE, try typing the computer name in the "Run" window, e.g. \othercomputer.

It worked fine. But for my opinion this is not a solution for the problem. It is something like a workaround.

So I am waiting for the next patch from Windows.

Greetings HPN