0X0000066A Patch Target Not Found – Fix It Fast

1. Corrupt Windows Update Store – The Most Common Cause

Nine times out of ten, this error comes from a corrupted Windows update store – specifically the SoftwareDistribution or Catroot2 folders. I’ve seen this on Windows Server 2019, Windows 10 (especially 1809 and 1903), and even on WSUS servers. If you get 0X0000066A after a failed cumulative update or a stuck install, this is where you start.

The real trigger is often a manual reboot during an update, or a space issue that leaves files half-written. I had a client last month whose entire print queue died because of this – the update process left the store in a state where it couldn't match the patch to any installed components.

Here’s the fix – reset the update store manually:

1. Open Command Prompt as Administrator – right-click Start, choose Command Prompt (Admin) or PowerShell (Admin).
2. Stop the update services by running these commands one at a time:

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

3. Rename the corrupt folders (don't delete them – you might need to roll back):

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

4. Restart the services:

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

5. Run Windows Update again. It will rebuild those folders fresh.

This works for about 80% of cases. If you're still stuck, move on to the next cause.

2. Missing or Corrupt Registry Key for Update Target

Sometimes the patch engine can't find the target because a registry key is missing – specifically under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing. I’ve seen this more times on systems that had an in-place upgrade or a feature update. The update tries to patch a file that no longer has a registered baseline, and boom – 0X0000066A.

Here’s the drill. Open Regedit as Administrator and navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

Look for a subkey named Packages. If it’s missing or empty, that’s your problem. But don't create it manually – that can break things worse. Instead, use the DISM tool to repair the component store:

DISM /Online /Cleanup-Image /RestoreHealth

Let that run – it can take 15-30 minutes. After it finishes, run sfc /scannow to double-check system file integrity. Then reboot and try the update again. I’ve seen this fix a lot of stubborn 0X0000066A errors on Server 2016 and 2022.

3. WSUS Client Pointing to Wrong Source

This one is sneaky – especially in corporate environments. If your server is configured to get updates from a WSUS server, but the WSUS server hasn't approved the patch or the client's policy is misaligned, you'll see this error. The patch file exists on disk (downloaded from WSUS), but the client can't match it to a target because the metadata is from a different update catalog.

I had a case where a client had a stale GPO pointing to an old WSUS server that was decommissioned. The update engine kept downloading the patch but couldn't install it because the target reference was missing.

Quick fix – reset the WSUS client configuration:

1. Open Command Prompt as Admin.
2. Run:

   wuauclt /resetauthorization /detectnow

3. Then force a detection:

   wuauclt /detectnow

4. Check your WSUS GPO: go to Computer Configuration > Administrative Templates > Windows Components > Windows Update and verify the intranet update service location is correct.

If you're not using WSUS, check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU – if UseWUServer is set to 1, but you don't have a WSUS server, that’s your problem. Change it to 0 and restart the Update service.

Quick Reference Summary Table

That's it. Start with #1 – it's the most common and takes under 5 minutes. If you're still seeing the error after all three, you may have a deeper SxS store corruption that needs a repair install, but that's rare. I've only seen it once in five years.