| 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. For DWRITE_E_CACHEVERSION, do not copy a font cache between machines or OS images as a performance optimization.
What the status establishes
When DWRITE_E_CACHEVERSION is returned, 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 in the DWRITE_E_CACHEVERSION path. For DWRITE_E_CACHEVERSION, font files should not be removed merely because the cache is rejected.
For DWRITE_E_CACHEVERSION, inspect the following boundary: version marker and cache lifecycle after OS servicing, image deployment, rollback, or copied profile data.
Build a useful incident record
| Record | Why it matters here |
|---|---|
| Cache version metadata when observable | For DWRITE_E_CACHEVERSION, recording cache version metadata when observable separates the DirectWrite font-cache compatibility boundary from a later wrapper symptom. |
| Current OS and DirectWrite file versions | In DWRITE_E_CACHEVERSION diagnostics, recording current OS and DirectWrite file versions ties the HRESULT to the DirectWrite font-cache compatibility boundary rather than to the final visible failure. |
| Upgrade, rollback, restore, or profile migration history | Comparing upgrade, rollback, restore, or profile migration history shows whether DWRITE_E_CACHEVERSION follows input, object state, or environment. |
| Font-cache service restart and regeneration events | Preserving font-cache service restart and regeneration events provides the evidence needed to test this distinction: cACHEFORMAT indicates invalid data independent of version; CACHEVERSION can be resolved by rebuilding cache data for the installed runtime. |
Interpret the controls
| Test | Interpretation | Hold constant |
|---|---|---|
| Same environment, reduced input | If DWRITE_E_CACHEVERSION disappears with a smaller faithful case, complexity within DirectWrite font-cache compatibility is implicated. | For DWRITE_E_CACHEVERSION, keep cache version metadata when observable fixed while simplifying upgrade, rollback, restore, or profile migration history. |
| Same input, fresh object generation | If DWRITE_E_CACHEVERSION changes after rebuilding state, examine ownership across font loader, font file or cache reader, face construction, shaping or glyph operation, and caller fallback. | For DWRITE_E_CACHEVERSION, place current OS and DirectWrite file versions on the timeline of the last successful transition. |
| Same operation on a controlled second path | If DWRITE_E_CACHEVERSION follows one environment, the failure is not explained by source data alone. | For DWRITE_E_CACHEVERSION, compare OS build, DirectWrite version, font source, process architecture, locale, and rendering parameters while preserving font-cache service restart and regeneration events. |
Reduce the scenario safely
For DWRITE_E_CACHEVERSION, preserve cache identity and servicing history, stop dependent components through supported means, and allow the installed runtime to regenerate derived data. When DWRITE_E_CACHEVERSION is returned, verify reuse across subsequent starts so a deployment tool is not restoring the rejected cache.
- When DWRITE_E_CACHEVERSION is returned, allow the supported service path to regenerate the cache.
- Test with a fresh user or clean cache location in the DWRITE_E_CACHEVERSION path.
- For DWRITE_E_CACHEVERSION, verify servicing completed without mixed binaries.
- When DWRITE_E_CACHEVERSION is returned, confirm no deployment tool restores an older cache after boot.
Prove the correction
A correction for DWRITE_E_CACHEVERSION should let the operation at the DirectWrite font-cache compatibility boundary complete repeatedly under the original supported conditions. Repeat the control that begins with “Allow the supported service path to regenerate the cache” and confirm that the following lifecycle step also succeeds. For DWRITE_E_CACHEVERSION, keep the original failing sample and one deliberate negative case so fallback cannot be mistaken for repair.
Technical references
When DWRITE_E_CACHEVERSION is returned, these references define the public API family, object model, or error list used to interpret this status.
- Microsoft: DirectWrite error codes.
- Microsoft: Introducing DirectWrite.
- Microsoft: DirectWrite font interfaces.
- Microsoft: Glyph image formats in DirectWrite.
Looking for a different code? Search another status or error code.