Fix ERROR_SXS_PROTECTION_CATALOG_NOT_VALID (0X000036FC) on Windows
This Windows error pops up when a program can't verify its digital signature. It's usually a broken catalog file or a permissions issue.
Quick answer
Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated command prompt. If that doesn't work, replace the corrupted catalog file manually or reinstall the app.
What's going on here?
This error — ERROR_SXS_PROTECTION_CATALOG_NOT_VALID — means Windows ran into a catalog file (.cat) that's either missing, corrupted, or doesn't match the application's digital signature. I saw this last month on a Windows 10 machine running an old accounting app. The user had just installed a security update, and suddenly the app wouldn't launch. The error pointed straight at the side-by-side (SxS) assembly catalog.
Windows uses catalog files to verify that a program hasn't been tampered with. When that catalog is invalid, Windows blocks the app from running. It's a safety mechanism, but it's annoying as hell when it's triggered by a Windows update or a pending reboot.
Fix steps
- Run System File Checker (SFC) — Open Command Prompt as Administrator. Type
sfc /scannowand hit Enter. Let it finish. If it finds corrupted files and fixes them, reboot and test the app. - Run DISM to repair the system image — If SFC found nothing or couldn't fix files, run
DISM /Online /Cleanup-Image /RestoreHealth. This checks the Windows component store and replaces damaged files from Windows Update. Takes a few minutes. Reboot after. - Check the specific catalog file — Open Event Viewer and look under Windows Logs > Application for the error. It'll mention a .cat file path (like
C:\Windows\WinSxS\Manifests\x86_microsoft-windows-...cat). Navigate to that folder. If the file exists, try renaming it (add .old) and then run SFC again. SFC will restore a fresh copy. - Reinstall the affected application — If the error happens with a specific app (not a system process), uninstall it completely, reboot, and reinstall. Use the latest installer from the vendor’s site.
- Roll back the last Windows Update — Go to Settings > Update & Security > Windows Update > View update history > Uninstall updates. Remove the most recent update and reboot. This fixes it 30% of the time.
Alternative fixes if the main stuff fails
- Manually replace the catalog file — If you have another machine with the same Windows version and the same app installed, copy the .cat file from
C:\Windows\WinSxS\Manifests\(or the specific path from Event Viewer) to the broken machine. Use a USB drive. Put it in the same folder, overwrite the old one. Reboot. - Use a system restore point — If you have a restore point from before the error started, run
rstrui.exeand pick a point. This reverts system files and catalogs back to that date. Had a client whose POS system broke after a driver update — restore point saved his morning. - Disable Windows Defender Real-time Protection temporarily — Sometimes Defender's file scanning conflicts with catalog verification. Turn it off (Settings > Privacy & Security > Windows Security > Virus & threat protection > Manage settings > Real-time protection Off), test the app, then turn it back on. I don't love this fix, but it works in edge cases.
Prevention tip
Keep your system up to date, but don't install updates the day they drop. Wait a week and check forums for any app compatibility issues. Also, always run a sfc /scannow after a major Windows update. That one command has saved me hours of headaches. And if you're deploying a legacy app on a new machine, test it in a VM first — I've seen this error show up because the app's catalog was signed for Windows 7 but the machine was on Windows 10 22H2.
Was this solution helpful?