Hi @mbartosh & @anon81385762, I am pleased to inform you that we have developed three fixlets for KB5050009 which are currently undergoing active testing. These fixlets have shown successful results in our lab, and we are optimistic that after thorough QA, they will be available to all customers.
If you are interested in validating and testing these fixlets, please let me know.
-Gus
Hi Gus, I am willing to test it for you.
Hi @mbartosh, I sent you a private message.
Thank you, Gus.
I did get an exit code 87 on one of the updates. I have not seen that one before.
Error 87 is a standard error message from Windows Installer. The actual message string is ERROR_INVALID_PARAMETER. This simply means that an invalid parameter was passed to the installer. This can happen if an unknown parameter ( AKA command line argument) is passed to the installer.Apr 9, 2021
The updated fixlet still didn’t release until now? I need to install CCU on 24H2 manually for these two months…
Hi @Edward, starting with February 11, 2025—KB5051987 (OS Build 26100.3194), the content team has released the checkpoint cumulative update combined with the latest cumulative update and deploying this update with Deployment Image Servicing and Management (DISM.exe). For more details, please review the following fixlets:
Fixlet ID | Fixlet Name |
---|---|
505198701 | MS25-FEB: Cumulative Update for Windows 11 Version 24H2 for ARM64 - Windows 11 Version 24H2 - KB5051987 (arm64) |
505198703 | MS25-FEB: Cumulative Update for Windows 11 Version 24H2 - Windows 11 Version 24H2 - KB5051987 (x64) |
505198705 | MS25-FEB: Cumulative Update for Microsoft server operating system version 24H2 - Windows Server 2025 - KB5051987 (x64) |
Thanks, Gus.
I recently stood up 3 Windows 2025 Servers. Two with desktop and one as Core.
I’ve been trying to patch the Core server up to date with December and January cumulative and it always fails.
I took inspiration from the February Cumulative, and added the second prefetch, etc… Still failed.
With the new February fixlet though, it went through fine the first time.
I have 1 2022 server that is also Core and has been failing for months. I’ll give this method a try over there and see if it resolve it as well.