| Previous | Next |
| DWRITE_E_ALREADYREGISTERED | DWRITE_E_CACHEVERSION |
DWRITE_E_CACHEFORMAT
The scope of DWRITE_E_CACHEFORMAT is DirectWrite font-cache compatibility. DirectWrite found font-cache data whose internal format is invalid or corrupt. Keep 0x88985007 beside the returning method because a wrapper can replace this distinction with a generic subsystem message.
Locate the first rejecting layer
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.
Font cache parsing and validation before cached glyph or font data can be trusted.
Misleading responses
CACHEVERSION means a structurally valid cache belongs to another DirectWrite version; CACHEFORMAT means the stored data itself cannot be accepted. Do not delete arbitrary font files when the failing object is the cache; distinguish cache regeneration from font removal.
Evidence to preserve
- Cache file identity, size, timestamp, and owner service
- OS and DirectWrite build
- Font changes immediately before corruption
- Service and filesystem errors during cache write
Controlled reproduction
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.
- Stop dependent applications before supported cache rebuild.
- Preserve a copy or hash for diagnosis when permitted.
- Validate filesystem and abrupt-shutdown history.
- Confirm DirectWrite regenerates the cache and loads the same fonts.
Technical references
Looking for a different code? Search another status or error code.