Windows 11 version 25H2 update loop errors 0x8000ffff and 0x80073712

Ugnius Grincevičius 20 Reputation points
2026-08-02T17:32:13.2766667+00:00

Hi everyone,

I am running a new Windows 11 desktop rig (10-core CPU, RTX 5060 Ti, Phison 1TB SSD) which was first booted on July 29. Windows Update automatically started rolling out the Windows 11 version 25H2 feature update immediately.Ekrano kopija 2026-08-02 202420

However, due to a boot loop issue, I had to perform a System Restore from the recovery environment on July 31. Ever since that system rollback, Windows Update has been completely broken and stuck in an endless loop.

It attempts to install the 25H2 update, fails at restart, and then spends 40 minutes undoing changes. The main error codes showing up in my history are 0x8000ffff and 0x80073712.

To protect my SSD from constant wear and stop this endless loop, I have forcefully set the "wuauserv" service to "Disabled" in Services. My latest history log now shows error 0x8024001e (Task Cancelled), which confirms the update engine is successfully frozen for now.

Is anyone else experiencing this exact driver/registry component store conflict on version 25H2 after a system rollback? Are there any known manual driver cleanup steps that can fix this before the next Patch Tuesday? Attached is my update history screenshot.

Thanks for any advice!

Windows for home | Windows 11 | Windows update

Answer accepted by question author
Ramesh 181.1K Reputation points Volunteer Moderator
2026-08-03T05:45:23.9+00:00

And if the update still fails, re-enable the Windows Update service and do the following.

Launch Settings > System > Recovery. Under "Fix problems using Windows Update", select Reinstall now.

This does a repair installation, keeping your files, apps, and settings.


More info:

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Ramesh 181.1K Reputation points Volunteer Moderator
    2026-08-03T03:23:20.55+00:00

    Hi,

    What's the OS build number? Please run winver.exe to find that out. Post a screenshot of that dialog.

    Open Command Prompt (admin) and run:

    DISM /Online /Cleanup-Image /ScanHealth
    

    Post the output.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.