Xp mapped network drives not updating
%u D83E%u DD19 — Mark Primo Miller (@Mark Primo) January 9, 2019 KB4480970 which is the Jan 2019 roll up for Windows 7 is causing lots of issues with SMB shares.
Just FYI for any IT folks out there dealing with sharing issues today.
' - of course not since I was never prompted :-) If you don't know what the problem it's hard to come up with the solution - I was lucky to find that forum post earlier that pointed me in the right direction.
Hopefully this blog entry with a more explicit title will be a little easier to find.
Over the last few months I've had to install several different VPN clients to connect to customer's private VPN networks - installing and uninstalling the clients and I suspect somewhere in that process the provider entry in the registry got munged.
Provider Order Dialog Thanks to Richard (in comments) I found out that you can also change the provider order interactively, although it takes some digging to get into the Provider Order dialog in Windows.
Microsoft released its update to fix several identified vulnerabilities, including a remote execution flaw in Power Shell and to add robustness against side-channel attacks like those targeting the Meltdown and Spectre flaws.
But a number of users immediately complained of networking issues, with Microsoft confirming there are now three known problems with the January patch.
Further, it failed immediately with: This was very frustrating because network connections for all internet protocols and messaging have been working just fine - it's just that all the Windows based network mapping/location features failed immediately.
The other issues comprise an authentication error, and a file-sharing issue affecting some user accounts. Microsoft Patch Tuesday screwed up a bunch of my clients today.