Lost network after 1803 update

SUCCESS !!!!!!!!!
Well, almost, 98% there.

I had to change the Computer Names on all 4 Computers. Then after several re-boots of each one, I finally got
all 4 Computers to show up under Network in Explorer.

Then, there were two folders on one Computer I could not access. After searching I found that in each of those
two folders, under Properties/Security, there was one name missing. That name was on all the other Folders.
I added the name to those two and that issue went away.

Now, the last issue, but I have a workaround. When on Computer A I try to access a Directory on Computer B,
(Computer C has no problem with that access), Network Credentials rears it's ugly head. I found if click on More,
then OK, I get access.

Don't ask me why ... I found from years of painful experience with Software that if you find something that works,
don't ask why. I swear some of these programs are written by people from another Planet !!

So, I finally have my Network back, for now. Who knows what will happen when I try to access some file on another
Computer. Just toss that salt over your shoulder and pray.

Thanks to all that replied,

Richard S.

TonkaNL said:

So this worked like a charm.
Thanks a million!

Thanks from this user too! We use an older file search tool, Multifind, no longer available anywhere on the web AFAIK, to search files and contents on our NAS. After the 1803 update, it refused to work properly. It would show the Network Icon in the Browse for file dialog and would show the NAS but not its contents or shares. This same issue was noted on another search utility, FileSearchy.

After starting FDRP and FDPH both utilities work again. I set both services for Automatic-Delayed start.

Also, a Dell laptop I use (also running Win10 rel 1803), had both services set to manual when I checked but they were running. My copy of Multifind was and is running normally on that machine. That means there may be more to this issue than meets the eye but so far, I'm extremely pleased.

Hello and thank u guys
I fixed my problem by the solution u guys offered but my ping and network is still unstable because MS messed up somewhere in the new update i already lost a lost of time and data because i thought its my problem and tried for days reinstalling and updating my windows.

June 12 update didn't fix "can't see network PCs.

Serious question: how many of you are still using the SMB v1 protocol? I have SMB v1 installed but disabled with SMB v2 and above enabled. With this, the network browser function seems disabled, but the network computers can be reached by typing \\networked computer name in windows explorer if you have each networked computer added to the hosts file in C:\Windows\System32\drivers\etc. Other than that you'd have to type \\ip address instead.

I'm no longer using SMBv1 (uninstalled it) as I no longer have any legacy devices on my network that require it and I don't have any entries in my host file for my networked PC's. Both PC's show in File Explorer > Network and I can access them by \\PCNAME or \\IPADDRESS

My Windows Services are set as follows ...
Function Discovery Provider Host | Running | Startup Automatic
Function Discovery Resource Publication | Running | Startup Automatic
SSDP Discovery | Running | Startup Manual
UPnP Device Host | Not Running | Startup Manual

Note:
1. I have a Netgear AC 1750 with ReadyShare (USB File Sharing) and the USB share drive does NOT show in File Explorer > Network, but I can access it by \\SHARENAME or \\IPADDRESS.
2. If I enable SMBv1 Client & Server the USB share drive will show in File Explorer > Network, but since it actually uses SMBv3 (according to the Powershell command get-smbconnection) ... I just mapped it by ipaddress vs leaving SMBv1 installed.

Clint said:

I did this on both PCs. No fix.

same with me, no resolution.

saltyK said:

Just registered to say thanks for the info here. I spent most of the day trying to get my small network working again after the windows update. I could see the share on the network but could not access the folders despite it working for the last few years. I made sure the services were running and the advanced sharing options were correct and the share folders had correct permissions, everything seemed right but still no joy accessing files although I could ping the other computers. Final solution was simply renaming the PC's on the system, after changing the names I can access everything as before. After changing the PC names, I tried renamed them back to what they were before and had same issue with no access to the folders. After renaming the PC's again all is working. Thanks it's something I would not have thought to do without reading this thread.

I did this... file sharing was back... renamed the PCs back to what they were, sharing has gone again... bloody Windows!!!!!

Access Denied, Your answer to Clint fixed my problem that I have been dealing with for days, now. Although my problem was a bit different, it was similar enough to make the changes in services.msc that you suggested. My problem solved. I should have come to tenforums first!. Thanks

JustDave

Access Denied said:

Ok, first lets make sure the discovery is working properly. There are 2 services that should be running but for some reason in 1803 they never run and cause networking issues.

You need to set two services to automatic (delayed start):



Function Discovery Provider Host
Function Discovery Resource Publication


Open a Run box, (win key + R) type services.msc and press enter to open the Services List. Scroll down until you find those two. Set them to automatic (delayed start). Then right click and start them both. That PC will now show up.

You will need to do this on both machines if they are both on 1803.