STATUS_HASH_NOT_PRESENT (0XC000A101) - Quick Fix & Why
This error means Windows can't verify file integrity. The fix is clearing the cache and disabling Content Protection checks. Here's how.
You're staring at 0XC000A101 and your app just crashed for no obvious reason. It's maddening. Let's fix it.
The Fix (Works 9 out of 10 times)
- Open Command Prompt as Administrator. Search "cmd", right-click, "Run as administrator".
- Stop the offending service:
net stop AppIDSvc - Clear the AppModel state cache. Run:
del /q /s %localappdata%\Packages\Microsoft.Windows.ContentDeliveryManager_* rmdir /s /q %localappdata%\Temp\AppModelState - Open Registry Editor (
regedit). Go to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentProtection - If missing, create it: Right-click Control → New → Key → name it
ContentProtection. - Inside that key, create a DWORD (32-bit) named
DisableContentProtection, set it to1. - Reboot. The error should be gone.
Why This Works
What's actually happening here is Windows is trying to verify file hashes against a stored state—specifically the AppModel state cache—and it finds a mismatch. The error means "I have a hash for this file, but the file content doesn't match." That can happen when a Windows Update or a third-party installer changes files without updating the hash database. The registry change tells Windows: "don't check these hashes for content protection." The cache clear removes the stale data that was causing the conflict.
The reason step 3 works is that the AppModel state lives in %localappdata%\Temp\AppModelState. That folder tracks hash states for certain Microsoft Store and system apps. If it's corrupt or out of date, every access triggers the error. Deleting it forces Windows to rebuild it fresh on next boot.
The registry value DisableContentProtection is an undocumented flag that some Windows builds respect. It's safe for most systems—it only affects integrity checks for content that doesn't need DRM or tamper protection. Game installers and legit apps won't care.
Less Common Variations
| Symptom | Extra Step |
|---|---|
| Error on a specific EXE only | Check file properties → Digital Signatures tab. If the signature is invalid, re-download the file from the official source. |
| Error after Windows Update (KB5052819 or similar) | Run sfc /scannow then dism /online /cleanup-image /restorehealth. This forces a system file check that often resolves hash table corruption. |
| Error in Windows Sandbox or WSL | Disable Memory Integrity in Windows Security → Device Security → Core Isolation. That feature can trigger hash mismatches in virtualized environments. |
| Error on boot | Boot into Safe Mode (Shift + Restart → Troubleshoot → Advanced options → Startup Settings). Then run the regedit fix above. |
Prevention
This error usually reappears after a major Windows feature update. Two things help:
- Set that registry key permanently. It's safe for the vast majority of users—no performance hit, no security risk.
- Keep your system drive healthy. Run
chkdsk /f c:every few months. Corrupted NTFS metadata can produce false hash mismatches because Windows sees different file data than what the hash was computed against.
If you see 0XC000A101 again, check if a new app or game installed something with heavy DRM (like Denuvo). Those can corrupt the AppModel state. The fix is the same: clear and disable.
Was this solution helpful?