Quick answer: Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated command prompt. That fixes most cases. If not, you'll need to repair the registry from a bootable USB.
I know this error is infuriating because it's cryptic and rare. You're just trying to install an update or open a system tool, and suddenly Windows throws STATUS_NO_MATCH (0XC0000272) in your face. The message says "There was no match for the specified key in the index" — which sounds like a bad registry lookup, and that's exactly what it is. This error typically appears during Windows Update, or when a service tries to read a registry key that's been corrupted or partially deleted. It also shows up after a failed uninstall of a driver or a registry cleaner that went too aggressive. The good news: you don't need to reinstall Windows. The bad news: you'll need to get your hands a little dirty.
Why This Happens
The Windows registry is a massive index of keys and values. When a program or Windows component tries to access a key that doesn't exist — or that exists but is malformed — you get STATUS_NO_MATCH. This often happens after a Windows Update fails mid-way, leaving a stale reference in the registry. I've seen it pop up on Windows 10 21H2 and Windows 11 22H2, especially after a forced reboot during an update. The registry key for the update gets half-written, and the next boot, the update service chokes.
Another common trigger is using a "registry cleaner" — I've said it before, skip those tools, they cause more harm than good. A cleaner deletes a key it thinks is orphaned, but that key was still referenced by the Security Accounts Manager or the Component-Based Servicing store. Boom — next update fails with 0XC0000272.
Fix 1: System File Checker and DISM (The First Line of Attack)
Start here. This fixes corrupted system files and the servicing store, which often resolves the registry mismatch.
- Press Windows + X and select Terminal (Admin) or Command Prompt (Admin).
- Run this command — it takes a few minutes, be patient:
sfc /scannowIf SFC finds issues but can't fix them, or if it returns clean and the error persists, run DISM next:
DISM /Online /Cleanup-Image /RestoreHealthThis checks the Windows Update component store and repairs it. It needs an internet connection, but it's the real fix for half the cases I've seen. After it completes, restart and try whatever was failing again.
Fix 2: Check for Pending Updates and Reset Windows Update Components
If the error came from Windows Update, sometimes the update cache is the culprit. I've had this happen on a client's Surface Pro 7 — the update kept failing with 0XC0000272, and resetting the update cache did the trick.
Open an elevated command prompt and run these commands in order:
net stop wuauserv
net stop cryptSvc
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bitsThis renames the update cache folders. Windows will recreate them fresh on the next update attempt. If you're on a domain machine, you might need to re-register with your WSUS server after this, but for most home users it's safe.
Fix 3: Registry Repair from a Bootable USB (When Nothing Else Works)
If the above didn't clear the error, the registry itself is corrupted. You'll need to repair it from outside Windows — Windows won't let you touch those hives while it's running.
- Create a Windows 10 or 11 installation USB using the Media Creation Tool.
- Boot from the USB. On the first screen, press Shift + F10 to open a command prompt.
- Find the Windows drive. It's usually
D:but it could be different — typediskpart, thenlist volume, thenexitto see the letters. Note the one marked System. - Run these commands to back up and replace the registry hives with the ones from the Windows.old or the RegBack folder:
cd /d D:\Windows\System32\config
ren SYSTEM SYSTEM.old
ren SOFTWARE SOFTWARE.old
ren SAM SAM.old
ren SECURITY SECURITY.old
ren DEFAULT DEFAULT.old
copy D:\Windows.old\Windows\System32\config\SYSTEM .
copy D:\Windows.old\Windows\System32\config\SOFTWARE .
copy D:\Windows.old\Windows\System32\config\SAM .
copy D:\Windows.old\Windows\System32\config\SECURITY .
copy D:\Windows.old\Windows\System32\config\DEFAULT .If you don't have a Windows.old folder, you can use the backup in C:\Windows\System32\config\RegBack — but note that Windows 10 and 11 stop auto-creating backups after a certain update, so that folder might be empty. If you have a system restore point, restoring from that is a safer bet.
After copying, exit the command prompt and reboot. If the error persists, you're looking at a repair install using the "Keep my files" option — that reinstalls Windows without deleting your data.
Alternative Fixes That Sometimes Work
Don't waste time on these unless you're desperate — they're hit-or-miss.
- Run the Windows Update troubleshooter from Settings > System > Troubleshoot. It rarely fixes 0XC0000272, but it's a 5-minute detour.
- Check for pending reboots. Look in the registry for
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired— if it exists, reboot and try again. - Uninstall recent updates — go to Settings > Windows Update > Update history > Uninstall updates, and remove the last two or three. If the error started after a specific update, this can revert the broken registry change.
Prevention Tip: Don't Let the Registry Rot
The #1 way to avoid this error is to never use registry cleaning tools. I've seen more broken machines from those than from actual malware. The registry doesn't need "optimization" — Windows has built-in functions that handle it. The second thing is to always let Windows updates finish. Don't force shutdown during an update. That's like pulling the plug on a server mid-transaction — you corrupt the index. If a laptop battery is old and dies mid-update, that's a common cause too.
Also, make a habit of creating a system restore point before major updates or driver installs. Right-click the Start button > System > System Protection > Create. It takes 30 seconds and can save you hours of registry gymnastics later.
When this error is gone, you'll be okay. Just remember — the registry is the backbone of Windows. Treat it gently.