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

It's called a "mapped drive" and you can you make it "persistent" which means it should reconnect automatically.

This article should help:

https://superuser.com/questions/419611/create-network-shares-via-command-line-with-specific-permissions

e.g. if you run

net use drivename: \\hostname\share /persistent:yes

(and having the same user and password on both machines)

the drive should try to reconnect on startup and by "active".

On the other problem.

As you can see from an earlier posting I tested exactly the solution given in the marked solution answer by Microsoft and it works. It's not 100% reliable, maybe 99%. I found that sometimes a client disappears and you have to refresh twice or so to get it back. On the other hand I also found that once I enabled it on a remote PC that PC would appear within a second on my local PC and I didn't even have to refresh. So, not appearing there seem to be glitches.

I completely removed smb v1 and can still see the other PCs. You have to enable these services on all your PCs! Did you do that? (Leave out Computerbrowser, it's of no use anymore in this scenario!)

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.

Hello,

all what is written in your list does not work on my LAN with 3 PCs Win 10 Pro/Home 1803.

But I can share all Data between the 3 PCs by a special procedure.

1. It is neccessary (but simple in this case) to know the name of all PCs in the LAN to connect to a PC by:

Win R

\namePCx

Now I have to identify myself with Windows account name and password.

2. One of the explorer windows now shows me all free directories on this PC. Double click to open the directory on my PC.
3. To establish a long time connection to reduce the procedure at next connection after new start, I activate a network-Laufwerk.

After the new start this Laufwerk has a cross for not active. But double click it and i can use that connection again.

To summarize: connecting is possible, but not to look which PC is in the LAN.

It is amazing for me that big MS has problems with that topic.

Greetings HPN

sorry for the german word "network-Laufwerk". It means that a directory on a other PC will be handeld as a decive/drive on the current PC.

I would think that adding your printer (and problems doing that) is a completely different issue than described in this thead. You don't use "file sharing" protocols for that, but certain printer protocols. You should open a new thread and explain your problem in detail, including relevant network config like IP and hostname of the router and the brand and name and possibly which network printer protocols it supports (if you can figure that out from the manual). And any third-party security program, if you use one. Add a link to that thread here.