Windows Update Error 0x80070BC9 — Fix Guide

What Does This Error Mean?

Windows Update error 0x80070BC9 means the update cannot be applied because your PC is waiting on a restart that has not happened yet. A previous update or software installation left Windows in a state where it needs a reboot to finish. Until that reboot happens, no new updates can be installed on top of the pending changes. The fix is almost always as simple as restarting your computer and trying the update again.

Affected Models

Windows 10
Windows 11
Windows 8.1

Common Causes

A previous Windows Update was downloaded and partially applied but the required restart was postponed or dismissed
A software installation (such as a .NET Framework update or driver package) requires a reboot and has not completed
Windows is holding a pending file replacement operation that can only execute during the boot process
The Windows Update service has a stale lock from a previous interrupted update session
Group Policy or enterprise management software has queued a configuration change that requires a restart

How to Fix It

Restart your computer completely. Do not use Shut down and power back on — use Restart specifically. After the reboot, open Windows Update and try again.

A full Restart is different from Shut down on modern Windows. Shut down uses Fast Startup, which does not fully clear pending operations. Restart does a full reboot.
Run the Windows Update Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run.

The troubleshooter automatically detects and clears stuck update states, including pending restart flags and corrupted update caches.
Manually clear the Windows Update cache. Open Command Prompt as Administrator and run these commands one at a time: net stop wuauserv — then net stop bits — then del /f /q C:\Windows\SoftwareDistribution\Download\*.* — then net start wuauserv — then net start bits

The SoftwareDistribution folder holds downloaded update files. Clearing it forces Windows Update to re-download fresh copies, which clears any stuck states.
Check for any pending software installations outside of Windows Update. Open the Start menu and look for any programs showing an 'Install' or 'Setup requires restart' notification in the notification area.

Third-party software installers can set the same pending-restart flag that causes this error. Finishing those installations first clears the flag.
If the error persists, run: Dism /Online /Cleanup-Image /RestoreHealth in an Administrator Command Prompt, then restart again and retry Windows Update.

DISM repairs the Windows Update components themselves, which can get stuck or corrupted over time.

When to Call a Professional

If restarting multiple times and running the Update Troubleshooter do not resolve the error, a technician can check the Windows Update log files and registry for stuck pending-restart flags. This is particularly common in enterprise environments where Group Policy prevents automatic restarts.

Frequently Asked Questions

Why does Windows Update need restarts so often?

Many Windows components — especially core system files — are in use while Windows is running and cannot be replaced live. Windows schedules the replacement to happen at the next startup, before those files are loaded. This is why updates often say 'Preparing to configure Windows' during a restart. Until the restart clears those pending changes, new updates cannot be safely applied on top of them.

Is it safe to keep postponing the restart?

Postponing occasionally is fine, but leaving a restart pending for days or weeks causes problems. The longer the restart is delayed, the more updates pile up behind it. It can also leave your system partially patched, meaning security fixes are waiting but not yet active. As a rule of thumb, restart at least once a week if you use Postpone regularly.

Why does Shut down not count as a restart?

Modern Windows uses a feature called Fast Startup (or Hybrid Shutdown) when you click Shut down. Fast Startup saves the Windows kernel state to disk and restores it on the next power-on — making startup faster. But this means the system never fully restarted, so pending operations are not processed. Using the Restart option bypasses Fast Startup and does a true full reboot.