| Previous | Next |
| DWRITE_E_CACHEFORMAT | DWRITE_E_UNSUPPORTEDOPERATION |
DWRITE_E_CACHEVERSION
The scope of DWRITE_E_CACHEVERSION is DirectWrite font-cache compatibility. The font cache was created for a DirectWrite version incompatible with the current runtime. Keep 0x88985008 beside the returning method because a wrapper can replace this distinction with a generic subsystem message.
Keep neighboring failures separate
CACHEFORMAT indicates invalid data independent of version; CACHEVERSION can be resolved by rebuilding cache data for the installed runtime. Do not copy a font cache between machines or OS images as a performance optimization.
What the status establishes
Font-cache data is derived state tied to a runtime format and version. Corrupt structure and incompatible version are distinct: one points to invalid stored bytes, while the other can follow servicing, rollback, deployment, or restoration of cache data from another image. Font files should not be removed merely because the cache is rejected.
Version marker and cache lifecycle after OS servicing, image deployment, rollback, or copied profile data.
Evidence to preserve
- Cache version metadata when observable
- Current OS and DirectWrite file versions
- Upgrade, rollback, restore, or profile migration history
- Font-cache service restart and regeneration events
Reduce the scenario safely
Preserve cache identity and servicing history, stop dependent components through supported means, and allow the installed runtime to regenerate derived data. Verify reuse across subsequent starts so a deployment tool is not restoring the rejected cache.
- Allow the supported service path to regenerate the cache.
- Test with a fresh user or clean cache location.
- Verify servicing completed without mixed binaries.
- Confirm no deployment tool restores an older cache after boot.
Technical references
Looking for a different code? Search another status or error code.