Fix STATUS_INVALID_IMAGE_HASH (0XC0000428) on Windows 10/11

Quick answer: Boot into Safe Mode and disable driver signature enforcement via advanced startup options, then find and remove the offending driver — usually a corrupted network adapter or graphics driver.

Why This Error Happens

I know this error is infuriating. It usually appears after a Windows update or a driver update gone wrong — you restart your PC and bam, blue screen with 0XC0000428. The message says the hash for an image (a .sys file or .dll) isn't in the system catalogs. That's Windows Driver Signature Enforcement throwing a fit.

Windows catalogs are like a whitelist of approved drivers. If a driver's hash doesn't match what's in the catalog, Windows refuses to load it. This most often hits Realtek network drivers, NVIDIA graphics drivers, or third-party antivirus filter drivers. I've seen it on Windows 10 22H2 and Windows 11 23H2, especially after a failed cumulative update.

Fix Steps

You'll need to boot into Safe Mode to fix this. Here's how:

Force-restart your PC three times — when the Windows logo appears, hold the power button until it shuts down. On the third restart, you'll see the blue Advanced Startup screen.
Select Troubleshoot > Advanced options > Startup Settings > Restart.
After restart, press 7 or F7 to Disable driver signature enforcement.
Once booted into Safe Mode, open an admin Command Prompt (cmd as Administrator).
Run this command to find the culprit:
```
dir %SystemRoot%\System32\drivers\*.sys /o:d
```
Look for files modified right around when the error started — usually a .sys file with a recent date.
Check the System event log (eventvwr.msc) under Windows Logs > System. Filter by Event ID 55 or 41. The log should name the failing driver — something like rt640x64.sys or nvlddmkm.sys.
Once you know the driver name, uninstall it:
```
dism /online /remove-driver /driver:rt640x64.sys
```
Replace rt640x64.sys with your actual driver file.
Restart normally. If the error's gone, you're set. If not, move to the alternative fixes.

Alternative Fixes

1. Disable Secure Boot temporarily
Some firmwares have buggy Secure Boot implementations that break catalog lookups. Enter your BIOS/UEFI and set Secure Boot to Disabled. Reboot and see if the error clears. Re-enable it later if you want — but if the error returns, update your motherboard's firmware.

2. Use System Restore
If you have a restore point from before the error started, boot from a Windows installation USB, select Repair your computer, then Troubleshoot > Advanced options > System Restore. This rolls back driver installations and updates.

3. SFC and DISM
In Safe Mode, run these — skip this until you've tried the other steps, because they rarely fix hash errors directly:

sfc /scannow
dism /online /cleanup-image /restorehealth

Prevention Tip

Always check the WHQL (Windows Hardware Quality Labs) status on driver downloads. Stick to drivers from your PC manufacturer's support site — not the chip vendor's latest beta. And if you're using an old printer or network card, consider replacing it: Windows 11 23H2 dropped support for several legacy drivers that trigger this exact error.

Pro tip: Create a restore point before every driver update. Takes 2 minutes, saves hours of headache.