[English]I have come across user reports in my German blog that the August 2025 update KB5063878 may cause issues during installation and fails. The update cannot be installed in Windows 11 24H2 and aborts with error code 0x80240069. Direct install on WSUS seems to work for some people. However, there may be a workaround.
Advertising
Windows 11 24H2: Update KB5063878 fails
Cumulative Update KB5063878 includes quality improvements and security patches. I mentioned the update in the blog post Patchday: Windows 10/11 Updates (August 12, 2025).
Several users commented on my German blog post, and reporting that the update installation aborted with error code 0x80240069 after downloading only a few percent. Blog reader Sebastian writes in this German comment that he gets a download error 0x80240069 for both updates KB5063878 (Windows 11 24H2) and KB890830 (Malicious Software Removal Tool).
In the German blog post Patchday: Windows 10/11 Updates (12. August 2025), other readers reported receiving this installation error with Windows Update, all with WSUS.
Brief error analysis
Sebastian then inspected the event log and found the following text under ID 7031:
ID 7031
The Windows Update service has unexpectedly stopped. This has happened once before. The following corrective measures will be taken in 60000 milliseconds: Restart the service.ID2
The following error occurred when starting the WindowsUpdate_trace_log session: 0xC0000035.
The (Windows 11) error code 0xC0000035 is triggered by a kernel event tracing event and stands for "STATUS_OBJECT_NAME_NOT_FOUND". In connection with update installation, this could indicate that the registry entries for an event tracing session could not be found.
Advertising
A possible workaround
On reddit.com, there is a thread titled Deploying Windows 11 23H2 Enablement package crashes svchost.exe_wuauserv – all endpoints. In his comment here, Olaf Koehler refers to the solution mentioned by user Despairz936, which was named by Microsoft in April 2025 as a workaround ("Here is the workaround proposed by Microsoft following the opening of a ticket for the same problem/error code.") for the error. The following registry entries must be set.
Auf reddit.com gibt es den Thread . Olaf Koehler weist in seinem Kommentar hier auf die von Benutzer Despairz936 genannte Lösung hin, die von Microsoft im April 2025 als Workaround ("Here is the workaround proposed by Microsoft following the opening of a ticket for the same problem/ error code.") für den Fehler genannt wurde. Es müssen folgende Registrierungseinträge gesetzt werden.
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"
Einfach die obigen Registrierungseinträge per Editor in eine Reg-Datei speichern. Dann regedit.exe über Als Administrator ausführen mit administrativen Berechtigungen starten und die .reg-Datei über das Menü Datei und den Befehl Importieren in die Registrierung importieren lassen. Im Anschluss einen Neustart des Systems ausführen.
After that, the update should be downloaded and installed. There is also a note in the comments on the blog that manual download and installation works. Maybe that will help. It worked for Olaf, anyway (thanks to the reader for the tip).
Similar articles:
Microsoft Security Update Summary (August 12, 2025)
Patchday: Windows 10/11 Updates (August 12, 2025)
Patchday: Windows Server Updates (August 12, 2025)
Patchday: Microsoft Office Updates (August 12, 2025)
Advertising
Receiving this error on all test W11 24H2 that use SCCM + WSUS for updates. Surprisingly, Intune-managed machines seem to be installing that update just fine. Go figure. I am not usually one for conspiracy theories, but thats just suspicious.