-
Win10 patch KB3200970 may cause MacOS network share failures
Noel Carboni sent me an interesting note. Apparently, one of the Nov 9 Win10 patches (most likely KB 3200970, the patch that brings version 1607 up to build 14393.447) resets a setting that can gum up MacOS network shares.
Here’s Noel’s observation:
I just came across this interesting post on msfn.org:
http://www.msfn.org/board/topic/176212-windows-update-causing-mac-os-network-shares-failure/
I haven’t verified it myself, as I don’t have the exact mix of systems he has online right now. But if I’m interpreting it right, beyond a specific unwelcome side effect of applying Windows 10 updates, it catches Microsoft at resetting policy preferences a user had made, and in doing so breaking his network.
Microsoft overriding user preferences is something serious that they seem to be doing more and more of lately – apparently in the name of “WaaS” – and it is something we just cannot accept!
Having Microsoft manage people’s systems config may be a laudable goal, and may even benefit a lot of folks, but it has to be done right on EVERY system – not in an oversimplified way that makes things just stop working for some people! The preferences were provided by Microsoft precisely because the software cannot work in all situations without user-chosen options… Policies are the most carefully provided and managed options.
And now we see a report of a security policy just being reset out of the blue? Who at Microsoft made the decision to do that? Who thinks user preferences are no longer the most important?
As with so many technical things, the devil is in the details, and the details have to be gotten right every time, or the whole basis for WaaS falls apart. The “we know better” vibe from Microsoft needs to be kept in the public consciousness and questioned, because apparently they don’t, at least not always. This is of course especially true now, in light of Microsoft reducing users’ control of updates.
Windows 10 cumulative updates have a long history of resetting things that they shouldn’t. Microsoft’s been working hard to find and fix the problems.
Like Noel, I don’t have the right setup to verify the problem. By any chance, do you know of someone who does?