|
Patch reliability is unclear, but widespread attacks make patching prudent. Go ahead and patch, but watch out for potential problems. |
I’m trying to make the transition from Security Only to the monthly roll ups. I’m updating from June ’19 SO to the December ’19 cumulative roll up. I think I’m missing a critical Servicing Stack Update. I’m not getting any .NET maintenance offered – who knows what else is missing.
Looks like SSU KB4523206 was offered in November, but was not offered when I ran Windows Update > Check for Updates. Is this right? Comments?
PS. I’m going to use @abbodi86’s telemetry neutralization.
If your PC is up to date with Novemver SSU KB4524445, you shouldn’t need anything else.
KB4519976 is one of the requirements for applying for ESU from Microsoft. I can’t find the link right now, but somewhere here in the last month Susan Bradley has listed the requirements.
Found it – here are the requirements.
Yes, you are correct. KB4536952 is the 2020-01 Servicing Stack for Win7.
We are on DEFCON-2. Wait to install it until the DEFCON number is 3 or greater.
That’s because of a limitation in Win 7 updating mechanism
if SSU was deployed and installed with other updates, it will cause a boot hang
and they cannot possibly make all updates dependant on SSU and won’t show before it
moreover, SSU <=> Rollup prerequisite relationship is not explicit on the same month
meaning, December and January rollups (or security-only update) do not stricly require December and January SSUs
instead, they only need any previous SSU, starting KB4516655 (September) or later
I agree 100% & I’m also aware that SSU updates must be installed separately as stand alone updates.
However, MS guidance recommends SSUs before CLUs but WU implements SSUs after CLUs.
Couldn’t WU present only the latest SSU (if not already installed) first then after it’s installed, present the rest of that month’s updates? My understanding is that a system reboot is not required for an SSU. If a reboot was required under this scenario, WU could so indicate.
This SSU installation sequence would be in accordance with MS’s own guidance wouldn’t it?
In any event, I’m not advocating that MS needs to (or should) change their WU implementation concerning SSU updates, just trying to address the confusion concerning the various posts sprinkled about here & there within AskWoody about the correct sequence of installing SSUs vs CLUs and/or SOs.
As I’ve indicated here before, I’m a strong proponent of installing monthly CLUs and/or SOs first then after the reboot, installing the newly released latest SSU as this is the same exact sequence implemented by WU.
Now that this horse is really dead, dinner bell’s ringing 🙂
Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS
No it cannot, Win7 WU client is ancient and limited
like i said that require MS to make all January updates (including .NET) dependant on SSU, which is not feasible
the gudance is not necessary written by the same WU deployment guys 🙂
and it’s really ment for reading users and IT admins, regular simple users will just install whatever WU offer as important
evevtially, SSU will show up
generally, SSU should always be installed first, alone
@abbodi86 … again you’ve made my point.
MS guidance guys/gals say do SSUs first but WU guys/gals implemented SSUs last hence confusion.
Also, using WU … search for updates, hide all found updates, search for updates again, install found SSU update, unhide previously found updates (WU searches for updates again), install re-found updates. This is us forcing WU to follow MS published guidance.
Some of us here (reading users ? / IT admins ?) are following MS guidance by using this method while using WU if/when it is known that a new SSU was released that month.
Couldn’t MS simply change (if MS wanted or needed to) the update precedence logic meta-data to show SSU first if installing SSU first is the correct installation sequence? (again not saying MS should or needs to)
Though I don’t do it this way, many posts here say this not only works but this is the way to do it … always do SSU first because guidance says so.
Simple users let WU handle it simply and install updates in the order found … CLUs then SSUs. Several posts here say this also works & this is the proper way to do it.
Being an active Group B member, I download/install SO & IE11 updates from MS Catalog & after reboot, let WU find then install all other checked important/recommended MS updates (hiding the CLU of course), then finally another WU to find/install the SSU (if any) last.
Again, I’m only trying to point out why there’s so much confusion about what to do first and both of our 2nd paragraphs (which seem to be in total agreement) hit that proverbial nail squarely on its head. 🔨🔨🔨
Win7 - PRO & Ultimate, x64 & x86
Win8.1 - PRO, x64 & x86
Groups A, B & ABS
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.
