We started upgrading our Windows 11 computers to 24H2 in November. After the upgrade I noticed a high number of failures when applying the November 24H2 cumulative. Here we are in Dec and we’re still seeing a high number of update failures with the Dec 24H2 cumulative. Is anyone else experiencing issues with the 24H2 cumulative updates after the upgrade?
I tried to manually install on a few of the computers that were failing and it errors out with the error "Windows Update Standalone Installer: installer encountered an error 0x800f0838. I tried a number of fixes typically used to cleanup the windows update directory, DISM, etc. Nothing would work.
I then noticed if you try to download the latest DEC Cumulative from the Microsoft Update Catalog website there are two updates listed there. The first is a September 24H2 update KB5043080 and the DEC 24H2 Cumulative KB5048667. I found that if you install KB5043080 which is the September 24H2 cumulative you can then install the DEC 24H2 cumulative without error.
You would think that September 24H2 cumulative would be included in the 24H2 iso I downloaded from Microsoft in October after they officially released 24H2. I noticed KB5043080 is not in the BigFix console. Should that be added or possibly bundled with the Dec 24 Cumulative?
@cody_gregg We have noticed the same issue. It is very strange that Microsoft lists them together in the update catalog instead of making the KB truly cumulative. We are unable to find any mention from the MS side about this issue.
I’m relieved to see I’m not the only one encountering this. There isn’t much information available online about it either. I ended up creating a custom task in BigFix to deploy KB5043080 from September since no fixlet exists for it in BES. I just finished testing the deployment on a few computers at my desk, and they updated successfully. After pushing it out, the December updates installed without any issues. I’m now preparing to pilot this with our beta group.
I figured there would be more people complaining at this point. It could be that a lot of other companies have yet to deploy the 24H2 upgrade is my guess.
Here’s a possible explanation: “Checkpoint cumulative updates”, a new feature that comes with Win11 24H2. It is meant to reduce the size of monthly updates.
There is another issue that apparently causes issues with 24h2 clients updating. If they were installed with 24h2 install media from Oct or Nov there is apparently a know issue that theybare investigating a solution for.
When using media to install Windows 11, version 24H2, the device might remain in a state where it cannot accept further Windows security updates. This occurs only when the media is created to include the October 2024, or November 2024, security updates as part of the installation (these updates were released between October 8, 2024 and November 12, 2024).
Please note, this only occurs when utilizing media - such as CD and USB flash drives - to install Windows 11, version 24H2. This issue does not occur for devices where the October 2024 security update or the November 2024 security updates are installed via Windows Update or the Microsoft Update Catalog website.
Workaround: To prevent issues, do not install Windows 11, version 24H2 which installs the October 2024 or November 2024 security updates. Instead, ensure that media used to install Windows 11, version 24H2, includes the December 2024 monthly security update (released December 10, 2024), or later.
Next steps: We are working on a resolution and will provide more information when it is available.
I have worked with MS support for this case for these two months about Win11 24H2 and found that “WUSA” command (or double click *.msu) isn’t worked for checkpoint cumulative update. Only DISM command is worked for CCU now.
If you put all related CU/SU including previous checkpoint packages in same folder, running DISM to install the latest CU/SU, it would automatically to install previous checkpoint from same folder, no KB and no article mentioned it, MS suggested!
Unfortunately, BigFix fixlet is now only using WUSA for deployment. I will ask BigFix support later
Looks like HCL has provided a fix on the patch forum, article number 50557 “Content Release: Patches for Windows published 2024-12-24” posted on 12/24. I am unable to link to the article in this post.
Hello, thank you for the fix. However, when installing a clean install or upgrade install of Win11 24H2 using the latest RTM ISO, this will turn out as UBR 1742. It will still require KB5043080 to be patchable with any later cumulative update.
504308003 is defining UBR < 1742 as relevance criterion. Hence, I believe this leads us into a patching deadlock again. Could you please verify if that’s the case and how to solve it?
Hi @Mike_X, this issue is acknowledged. I’ve raised an internal issue to get this matter addressed. In the meantime, please validate that your Win11 endpoint has an OS build of 26100.1742 at a minimum before attempting to deploy the current January 14th 2025 cumulative update:
Fixlet # 505000903 - MS25-JAN: Cumulative Update for Windows 11 Version 24H2 - Windows 11 Version 24H2 - KB5050009 (x64)
You would first need to deploy the following fixlet if it is applicable which will get the OS build to 26100.1742:
Fixlet # 504308003 - 5043080: Cumulative Update for Windows 11 Version 24H2 - Windows 11 Version 24H2 - KB5043080 (x64)
Is this fixlet below you’re referring to supposed to be in the BigFix console under fixlets and tasks? If so for some reason I do not see it anywhere in my console when searching 504308003. I had to actually download the KB from Microsoft’s Update catalog and manually setup a task to deploy it. Just wanted to make sure I am not missing something. If this is supposed to be in the console, I am now curious why it’s not showing in my console.
“Fixlet # `504308003 - 5043080: Cumulative Update for Windows 11 Version 24H2 - Windows 11 Version 24H2 - KB5043080 (x64)”
It’s in my console. Check that ‘Show Hidden Content’ and "Show Non-Relevant Content’ are selected. Since we’re troubleshooting a false-negative, perhaps none of your endpoints are relevant.
It’s in Patches for Windows, version 4482 (or perhaps a bit earlier, but that’s the version I’ve gathered)
The KB number is “5043080”, the “03” at the end refers to our specific Fixlet ID instance (we append a number based on the targeted OS for each particular fixlet, we would have several fixlets for 5043080)
In your console, you’re not showing the “ID” field. You can right-click in the column headers and add the ‘ID’ field for this one to show up in your search, or else just search on 5043080 instead of 504308003
Fixlet # `505000903 - MS25-JAN: Cumulative Update for Windows 11 Version 24H2 - Windows 11 Version 24H2 - KB5050009 (x64)’ is not relevant for me because the UBR is not < 1742 as mentioned earlier. I did not see a solution in this situation.
Here is what worked for me. Can we get a fixlet published?
Fix for Windows 11 24H2 Update Error 0x800f0838 When Using Local Source for Feature On Demand or Language Pack
I encountered the Windows update error 0x800f0838 on Windows 11 24H2 when attempting to install updates with a Feature On Demand or language pack installed via a local source (no WSUS or Windows Update access). After a lot of troubleshooting, I found a solution and wanted to share it here in case it helps someone else.
The issue is documented in this Microsoft article:
For me, double-clicking the .msu file or using DISM didn’t work, so here’s the process I followed to resolve the issue:
Download the update package mentioned in the KB (as of now, the September 2024 KB5043080) and the update you want to install (e.g., January 2024 KB5050009).
Place only these two updates in the same folder.
Open a command prompt or PowerShell session as Administrator.
Navigate to the folder containing the updates using the cd command.
Run the following command to install the update: Add-WindowsPackage -Online -PackagePath "C:\Packages\windows11.0-kb5050009-x64_97aac2ab4f607b11d50ad2fd88a5841ee0b18dd5.msu"
This resolved the issue for me after spending an entire day troubleshooting why updates wouldn’t install on my Windows 11 24H2 systems. Hopefully, this saves someone else time!
Hi @mbartosh, your request is acknowledged. I’m currently working internally to get this issue resolved. Furthermore this is applicable to Win11 24H2 and Win2025 where we’ll need to use the checkpoint cumulative update along with the latest cumulative update. More details to follow when these fixlets are modified. -Gus
Have you seen a new fixlet? I saw there was an announcement for an updated fixlet for Windows 11 cumulative update, but I am not seeing it in my console.
i have not seen it. I was able to caveman automate this by mass copying with a .bat file using robocopy so both those msu files were in the same folder on each client. i pushed a custom action to those hostnames, just the powershell command - "Add-WindowsPackage -Online -PackagePath “C:\Packages\windows11.0-kb5050009-x64_97aac2ab4f607b11d50ad2fd88a5841ee0b18dd5.msu” Then scheduled a reboot. when they rebooted, the build number changed and verified the janurary update installed. gotta love microsoft …
