What's happening when you see 0x00000669?
You're installing a Windows update, probably a cumulative update on Windows 10 or 11. The progress bar hits 100%. Then you get a message like "The requested operation completed successfully. The exact error code is: 0x00000669." Or maybe you check the update history and see that code next to a failed-looking entry.
Here's the thing: this is not a real error. The code's name is ERROR_SUCCESS_REBOOT_INITIATED. It means the update installed fine, but a reboot was started or is pending. Windows Update just uses weird phrasing. It's like getting a trophy that says "You won, but here's a typo."
The trigger is almost always a cumulative or driver update that needs a restart to finish. You might have clicked "Restart now" or the system scheduled one for later. The error shows because the update engine reports success AND a pending reboot in the same status code, and the history logs it as a warning instead of a green checkmark.
Root cause in plain English
Windows Update tracks two things: did the installation work, and does the system need a restart? When both are true, it returns this combined code. The user-facing UI doesn't always handle it gracefully. So instead of showing "Update applied — restart your PC", it shows an error code. That's it.
It's not corruption. It's not a driver conflict. It's not a failed download. It's a status message that got dumped into the error bucket incorrectly.
How to fix 0x00000669
There's only one real step, but I'll break it down with what to expect. Don't waste time with SFC scans or DISM commands here — those are for actual failures.
- Restart your computer completely. Not shut down and turn back on — use the Start menu, click Power, then choose Restart. Wait until you see the login screen again. After restart, go to Settings > Windows Update > Update history. You should see the update listed with a green checkmark and "Successfully installed" instead of that error code. If you still see 0x00000669, move on.
- Check for a second pending restart. Sometimes multiple updates queue up. After the first restart, Windows might need another. Open Start, type "Check for updates", hit Enter. Click "Check for updates" again. If it finds anything, install it and restart again. Keep doing this until it says "You're up to date."
- Verify the update is actually installed. Open Settings > Update & Security (or Windows Update in Windows 11) > Update history. Look at the list. If the update that gave the error shows "Installed" or "Successfully installed", you're done. Windows just logged the code weirdly. The error history might still show 0x00000669, but that's a cosmetic display bug — not a real problem.
- Clear the pending reboot flag if it's stuck. Only do this if you've rebooted multiple times and the error still appears in update history. Open Registry Editor (press Win+R, type
regedit, hit Enter). Go toHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update. Look for a value named RebootRequired. If it exists and is set to 1, right-click it and delete it. Close Registry Editor. Reboot once more. Then check update history. This tells Windows "I've already restarted, stop waiting."
What to check if the error won't clear
If after all that you still see 0x00000669 in update history, check these three things:
- Is your system date and time correct? Go to Settings > Time & Language > Date & time. Turn off "Set time automatically," then turn it back on. Sync now. Wrong time can confuse update logging.
- Are there old pending updates in the queue? Open an admin Command Prompt (right-click Start > Windows Terminal (Admin) or Command Prompt (Admin)). Run
wuauclt.exe /updatenowand thenUsoClient.exe ScanInstallWait. This forces Windows Update to re-evaluate its queue and clear stale entries. - Do you have third-party antivirus? Some AV tools (especially McAfee, Norton, or Avast) block reboot triggers. Temporarily disable the AV, reboot, then re-enable it. Check update history again.
If the error code still shows after all that, the update itself might have a glitch. Check Microsoft's update KB page for known issues. But 99% of the time, it's just that first reboot that fixes everything. Don't overthink 0x00000669 — it's Windows yelling "I did it!" in a confusing way.