Troubleshooting Windows 11 KB5063878 Installation Issues
The recent Windows 11 update, KB5063878, has been linked to installation failures caused by error code 0x80240069. This particular issue predominantly affects users who deploy updates through Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM).Other related errors, such as 0x80240031 and 0x800f0922, also hinder users from completing the August 2025 Update installation.
Originally released on August 12 as an essential security update, Windows 11 KB5063878 is designed to download and install automatically. Users may face installation failures through WSUS, typically indicated by the error code 0x80240069.
Understanding the Error 0x80240069
This error is not entirely new, having first been highlighted by Windows Latest on April 30. Although Microsoft released a patch to address this earlier, it seems the glitch has resurfaced in the August 2025 Update. Users on various platforms have reported persistent failures with KB5063878, particularly in environments utilizing WSUS and SCCM.
Upon examining Event Viewer, technicians may observe logs delineating the installation failure. Notably, the error entry will specify:
- Faulting app: svchost.exe_wuauserv
- Faulting module: ntdll.dll (version 10.0.26100.4652)
- Exception code: 0xc0000005
- Service termination appears frequently in the logs.
One system administrator managing approximately 100 PCs reported that while updates from June and July succeeded, the August update consistently fails to install via both MECM and WSUS.
How to Resolve Error 0x80240069
If you’re encountering installation issues with KB5063878 using WSUS, you may modify the Windows Registry to potentially resolve the error. Here’s how:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3000950414]
“EnabledState”=dword:00000001 “EnabledStateOptions”=dword:00000000 “Variant”=dword:00000000 “VariantPayload”=dword:00000000
Save the above code as a.reg file. To apply it, right-click the saved file and select ‘merge, ’ allowing changes to the registry.
Restart your system afterward to ensure the modifications take effect. Following that, the 0x80240069 error should be resolved for WSUS or SCCM deployments. You can also rerun a sync by executing gpupdate /force and checking Windows Update or the Software Center again.
For administrators managing multiple devices, a PowerShell script can be used to make similar registry changes across all computers:
New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8"-Name "3000950414"-Force | Out-Null New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3000950414"-Name "EnabledState"-PropertyType DWord -Value 1 -Force | Out-Null New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3000950414"-Name "EnabledStateOptions"-PropertyType DWord -Value 0 -Force | Out-Null New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3000950414"-Name "Variant"-PropertyType DWord -Value 0 -Force | Out-Null New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\8\3000950414"-Name "VariantPayload"-PropertyType DWord -Value 0 -Force | Out-Null
This script overrides problematic features introduced with the latest update. Setting the DWORD values to zero signals Windows to disregard certain logic checks, allowing the Windows Update service to operate correctly.
While Microsoft has yet to provide extensive documentation about these WSUS-related problems, previous insights from support staff suggest that the registry modifications could alleviate the 0x80240069 error.
Additional Workarounds and General Issues
If you’re unsure about making registry changes, consider awaiting an official resolution from Microsoft. An alternative method is to manually download and install KB5063878 from the Microsoft Update Catalog.
Users have also reported experiencing other installation glitches, such as the update reaching 100% completion before displaying a message stating, “something went wrong, reversing changes.” Others faced download stall issues, where progress halted at around 4% or 6% for extended periods.
Microsoft’s Confirmation of Ongoing Issues
Microsoft has acknowledged these complications in its official support documentation. Users may see a misleading Event ID 57 regarding the initialization failure of the Microsoft Pluton Cryptographic Provider following recent updates, including KB5063878. While this represents another known problem, it can be safely disregarded.
As Microsoft works on a comprehensive solution for these ongoing issues, staying updated through their official channels is recommended.
Leave a Reply