In addition to the second cumulative update for 1803 this month, we have another Servicing Stack update

Topic

New Reply

Susan’s post below talks about the KB 4284848 second June cumulative update for Win10 1803. There’s also a “critical” Servicing Stack update for 1803,
[See the full post at: In addition to the second cumulative update for 1803 this month, we have another Servicing Stack update]

1 user thanked author for this post.

Elly

Reply | Quote

Replies

Enterprise version only?

Reply | Quote

No.  When you get your updates via MU these servicing stack updates are automatic and silent (in the background, not even shown to you in the history)

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

GreatAndPowerfulTech

Reply | Quote

It’s a bit annoying actually. 4284848 shows up in ConfigMgr and the support article promises all goodies of fixes to current issues. But being a dynamic update means I have to do everything manually to test it “as a preview”. See the last 2 paragraphs of:
https://blogs.technet.microsoft.com/mniehaus/2017/09/30/using-dynamic-update-with-wsus-to-install-windows-10-feature-updates/

Reply | Quote

I see the 1803 upgrade like this:
Imagine  you are about to ride an aerostatic Globe called “Windows 1709/1703” (pick your favorite)  and the staff that manages the Globes are telling you to change to “Windows 1803” however with each passing moment you see them patching holes after holes that appear in the globe in an amazing frecuency  so, the question is, would you ride such unreliable globe?  or you would wait for it to become stable enough?

Just someone who don't want Windows to mess with its computer.

Reply | Quote

It was laughable when Microsoft said 1803 was ready for enterprise. Even the best of OS upgrades requires at least six months to work through bugs and driver updates. There is always some unexpected issues even when the best intentions are to have a stable release. Just never understood why Microsoft would risk its reputation with enterprise by branding 1803 as good to go so early?

Reply | Quote

Microsoft risk its reputation? What reputation! Ha!

Even if complaints are voiced, it’s just noise to Nadella & Co., and nothing will happen. Enterprises are so entrenched with Microsoft products (Windows, Office, and Exchange, just to name a few) that they simply cannot jump ship without investing nearly countless hours of manpower and untold amounts of money to rewrite applications for a new platform.

Consider how difficult it is for Joe Blow to switch to something like Linux, macOS, or ChromeOS? Not only is there the learning curve (which differs dramatically according to the person), but we’re talking about an investment of new apps, a loss of other apps, and a completely new workflow. Now multiply that times hundreds or thousands of users, add to it the inherent complexity that comes with large computing environments, and wrap it up with the general unwillingness from management to spend money on anything related to IT (until something catastrophic happens, of course).

Honestly, I think Microsoft understands this and I believe it’s one reason why they’ve thrown so much caution into the wind. Enterprises will balk and squawk until Lotus Notes doesn’t run, but they simply cannot leave the torture chamber without a Herculean effort.

Edit for content

Reply | Quote

May I request that posts describing such a patch include the Windows 10 “build” number that is supposed to be the result.

It would be a lot less difficult to check a system to see whether it already has it.

Thanks.

FYI, I just installed it. My test system went to: Version 1803 (OS Build 17134.137)

-Noel

Reply | Quote

There was no build number change for the Servicing Stack update referenced in this topic.

I would be curious to know however, was your installation of the Cumulative Update manual or via WU?  Also, which edition (Enterprise, Pro, etc.)?

Reply | Quote

I just picked the latest cumulative update for Win 10 x64 from the catalog, KB4284848, and voila: 17134.137 from 17134.112.

-Noel

Reply | Quote

Did you by any chance also choose the Servicing Stack Update from the catalog and install it?  If so, did you install before or after the Cumulative Update?  Which edition are you using (Enterprise, Pro, etc.)?

Reply | Quote

It doesn’t matter which Edition you are using (Home, Pro, Enterprise). You need to download the Servicing Stack if it’s available and install it before the CU. The SSU is the update for the Windows Update mechanism.

Reply | Quote

Thank you.  I see now that Microsoft updated the SSU KB article on June 27th to include all editions of 1803 not just Enterprise per their original post on June 26th.  Google cache still shows the original post.

Reply | Quote

Need?

Ugh, now I’m a bit concerned that I have not applied the right updates in the right order. I did not apply the Servicing Stack update.

I guess I was still under the naive impression that “cumulative” in the catalog means that you get everything you need. My bad I guess for thinking Microsoft uses English.

Sigh. Now I’m imagining / anticipating I’ll be getting into another condition another condition where my VM becomes unserviceable and I’ll have to revert it to an older snapshot again…

Microsoft is surely not making this straightforward.

-Noel

Reply | Quote

I agree that Microsoft’s guidance on this is confusing.  For example, it it were truly a “need” to manually install the SSU before the CU wouldn’t that suggest a prerequisite?  Instead their KB article guidance for the CU is that “[w]hen installing both the servicing stack update (SSU) KB4338853 and the latest cumulative update (LCU) from the Microsoft Update Catalog, install the SSU before installing the LCU.”  One could read that as you only “need” to do it that way when installing both.  What if I decide not to install both?  Do I just ignore the guidance?  Why not come right out and say that in order to apply the CU properly, you must first install the SSU?  Sheesh!

Anyway, there were several times on 1709 where I manually installed CU’s without the SSU and don’t recall any issues.  However, since moving to 1803, I have heeded PKCano’s wise advise to “just use WU” and leave the catalog for the pro’s.

Reply | Quote

“Susan’s post below…”

“I’m not seeing Susan’s post below.  Short-circuit?

 

Edited for HTML. Please use text tab for copy/paste.

Reply | Quote

“Susan’s post below” it Susan’s topic directly below this thread on the main blog page.

1 user thanked author for this post.

Elly

Reply | Quote

You don’t need to separately install the SSU prior to installing the CU if you are using version 1803 and “searching for updates” or simply getting the CU when Microsoft sends it through WU. The SSU will be installed automatically before the CU installs as part of the whole install (i.e. included first).  That’s why, for most 1803 users, it’s best to either wait for Microsoft to do it for you automatically, or if you must, click on “search for updates” on the Windows Update page in Settings.

 

Reply | Quote

The reference was to manual installation using downloads from the MS Catalog. In that case the SSU should be installed first manually before the CU.

Reply | Quote

Neither one shows up in my Windows Update… Strange.

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote

Do you have your settings at Semi Annual Channel? If you set it for SAC (Targeted) you will probably see those patches (SSU and CU). The non-security ones released later in the month are like the “Previews” for Win7/8.1. The ones on Patch Tues are SAC.

1 user thanked author for this post.

radosuaf

Reply | Quote

OK, so I guess that’s the case. I have set Semi Annual Channel.

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote