SCCM August 2025 CU update fails

[Sheridan]

I started to test the Aug 2025 CU for Windows 11 24H2 on our test collection - all have 24H2 and the last patch was July 2025

 

SCCM has failed on every one in the test collection with the error:

Failed to download update: 0x80240069 

 

This error was around during the April updates, but our systems have have April, May, June and July updates applied since then without error - anyone else tried deploying Aug 2025 yet?

[5tu]

Seems to be a WSUS issue.  Others are reporting the same here

[Sheridan]

Same error April - although we didn't see it then. The registry fix has worked on the test PC I tried.

 

Now to roll out the reg fix across 100s of desktop and laptops....

[Sheridan]

Correction  - the registry fix isn't working for us - on an identical test set of 10 it worked on 2 and the other 8 still show the 0X80240069 error

 

I guess we'll be skipping the Aug 2025 updates for a while to see if MS sort this out

Edited August 13, 2025 by Sheridan

[OLPTech]

 

Microsoft's official response:

The August 12, 2025 Windows security update for Windows 11, version 24H2 (KB5063878), might fail to install with error code 0x80240069 when installed via Windows Server Update Services (WSUS). WSUS allows Servers with the WSUS role to defer, selectively approve, and schedule updates for specific devices or groups across an organization.

Home users are unlikely to experience this issue, as WSUS is designed for use across business and enterprise environments.

Workaround: 

This issue is mitigated using Known Issue Rollback (KIR) for enterprise-managed devices managed by IT departments. IT administrators can resolve this issue by installing and configuring the special Group Policy listed below.

Group Policy downloads with Group Policy name:  

Download for Windows 11, version 24H2 -- Windows 11 24H2 and Windows Server 2025 KB5063878 250814_00551 Known Issue Rollback

The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name>. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.  

The August 2025 Windows security update can also be installed manually via Windows Update or the Microsoft Update Catalog.

Next Steps: We are working to include the resolution in a future Windows update. Once the update with the resolution is released, organizations will not need to install and configure this Group Policy to address this issue. We will provide more information when it becomes available.

Affected platforms:

Client: Windows 11, version 24H2

Server: None

This is the link: https://download.microsoft.com/download/162492da-0507-4f19-bcc5-add3e82467c4/Windows%2011%2024H2%20and%20Windows%20Server%202025%20KB5063878%20250814_00551%20Known%20Issue%20Rollback.msi

[Sheridan]

I think the KIR package is just the registry changes required anyway? Not sure but I've tested some more and the registry fix is working on a lot of them - so it may have been my initial test set were still having issues from the initial failed sccm deployment

[DavR]

2 hours ago, liamread2000 said:

Next Steps: We are working to include the resolution in a future Windows update. Once the update with the resolution is released, organizations will not need to install and configure this Group Policy to address this issue. We will provide more information when it becomes available.

 

I wonder if they'll re-release August CU with the fix, or if we'll have to wait until September?

 

I'm rebuilding workstations over the holiday, would be kinda nice if we had all updates installed before I sign off on the job.

[kennysarmy]

We are being affected here - roll out updates via WSUS

 

Interestingly Server updates also via WSUS are fine, it's just Win11.

 

Edited August 14, 2025 by kennysarmy

[Sheridan]

1 hour ago, DavR said:

 

I wonder if they'll re-release August CU with the fix, or if we'll have to wait until September?

 

I'm rebuilding workstations over the holiday, would be kinda nice if we had all updates installed before I sign off on the job.

If it follows the same issue in April they'll just fix it in a later CU - so Sept at the earliest I'm guessing

[kennysarmy]

I'm finding a few RETRY's and a reboots and it eventually starts to install.

 

 

[DavR]

1 hour ago, Sheridan said:

If it follows the same issue in April they'll just fix it in a later CU - so Sept at the earliest I'm guessing

 

I'll run with the registry fix for now, then. If I'm rebuilding my workstations, I want them fully patched for a clean start in September.

[Sheridan]

On 14/08/2025 at 13:39, kennysarmy said:

I'm finding a few RETRY's and a reboots and it eventually starts to install.

 

 

I'm seeing some weird results as well, I deployed the registry to a couple of groups and in one case it worked after three reboots and the other worked a day later without any intervention (and no reboots at all) and they're the same hardware and os level

 

I think I'll just deploy the Aug CU after the registry fix has been deployed network wide and see which ones fail

[OLPTech]

The August 2025 update has been re-released with the issues fixed, so the registry keys / GPO is no longer necessary. Just need the new update deployed out (its the exact same KB)

https://learn.microsoft.com/en-us/windows/release-health/resolved-issues-windows-11-24h2#3635msgdesc

[Sheridan]

Yup just seen this update has been replaced in SCCM so will test the deployment of this one instead!

[DavR]

Good news. Just in time to rollback the manual fix, before I do a wider rollout.