|
Patch reliability is unclear, but widespread attacks make patching prudent. Go ahead and patch, but watch out for potential problems. |
.Patch Lady here: Tonight I noticed that the recent update for Windows 10 1709 KB4090913 now includes the following in the release notes indicating th
[See the full post at: Patch Lady – proving that documentation is key]
Susan Bradley Patch Lady/Prudent patcher
Man, I have my fingers crossed.
Wonder why they didn’t document the INACCESSIBLE part, in the first place?
Remember this quote from Microsoft‘s Brad Anderson?
“Our long term vision on Windows 10 management is that organisations should rely on Microsoft to do more for them on their behalf. Let us worry about your images. Let us keep your devices updated through Windows Update for Business. Rather than you approving which patches you want, we are saying let them all flow because the way organisations get the most secure, the most compliant, the most reliable and most performance devices is to stay updated with all of our updates.”
While that blurb was clearly about enterprise updating, it’s quite obvious that their attitude about “let us worry about it” carries over into the consumer sector as well, with even more control demanded by Microsoft over the machines upon which Windows runs than in the enterprise sector.
Wouldn’t the relative paucity of documentation just fit very well with the sentiment expressed in that quote? If we are to let Microsoft handle updating and not pick and choose the patches ourselves, do we even need patch notes?
Whether that omission was a mistake or a deliberate decision, of course, is yet to be seen, but it can safely be said that ever since the dawn of the Windows 10 era, Microsoft has been seen many times engaging in behavior that can only be described as testing the limits, finding out what Windows users will tolerate and what they will not.
Interesting times we live in– unfortunately.
Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon 6.2
XPG Xenia 15, i7-9750H/32GB & GTX1660ti, Kubuntu 24.04
Acer Swift Go 14, i5-1335U/16GB, Kubuntu 24.04 (and Win 11)
Whether that omission was a mistake or a deliberate decision, of course, is yet to be seen, but it can safely be said that ever since the dawn of the Windows 10 era, Microsoft has been seen many times engaging in behavior that can only be described as testing the limits, finding out what Windows users will tolerate and what they will not. Interesting times we live in– unfortunately.
That is also the famous (infamous?) Chinese curse: “May you live in interesting times.”
Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...
It could be argued that Microsoft isn’t testing the limits of what Windows users will tolerate but that it is continually setting new limits. Unfortunately, the painful reality is that Microsoft has no limits when it comes to forcing its own agenda on users and disingenuously minimizing the fallout from policies and procedures that have turned Windows Update into a malware delivery channel.
Forgive me for being very petty (since I’m still on Windows 8.1 & any Win 10 updates are irrelevant to me)… but I Love your New Logo for these posts! The 4 Windows colors in the shield… & the band-aid caps it off. Plus your title… “Susan Bradley — Patch Lady”. If you don’t have business cards like this… you Should! You & the main MVP’s should get “00” designations, like a certain agent does in the movies. Agent “001”… “Bradley… Susan Bradley. I’m the Patch Lady.”
Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...
“That last one was not in the original KB release.”
That is true indeed. Here is an older version of that article: http://webcache.googleusercontent.com/search?q=cache:https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4090913%2Fmarch5-2018kb4090913osbuild16299-251.
Sitemap https://support.microsoft.com/sitemap_en-us_help_81 (one of the many sitemaps used by the KBNew-generating macros) currently lists the “lastmod” date for KB4090913 as 2018-03-05, but the “Last Updated” date on https://support.microsoft.com/en-us/help/4090913/march5-2018kb4090913osbuild16299-251 is “Mar 6, 2018.”
Love the logo…. and the good info!
Non-techy Win 10 Pro and Linux Mint experimenter
Hi Seff,
Broken for me also.
are you referring to the portions where PL pasted in the KB release notes? MS has the same format in the KB article so that’s why it looks that way
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Notifications
