Error 0x800704C7 is Windows telling you, in its own terse way, that the update was cancelled. Not failed to download, not blocked by the server — cancelled, mid-operation, on your own machine. On Windows 11 24H2 this most often happens when a third-party antivirus terminates the installer, when an update service crashes partway through, or when the machine is shut down or put to sleep during a long install.
The tricky part is that the cancellation is usually silent. You see the update progress bar, walk away, and come back to the error — with no obvious sign of what pulled the plug. Because the cause is an interruption rather than corruption, the standard ‘clear the cache’ advice only helps if the interruption left the update state inconsistent. The real fix is finding and removing whatever keeps cancelling the operation.
The sequence below starts with the quick checks and moves to isolating the interfering software. Most 0x800704C7 cases are solved by Fix 3 or Fix 4. If the update instead completes but then rolls back at restart, see our walkthrough for undoing-changes loops in Windows 11 24H2 .
Why this happens
Third-party antivirus terminating the installer — Security suites with aggressive behavior monitoring sometimes kill the trusted installer process or quarantine update payloads mid-install, which Windows reports as a cancellation.
Windows Update services crashing — If wuauserv, BITS, or the cryptographic service dies during the install phase — often due to corrupted service state — the operation aborts with 0x800704C7.
Shutdown or sleep during installation — Closing the lid or forcing a power-off while the update is in its install phase cancels it. Laptops with aggressive sleep timers are especially prone to this.
Corrupted pending update state — A half-applied previous update leaves the servicing stack in a ‘reboot pending’ limbo. Every new update attempt detects the inconsistent state and cancels itself.
Conflicting background software — System utilities, driver updaters, and ‘PC cleaner’ tools that hook into system processes can interfere with the installer and trigger a cancellation.
Insufficient disk space at install time — The download fits, but the extraction and staging phase needs several extra gigabytes. If space runs out mid-install, the operation cancels rather than failing cleanly.
Corrupted user profile permissions — The installer runs with system privileges, but damaged ACLs on key folders can cause access-denied cancellations that surface as 0x800704C7.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Free up disk space before retrying
Rule out the simplest cancellation trigger first. The install phase needs breathing room beyond the download size — aim for at least 20 GB free on the system drive.
- Open Settings > System > Storage and check free space on C:.
- Run Storage Sense and Cleanup recommendations to clear temp files, old downloads, and the Recycle Bin.
- Move large personal files off the system drive if you are under 20 GB free.
- Retry the update from Settings > Windows Update.
Fix 2: Run the Windows Update troubleshooter
The troubleshooter resets the update service state and clears the cancelled-operation flags. It is a quick first pass before manual service work.
- Go to Settings > System > Troubleshoot > Other troubleshooters.
- Click Run next to Windows Update and apply any recommended fixes.
- Restart the laptop when it finishes.
- Check for updates again and let the previously cancelled update retry.
Fix 3: Perform a clean boot to isolate the interfering program
A clean boot starts Windows with only Microsoft services, which exposes whether third-party software is cancelling the install. This is the highest-yield diagnostic for 0x800704C7.
- Press Win + R, type
msconfig, and open the Services tab. - Check Hide all Microsoft services, then click Disable all.
- Open the Startup tab, click Open Task Manager, and disable all startup items.
- Restart, run Windows Update, and if it succeeds, re-enable services in halves to find the culprit — usually an antivirus or system utility.
Fix 4: Reset the Windows Update components
Crashed or corrupted update services are a direct cause of mid-install cancellations. Stopping them, clearing their state folders, and restarting gives you a known-good baseline.
- Open an elevated Command Prompt.
- Run
net stop wuauserv,net stop bits,net stop cryptsvc, andnet stop msiserver. - Rename the state folders:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldandren C:\Windows\System32\catroot2 catroot2.old. - Restart all four services with
net start, then check for updates. If the troubleshooter itself misbehaves, see our guide to fixing a broken Windows Update troubleshooter .
Fix 5: Temporarily remove third-party antivirus
If the clean boot pointed at your security suite, do not just disable it — fully uninstall it for the test. Many suites leave filter drivers active even when ‘disabled,’ and those drivers are what kill the installer.
- Open Settings > Apps > Installed apps and uninstall the third-party antivirus (Windows Defender activates automatically).
- Restart the laptop to clear any loaded filter drivers.
- Run Windows Update to completion.
- Reinstall your antivirus afterward if you prefer it — or stay with Defender, which never conflicts with updates.
Fix 6: Repair system files with SFC and DISM
A damaged servicing stack cancels installs unpredictably. These two tools repair the files the installer depends on.
- Open an elevated Command Prompt and run
sfc /scannow. - When it finishes, run
DISM /Online /Cleanup-Image /RestoreHealth. - Restart the laptop after both complete.
- Retry the update. Microsoft documents both utilities in the Windows support hub .
Fix 7: Install the update manually from the Microsoft Update Catalog
If the automatic installer keeps getting cancelled, the standalone installer often sails through — it runs as a single process with fewer moving parts for background software to interfere with.
- Find the failing KB number in Settings > Windows Update > Update history.
- Search for it on the Microsoft Update Catalog and download the x64 package.
- Close all programs, then run the .msu file and do not touch the laptop until it finishes.
- Restart when prompted and confirm the KB appears in update history.
Closing
Error 0x800704C7 is almost always something on your PC pulling the plug on the installer — usually security software or a crashed update service. Isolate it with a clean boot, reset the components, and the update will finally get the uninterrupted run it needs.
