KIR to Fix WSUS Installation Failed with Error 0x80240069 Caused by Windows 11 24H2 KB5063878 Cumulative Update

Why Did Microsoft 11 Latest KB5063878 Cumulative Update Crash WSUS and How Can You Fix It?

A recent security update for Windows 11, version 24H2, is causing significant problems for businesses and organizations. The update, identified as KB5063878 and released on August 12, 2025, fails to install on computers managed through Windows Server Update Services (WSUS), showing the error code 0x80240069. This issue disrupts the normal patching process for many IT administrators.

Microsoft officially acknowledged the problem on August 13, 2025, and has provided a temporary solution to help organizations get their systems updated and secured.

Understanding the Installation Failure

The cumulative update KB5063878 is designed to deliver important security patches and quality improvements to Windows 11, version 24H2. While the update works correctly for home users who download it directly from Windows Update, it creates an issue for enterprise environments.

Who is affected?

The installation failure specifically targets devices that receive updates through WSUS or other management tools like Microsoft Configuration Manager (SCCM/MECM) that rely on WSUS. This means IT administrators managing networks of computers are the primary group experiencing this problem. Home users are not likely to encounter this error.

What is WSUS?

Windows Server Update Services (WSUS) is a tool that allows organizations to manage the distribution of updates to computers on their network. It gives administrators control over which updates are installed and when, which is crucial for maintaining system stability in a business setting.

The Error Code

When the installation fails, it generates error code 0x80240069. This signals that the update process was halted. Some system administrators have also noted that the Windows Update service (wuauserv) on the affected machines crashes or terminates unexpectedly during the update attempt. While Microsoft has officially confirmed the issue for Windows 11 24H2, some users have reported the same error on Windows Server 2025.

The Official Solution: Known Issue Rollback (KIR)

To address this problem without requiring a full uninstallation of the security patch, Microsoft has activated a Known Issue Rollback (KIR). A KIR functions like a precise switch, allowing Microsoft to disable the specific part of the update that is causing the error while keeping the essential security fixes active.

For IT administrators, resolving this issue involves downloading and implementing a special Group Policy provided by Microsoft. This policy contains the KIR instructions that correct the update behavior on managed devices.

Steps to Apply the KIR Fix:

Step 1: Download the Group Policy

Administrators need to download the MSI file for the KIR. The correct file is named “Windows 11 24H2 and Windows Server 2025 KB5063878 250814_00551 Known Issue Rollback”.

Step 2: Install and Configure

Once downloaded, install the MSI on a machine with Group Policy management tools. This adds the new policy template.

Step 3: Apply the Policy

The new policy can be found in the Group Policy editor under Computer Configuration > Administrative Templates. Locate the policy named after the KIR and configure it as instructed.

Step 4: Deploy

Link the configured Group Policy Object (GPO) to the organizational units (OUs) containing the affected Windows 11 devices. A device restart may be necessary for the policy to take effect and for the update to install correctly.

Alternative Methods and Considerations

While the KIR is Microsoft’s recommended approach, some system administrators have found other workarounds. One popular alternative involves manually importing the update into WSUS and declining the version that is synchronized automatically. This method reportedly allows the update to install without errors and avoids the need for a client-side Group Policy change or reboot.

Another, more technical, workaround involves making direct changes to the Windows Registry to bypass the problematic logic in the update. While effective, this method is riskier and should only be performed by experienced administrators who are comfortable editing the registry, as mistakes can cause system instability.

Microsoft has stated it is working on a permanent fix that will be included in a future Windows update. Once that update is released, the KIR and other temporary workarounds will no longer be necessary.

Has This Happened Before?

Yes, this same problem happened before in April 2025. Microsoft fixed it then with the same KIR method. But somehow the problem came back with this new update. This shows that even big companies like Microsoft can make mistakes. The good news is they have tools like KIR to fix problems quickly.

Who Does This Problem Hurt?

This problem mainly hurts companies and businesses that manage many computers. Home users who have just one computer probably will not see this error.

People affected:

• Office workers with company computers
• Schools with many student computers
• Hospitals with medical computers
• Government workers with official computers

People not affected:

• Home users with personal computers
• People who get updates directly from Microsoft

Why Should You Care About This?

Even if this problem does not hurt your home computer, it shows how computer updates can break things. It also shows that Microsoft has ways to fix problems quickly without making you wait weeks for a new update.

If you work at a company, your computer helper might need to apply this fix. You might need to restart your computer once they install the fix.

The most important thing to remember is that getting safety updates is still very important. Even when updates cause problems, the safety fixes protect your computer from bad people trying to hurt it.

Microsoft says they are working on a permanent fix that will come in a future update. Once that happens, companies will not need to use this temporary KIR fix anymore.