W10 ver 1803 failed again

I have no idea what it is with W10 f'updates but something in the home network gets broken between machines.  Usually a mapped drive no longer works.  You will see the other machine on the network but can't access shared folders.
 
  Network discovery doesn't always work nor does turn off password protection sharing.
 
  I go through plenty of youtube videos and websites addressing these issues and still fail.  The issue is always with shared and mapped drives.  Two are fine on 1803 but one system could not access my main system's shared drives. 
 
  I don't know if MS is trying to be Apple like with these features I could care less for but I think I would prefer going back to buying an OS upgrade and them releasing a few service packs.  I never had issue with W7 and I miss how networking drives was great for the totally ignorant in XP.
 
 Keeping them offline is not an option.

I do not know if this is related or will work for you but I have had trouble at work accessing our server.  Our IT tech believes MS updates are the cause and showed me a quick fix. "Run" \\server and it resets/finds and reconnects almost immediately.  Sorry, I don't know anymore than that - hope it helps.
 
I have been very fortunate at home with MS updates but our friend Jim Roseberry set it up so there you go!

Jim Roseberry
If you're still having an issue, roll back to previous version of Win10.
 
If you have the Pro version, there are two registry tweaks that'll stop all Automatic Updates.
That way, you can make sure you have an up-to-date backup image file prior to installing any updates.
If anything goes wrong, just reload from your backup image file.
 

What are those settings, Jim?

 There are no shortage of resources on this issue.  A quick fix is a freeware program called Advanced IP Scanner. Teamviewer always works.
 
 Nice that MS allows you to roll back. 
 
 The odd thing on the machine that had to be rolled back again system restore was not on either.
 
  After awhile you get annoyed at reading 72 articles and videos on this subject.
 
 

abacab

Jim Roseberry
If you're still having an issue, roll back to previous version of Win10.
 
If you have the Pro version, there are two registry tweaks that'll stop all Automatic Updates.
That way, you can make sure you have an up-to-date backup image file prior to installing any updates.
If anything goes wrong, just reload from your backup image file.
 

With Pro, you don't even have to touch the registry.
 
There are settings in the Group Policy Editor that will handle that for you.
 

How does one start the Group Policy Editor?

Jim Roseberry
With the particular Registry Tweak I mentioned, you (also) won't be bothered by Update Notifications.
ie: We've got one particular client who doesn't want update-notifications popping up while Slash, John-5, etc are over recording.  Many other folks feel the same.
 
The Group Policy Editor is great for shutting down unwanted components and tweaking Win10 more to your liking.
After having/using it, I can't imagine not having that control.
Most criticisms of Win10 can be addressed/resolved via the GPE.

I'm still interested in knowing

I assume you have the parameter set to "2", correct?
"Notify before downloading and installing any updates."

Cool.
It's the same as placing "NoAutoUpdate=1" in the Registry.  

I'm friends with a Microsoft developer named Tim Noonan.
On The Gear Page forums, I talked about using the GPE to disable "annoying" Win10 components like Cortana.
Turns out... Tim developed much of Cortana.
Put my foot in my mouth on that one...  

Jim Roseberry
I'm friends with a Microsoft developer named Tim Noonan.
On The Gear Page forums, I talked about using the GPE to disable "annoying" Win10 components like Cortana.
Turns out... Tim developed much of Cortana.
Put my foot in my mouth on that one...  

That's pretty funny.

Tim is both a friend and a client... and a pretty good guitar player.
His response was actually very friendly and funny.
IIRC, Tim said (jokingly) that I was, "crushing his soul".