Fix DSIG 0x80097016 Font Table Error on Windows

When this error hits

You're trying to print a report from QuickBooks or open a PDF in Adobe Acrobat, and bam – you get 0X80097016 with the message "The structure of the table MSSIPOTF_E_STRUCTURE is incorrect." Or maybe it pops up during Windows Update, or when you install a new font pack. I've seen it most often when someone installs a free font from a random site, or after a Windows 11 feature update re-indexes fonts.

Root cause – plain and simple

The error points to the DSIG (digital signature) table inside a TrueType or OpenType font file. Every font has a hidden table that carries a cryptographic signature – it's Microsoft's way of verifying the font came from the original foundry and wasn't tampered with. When that table is missing, corrupted, or malformed (like having wrong field sizes), Windows chokes on it. The MSSIPOTF part is just Microsoft's internal code for "font signature checking."

Had a client last month whose entire print queue died because of this – a single bad font named "CoolFonts-Regular.ttf" kept crashing the spooler every time someone tried to print. Removed that font, fixed instantly.

Fix it: Remove or replace the bad font

The most reliable fix is to find which font is broken and either remove it or reinstall it cleanly. Here's how, step by step.

Step 1: Identify the bad font

Open Event Viewer – hit Win + R, type eventvwr.msc, press Enter. Go to Windows Logs > Application. Look for recent Error events from source "FontCache" or "MSSIPOTF." The description often names the font file directly. Example: "The structure of the table MSSIPOTF_E_STRUCTURE is incorrect in file C:\\Windows\\Fonts\\SomeFont.ttf."

If you don't see it there, run this command in an elevated Command Prompt (right-click CMD, Run as Administrator):

sfc /scannow

When it finishes, check the log at C:\\Windows\\Logs\\CBS\\CBS.log for lines containing "0x80097016" – that'll point to the font.

Step 2: Delete or rename the bad font

Take ownership of the font file first. In File Explorer, go to C:\\Windows\\Fonts. Right-click the font, choose Properties > Security > Advanced > Change (next to Owner). Enter your username, click OK, then give yourself Full Control. If you can't delete, rename it – add ".old" to the end. That stops Windows from loading it.

Step 3: Clear the font cache

Font cache holds a pre-compiled list of all fonts. If it's referencing the bad font, the error persists. Do this:

Open Services (Win + R, type services.msc).
Find Windows Font Cache Service, right-click, Stop.
Navigate to C:\\Windows\\ServiceProfiles\\LocalService\\AppData\\Local (you might need to enable hidden files in View options).
Delete the file FontCache.dat.
Go back to Services, start the Font Cache service again.

That forces Windows to rebuild the cache from scratch.

Step 4: Reinstall the font properly

If you actually need that font, download a fresh copy from a reputable source – not some sketchy font site. Right-click the new .ttf or .otf file and choose Install for all users (check the box "Install for all users" if available). Alternatively, drag it into C:\\Windows\\Fonts with admin rights.

What if it still fails?

Sometimes the problem isn't a single font – a Windows system file got corrupted. Run DISM /Online /Cleanup-Image /RestoreHealth in an admin command prompt. If that finds issues, follow up with another sfc /scannow. Also, if the error appeared after a Windows update, roll back that update temporarily – I've seen a faulty cumulative update in July 2024 that broke font parsing on certain systems.

If you're still stuck, try this: boot into Safe Mode (hold Shift while clicking Restart), then remove any recently added fonts from %WinDir%\\Fonts. Safe Mode skips third-party font loaders like Adobe Fonts or NexusFont – if the error disappears in Safe Mode, one of those loaders is injecting a bad font. Uninstall the font manager and reinstall it.

That's it. 9 times out of 10, it's a single corrupt font file. Kill it, clear the cache, and move on.