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

"You can resolve this problem by setting some services to Automatic (Delayed Start) and restarting Windows:" is a misleading statement.

I did exactly as instructed and it did not resolve the problem. The above statement should say that it "may resolve" or "should resolve" but not imply that it will resolve the problem as it does obviously not resolve the problem in ALL cases, as by my example.

I got error code 87 when I tried to change computer browser.

I got an error code 87 incorrect parameter when I tried to change computer browser to automatic delayed.

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.

Hello Roger,

thanks for your help.

I have also noticed the method with the short cut (Netzwerklaufwerk), because I have used these before the 1803 upgrade. At beginning they are passive, but will be activated by a click.

I have to combine this method with the \computer name , because sometimes I am using other directories. These can connected by this method.

I am now waiting for Microsoft to get back the old LAN-connection by File browser.

Greetings HPN