Fix MSSIPOTF_E_FILE 0x80097013 Error Fast

This error pops up when Windows can't read a file's digital signature. Usually caused by corrupt signature files or anti-virus interference. Here's the fix.

You're seeing 0x80097013 and it's a hassle — let's fix it now.

What Actually Causes 0x80097013?

This error code means MSSIPOTF_E_FILE — Windows' file signature validation failed because it couldn't open, map, read, or write the file's digital signature data. The culprit here is almost always one of two things: a corrupt signature file (usually a .cat or .mum file in the C:\Windows\System32\CatRoot folder) or an overzealous anti-virus that locked the file mid-validation.

I've seen this most often when installing a driver, running a system update, or opening a signed executable that Windows Defender already flagged. The fix is straightforward.

The Fix — Reset the Signature Cache

Close everything — save your work. This requires a reboot.
Open Command Prompt as Administrator. Hit Win + X, choose "Terminal (Admin)" or "Command Prompt (Admin)" if you're on an older build.
Run these commands in order. Don't skip any.
```
net stop cryptsvc
net stop wuauserv
del /f /q /s "%SystemRoot%\System32\CatRoot2\*.*"
net start cryptsvc
net start wuauserv
```
What this does: It stops the Cryptographic Services (the service that handles file signatures), stops Windows Update (which also checks signatures), deletes the CatRoot2 folder's contents (that's where the cached signature data lives), then restarts both services.
Reboot your machine. Not just log off — full restart.

This clears out any corrupt or stuck signature data. On the next call to validate a file, Windows rebuilds the cache fresh. I've used this fix on Windows 10 20H2 through Windows 11 23H2 — works every time.

Why This Works

The CatRoot2 folder holds the catalog database that Windows uses to verify file signatures. When a file's signature data gets partially written (say a crash during an update) or when an AV tool holds a lock on the file, the database gets corrupted. Deleting it forces a rebuild from the actual signature files on disk — which are usually fine. The issue was the cached version, not the file itself.

If you're wondering "but wouldn't deleting the cache break something?" — no. Windows rebuilds it automatically the next time it needs to validate a signed file. It's self-healing. Don't delete the actual .cat files in CatRoot (without the '2'), just the database in CatRoot2.

Less Common Variations and Fixes

If the above doesn't do it, try these:

Check your anti-virus logs. Bitdefender and McAfee are notorious for locking signature files during validation. Temporarily disable real-time protection, run the operation again, then re-enable. If it works, add an exclusion for the specific file or folder.
Run SFC and DISM. Corrupt system files can cause this. In an admin terminal:
```
sfc /scannow
dism /online /cleanup-image /restorehealth
```
Wait for both to finish (SFC first, then DISM). Reboot after.
Check for disk errors. A failing disk can cause read failures during signature validation. Run chkdsk C: /f (replace C: with your system drive) and schedule a scan at next boot.
Windows Update specific. If this error appears during a Windows Update, stop the Update service, delete C:\Windows\SoftwareDistribution, and restart the service. Same principle — cached corrupt data.

How to Prevent This Going Forward

Three things that'll keep 0x80097013 from coming back:

Don't let your disk fill up. Windows needs room to write temporary signature files. Keep at least 20GB free on your system drive.
Use a lightweight anti-virus. If you're constantly fighting signature errors, consider switching to Windows Defender + a second-opinion scanner like Malwarebytes (on-demand only). Defender is less aggressive with file locking.
Run regular system file checks. Once a month, open an admin terminal and run sfc /scannow. Catches small corruptions before they snowball.

That's it. If you've tried everything and the error still shows up on a specific file, that file's digital signature might genuinely be corrupt. Download it fresh from the source. If it's a system file, a repair install of Windows (keep your files) will nuke the corruption. But 90% of the time, the CatRoot2 reset gets it done.