Fix MSSIPOTF_E_BAD_MAGICNUMBER (0X80097004) Error

The 30-Second Fix: Clear the Font Cache

This is the most common fix. Nine times out of ten, the culprit is a stale font cache. Windows loads font data into memory, and if that cache gets corrupted, you get the 0x80097004 error. Here's how to nuke it:

1. Press Win + R, type services.msc, and hit Enter.
2. Find Windows Font Cache Service. Right-click it and select Stop. Do the same for Windows Presentation Foundation Font Cache 3.0.0.0 if it's running.
3. Open File Explorer and navigate to C:\Windows\ServiceProfiles\LocalService\AppData\Local (you'll need to show hidden files).
4. Delete everything inside the FontCache folder. Yes, everything. Don't worry, Windows rebuilds it.
5. Restart the font cache services — right-click each and select Start.

Try whatever was throwing the error again. If it's gone, you're done. If not, move to the next step.

The 5-Minute Fix: Run SFC and DISM

If the cache clear didn't work, the OS itself might have a corrupted system file. I've seen this happen after a failed Windows update or a bad driver install. Run these two commands in order:

1. Open Command Prompt as admin (right-click Start, choose Command Prompt (Admin) or Terminal (Admin)).
2. Type sfc /scannow and press Enter. Wait for it to finish. It'll check and repair protected system files.
3. After SFC completes, run DISM /Online /Cleanup-Image /RestoreHealth. This fixes the component store itself.

DISM can take 10-15 minutes. Don't interrupt it. Once both finish, reboot. Test if the error reappears. I'd say this fixes about 30% of cases where the cache clear didn't work.

The 15+ Minute Fix: Identify and Remove the Broken Font

If you're still here, you've got a specific corrupt font file. The error message points to a broken TrueType or OpenType font. You need to find it, then remove it. Here's the real way to hunt it down:

1. Open Event Viewer (eventvwr.msc). Go to Windows Logs > Application.
2. Look for an error event with source MSSIPOTF or WinTrust. The event details often include the offending file name (like arial.ttf or segoeui.ttf).
3. If you see the file name, go to C:\Windows\Fonts and find it. Right-click and delete it. Important: Do not delete system fonts like Arial or Times New Roman without a backup. Copy them elsewhere first.
4. If Event Viewer shows nothing, use Process Monitor (download from Microsoft). Filter for Path contains .ttf or .otf and look for the error in real-time when you trigger the problem.

Once you've removed the bad font, restart. The error should be gone. If you can't delete the file (permissions), boot into Safe Mode and do it there.

Last Resort: System Restore or Reset

If none of the above worked, you're looking at a deeper corruption. Try a System Restore point from before the issue started. If that's not available, you can do a repair install via a Windows 10/11 ISO — it keeps your files and apps. I've only had to go this route twice in 14 years. It's rare, but it happens.

Pro tip: Always keep a backup of your C:\Windows\Fonts folder on an external drive. Saves you hours when a font goes rogue.