Fix ERROR_PATCH_NO_SEQUENCE (0x00000670) in Windows Updates

What's Actually Happening Here

Error 0x00000670 (ERROR_PATCH_NO_SEQUENCE) shows up when Windows Update downloads a batch of patches but can't figure out which one to install first. Think of it like a pile of puzzle pieces that were dumped on the table — Windows knows all the pieces are there, but it can't see the picture on the box. The update service internally tries to build a dependency graph where each patch lists the patches it needs before it. If that graph has a loop, a missing dependency, or a corrupted manifest, you get this error.

You'll typically see this after a failed cumulative update, a stalled Windows Update scan, or if you've manually installed updates out of order. It's common on Windows 10 22H2 and Windows 11 23H2, especially after using third-party tools like WAU Manager or disabling updates for a while, then letting them pile up.

The reason step 1 works for most people is it clears the corrupted download cache that Windows is trying to sequence. Step 2 resets the whole update pipeline. Step 3 is for the stubborn cases where the database itself is broken.

Step 1: The 30-Second Fix — Clear Update Cache

No admin rights? Just reboot. But if that didn't help (and it usually doesn't for this error), do this:

1. Press Win + R, type services.msc, hit Enter.
2. Find Windows Update service, right-click it, select Stop.
3. Open File Explorer, go to C:\Windows\SoftwareDistribution\Download.
4. Delete everything inside the Download folder. Don't delete the folder itself.
5. Go back to services, right-click Windows Update, select Start.

What's happening here: the Download folder holds partially downloaded update packages. When Windows tries to sequence them, it reads metadata from those files. If a file is corrupt or truncated, the sequence algorithm throws 0x00000670. Deleting the content forces Windows to redownload from scratch, where the fresh files have clean metadata.

Now run Windows Update again. If it works, you're done. If not, move on.

Step 2: The 5-Minute Fix — Run the Built-in Troubleshooter + Reset

Windows has a troubleshooter that resets update components automatically. It's better than doing it by hand because it also repairs permissions and re-registers DLLs.

1. Open Settings > Update & Security > Troubleshoot > Additional troubleshooters.
2. Select Windows Update, then Run the troubleshooter.
3. Let it complete. It will stop services, rename SoftwareDistribution and Catroot2 folders, and restart services.
4. Reboot.

The reason step 3 works in that troubleshooter is it renames the two main update databases (SoftwareDistribution and Catroot2). Windows creates fresh copies on next boot. This clears out corrupt update history that's confusing the sequence algorithm. If that still fails, move to the advanced fix.

Step 3: The 15+ Minute Fix — Manual Component Reset

This is for when the troubleshooter can't fix it. You'll manually reset every piece of the update pipeline. Open an admin Command Prompt (right-click Start > Terminal (Admin)).

1. Stop the update services:

   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver

2. Rename the critical folders (keeps them as backup):

   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 Catroot2.old

3. Reset the BITS queue and Windows Update cache:

   sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
   sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

   These commands restore default security descriptors on the update services. Corrupted permissions can prevent the sequence algorithm from reading registry keys it needs.

4. Re-register all update DLLs:

   cd /d %windir%\system32
   regsvr32.exe atl.dll /s
   regsvr32.exe urlmon.dll /s
   regsvr32.exe mshtml.dll /s
   regsvr32.exe shdocvw.dll /s
   regsvr32.exe browseui.dll /s
   regsvr32.exe jscript.dll /s
   regsvr32.exe vbscript.dll /s
   regsvr32.exe scrrun.dll /s
   regsvr32.exe msxml.dll /s
   regsvr32.exe msxml3.dll /s
   regsvr32.exe msxml6.dll /s
   regsvr32.exe actxprxy.dll /s
   regsvr32.exe softpub.dll /s
   regsvr32.exe wintrust.dll /s
   regsvr32.exe dssenh.dll /s
   regsvr32.exe rsaenh.dll /s
   regsvr32.exe gpkcsp.dll /s
   regsvr32.exe sccbase.dll /s
   regsvr32.exe slbcsp.dll /s
   regsvr32.exe cryptdlg.dll /s
   regsvr32.exe oleaut32.dll /s
   regsvr32.exe ole32.dll /s
   regsvr32.exe shell32.dll /s
   regsvr32.exe initpki.dll /s
   regsvr32.exe wuapi.dll /s
   regsvr32.exe wuaueng.dll /s
   regsvr32.exe wuaueng1.dll /s
   regsvr32.exe wucltui.dll /s
   regsvr32.exe wups.dll /s
   regsvr32.exe wups2.dll /s
   regsvr32.exe wuweb.dll /s
   regsvr32.exe qmgr.dll /s
   regsvr32.exe qmgrprxy.dll /s
   regsvr32.exe wucltux.dll /s
   regsvr32.exe muweb.dll /s
   regsvr32.exe wuwebv.dll /s

5. Reset the Winsock catalog (this fixes network-layer issues that can break update downloads):

   netsh winsock reset
   netsh winhttp reset proxy

6. Start the services again:

   net start wuauserv
   net start cryptSvc
   net start bits
   net start msiserver

7. Reboot and check for updates.

If none of this works, you're looking at a deeper system file corruption. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin command prompt. That replaces OS files that the update sequence algorithm depends on. On rare occasions, the only remaining option is an in-place upgrade (keep files) using the Windows 10 or 11 Media Creation Tool — but that's a nuclear option for when absolutely nothing else does.

One last thing: If you're running a third-party antivirus like McAfee or Norton, temporarily disable it during the update. Those tools sometimes hook into the update service and corrupt the sequence parsing. I've seen this exact error vanish the moment Bitdefender was uninstalled.