Install Servicing Stack Updates (SSU) Before Other Updates When User Initiated
The Current Branch 2002 release introduced a feature to install SSUs first but only when triggered by the deadline.
From the docs:
"SSUs are installed first only for non-user initiated installs. For instance, if a user initiates an installation for multiple updates from Software Center, the SSU might not be installed first."
A lot of work has been put into encouraging user-participation in the patching process. I want the user to decide when they're ready to install the updates and avoid situations where the deadlines impact their work. In those scenarios the behavior introduced in 2002 therefore not helpful.
I realize that if a user manually triggers the installs one-by-one that there's not much you can do about it. However, in pretty much every other scenario I would like to see the SSU install first.
User schedules the install from the update notification dialog.
User clicks 'Install All'.
User select multiple updates, including an SSU.
Updating status to Noted – see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each value.
Bryan Dam commented
@pilgi3: Right, for Windows 10 2004 and beyond though I believe they plan on back-porting to to all supported versions of Windows 10. Though that doesn't do squat for servers. Which I'd argue are the more serious/concerning use case here.
This is not necessary anymore.
Microsoft combines the SSU in the LCU right now.
A few month ago we created a ADR only with the SSU, which was installed hidden and silent in the background. The user has no impact and the update installs fast. So there will be no issues if a user install manually.
This would be useful for us, as well.