hey patchmanagement peeps,
I believe this one found in Azure Stack HCI 23H2 update history (and other Windows Update history pages) can transferred to other OS and releases that integrate their SSU with CU (thanfully), including:
- Windows 10 22H2
- Windows 11 22H2 and later
- Windows Server 2019 / 2022
- Windows Server 2022 Azure Edition
- Azure Stack HCI 22H2 or later
edit: Gosh, this isn't even new but personally never noticed this remark as I rarely scroll down after the "Known Issues" table and even not past "How to get this update" note.
Maybe it should be placed above the "Known issues" table.
Note from Microsoft
If you want to remove the LCU
To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages.
Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.source:
Caveats
The difficulty I see is the following: what will "tools" do, like
- Microsoft ConfigMgr
- Windows Update Services (WSUS)
- Settings App > Updates > Update History > Uninstall Updates
- legacy Control Panel in Windows > Programs and Features > Installed Updates
- WAC (if at all?)
- Windows RE (Recovery Enviromment), only available to uninstall updates in WinRE for
- Windows 10 21H2 or later
- Windows 11
- Windows Server 2022 or later
They could be using WUSA. Plus you will find WUSA as a recommendation in pretty much every "ask Dr. Google / GPT" how to uninstall Windows Updates, and of course our own muscle memory. Tricky.
That muscle memory
And mea culpa, until today I was rarely, but still using wusa just because its faster syntax compared to PShell or even dism.
On a sidenote
PShell should invoke Dism, e.g. Repair-WindowsImage, which is used very often, but unfortunately more frequently found as a dism command (dism /online /cleanup-image /scanhealth or /restorehealth), is much more complex in the syntax than the PowerShell commandlets.
#patchmanagement
