STATUS_INVALID_IMAGE_PROTECT (0XC0000130) — Fix Fast

1. Corrupted System Files Are the Usual Suspect

This error shows up when you try to open a program — could be a game, a productivity app, or even a Windows utility — and you get this exact stop code. The most common trigger is a botched Windows update or a crash that left system files in a bad state. Windows sees the file's digital signature or hash doesn't match what it expects, so it slams the door shut.

Here's how to fix that first:

1. Open Command Prompt as administrator. Click Start, type cmd, right-click Command Prompt, and choose "Run as administrator."
2. Type sfc /scannow and press Enter. You'll see a progress bar. Let it finish — this takes 5 to 15 minutes depending on your drive speed.
3. If SFC finds corrupted files but can't fix them all (you'll see a message about it), run DISM next. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This downloads fresh copies of system files from Microsoft's servers. Expect it to take 10 to 20 minutes.
4. After DISM finishes, run sfc /scannow one more time. This second pass should clean up anything DISM left behind.
5. Restart your computer. Try opening the app that failed before. If the error is gone, you're done.

If SFC found zero errors the first time, system corruption isn't your problem. Move to cause #2.

2. Corrupted or Unsigned Drivers Trigger This Too

Drivers are the second biggest cause of this error. Windows checks driver signatures at boot and when a program loads a driver. If a driver's been tampered with — maybe by a bad update, or a third-party tool patched it — you'll get 0XC0000130.

The quickest way to check is to look at your installed drivers in Safe Mode:

1. Restart your PC. As it boots, hold the Shift key and click Restart from the power icon. This opens the recovery menu.
2. Go to Troubleshoot > Advanced Options > Startup Settings > Restart.
3. After the restart, press 4 (or F4) to boot into Safe Mode.
4. Once in Safe Mode, open Device Manager (right-click the Start button, choose Device Manager).
5. Look for any device with a yellow exclamation mark. That's a driver that's not loading properly. Right-click it > Properties > Driver tab > Driver Details. If the driver file shows "Not digitally signed" or the file path points to a strange location (like a temp folder), that's your culprit.
6. For that device, right-click it and choose Uninstall device. Check the box that says "Delete the driver software for this device" if it appears. Then restart normally.
7. After restart, Windows will try to reinstall the driver automatically. If the error returns, you need to manually download the driver from the manufacturer's site — never from a third-party downloader.

I've seen this happen most often with network adapters (Realtek, Intel) and graphics drivers (NVIDIA, AMD). If you updated a driver recently and then this error started, roll back that driver: Device Manager > right-click the device > Properties > Driver tab > Roll Back Driver.

3. Antivirus or Security Software Is Blocking a Legit File

Sometimes the error isn't a real corruption — it's your antivirus getting paranoid. Windows Security (formerly Defender), or third-party tools like McAfee, Norton, or Malwarebytes, can flag a program's image as invalid when it's actually fine. This happens when a program gets updated and the security tool hasn't updated its whitelist yet.

To test if this is the case:

1. Temporarily turn off your antivirus real-time protection. In Windows Security: Start > Windows Security > Virus & threat protection > Manage settings > Real-time protection > Off.
2. If you use a third-party antivirus, find its shield icon in the system tray (near the clock), right-click it, and choose "Disable" or "Pause protection" for 10 minutes.
3. Try launching the app that gave the error. If it works now, add an exclusion for that specific program file. In Windows Security: Virus & threat protection > Manage settings > Exclusions > Add or remove exclusions > Add an exclusion > File > browse to the .exe file.
4. Turn real-time protection back on immediately.

Don't leave protection off — that's asking for trouble. If the error only happens with that one app and adding an exclusion fixes it, you're good. If not, you may need to reinstall the app from its official source.

Quick-Reference Summary Table

Start with cause #1 — that fixes roughly 60% of 0XC0000130 cases I've seen. If that doesn't work, move to drivers. The antivirus fix is less common but worth checking if you're still stuck.