Consider the next Gedankenexperiment.
You flip to your Chromebook (or telephone or iPad), issues whirr and glurg for a short while, and the pc throws up this message:
Error. Failure to put in SSU earlier than LCU. Turn your laptop off and again on once more.
That’s what we’re seeing this week in Windows land. Except Windows isn’t well mannered sufficient to throw a message up. It simply throws up.
To perceive the issue, and its documentation, you want to resolve this Microsoftspeak:
SSU = a Servicing Stack Update = an replace to the a part of Windows that installs updates. As Microsoft says:
The “servicing stack” is the code that installs different working gadget updates. Additionally, it accommodates the “component-based servicing stack” (CBS), which is a key underlying part for a number of components of Windows deployment, equivalent to DISM, SFC, converting Windows options or roles, and repairing elements. The CBS is a small part that usually does now not have updates launched each and every month.
Servicing Stack Updates arrive every now and then. We were given one for Win10 model 1803, KB 4456655, on Patch Tuesday. The remaining Win7 Servicing Stack Update that I find out about seemed in September 2016 — two years in the past. It’s known as KB 3177467.
What’s the most recent Servicing Stack Update for your model of Windows? I dunno. If Microsoft has a checklist of the most recent, I’ve by no means noticed it.
LCU = Latest Cumulative Update. No, I don’t know why the documentation insists on the use of but any other three-letter acronym for one thing that’s simply spelled out. I assume they wanted one thing to stay SSU, CBS, DISM and SFC corporate.
What does this need to do with you? Ah, satisfied you requested.
The normal rule of thumb is that you simply must set up the most recent SSU earlier than you attempt to set up the LCU, er, the most recent Cumulative Update (or, in the case of Win7 and eight.1, the most recent Monthly Rollup). You may assume that the Windows installer could be sensible sufficient to replace itself before you install a new cumulative replace and, neatly, you’d be flawed.
It now seems as though this SSU-before-LCU rule is accountable for two of the confounding issues of updates this month.
Windows 7 Monthly Rollup, KB 4457144, fails with error 0x8000FFFF
I’ve noticed reviews from all over the place the sector that folks can’t set up the day prior to this’s Win7 Monthly Rollup as a result of they preserve hitting an error 0X8000FFFF.
An nameless poster on AskWoody says:
Feedback from Microsoft premier strengthen:
set up Servicing Stack Update KB3177467 (September 2016), restart laptop, set up KB4457144. KB3177467 ist pre-requisite for KB4457144
And it seems that as though that solves the issue. Yes, you must manually set up an difficult to understand two-year-old Servicing Stack Update earlier than you’ll be able to get this month’s Win7 Monthly Rollup to put in. (Nope, you don’t want to reboot after putting in KB 4457144.)
Error 0X8000FFFF positive sounds extra user-friendly than “manually install KB 4457144,” doesn’t it?
Win10 1803 Cumulative Update KB 4457128 installs two times, or on no account
I’ve additionally noticed reviews from all over the place the sector about an atypical habits with this month’s Win10 1803 Cumulative Update. Yep, that’s the most recent, latest and bestest model of Windows ever.
Günter Born describes the collection many of us see:
Cumulative replace (CU) KB4457128 calls for the former set up of the Servicing Stack Update (SSU) KB4456655 for Windows 10 Version 1803. This replace isn’t a part of KB4457128 this time. If the Servicing Stack Update (SSU) KB4456655 is lacking, remaining cumulative replace (LCU) KB4457128 can’t be put in. So KB4457128 is scheduled for putting in, however fails – with out an error, and Servicing Stack Update (SSU) KB4456655 is put in first. The KB4457128 is putting in once more – so customers can see two installs in Update History or Reliability Monitor.
SSU earlier than LCU except for after C or when it feels like a … oh, by no means thoughts.
Why must you must trouble with this? I dunno. Why can’t Windows replace itself as easily as ChromeOS? Or macOS or iOS or Android? I dunno. Why do you’ve gotten to concentrate on the Windows installer’s burps — why doesn’t Windows simply repair itself and get on with the industry to hand? It will have to be a laborious laptop science drawback.
I name it WaaTOR = Windows as a Tired Old Relic. We’re seeing a lot of that in recent times.
Thx @Pradeep_Dixit, @PKCano
Join us for a candlelight vigil at the AskWoody Lounge.