| Previous | Next |
| DWRITE_E_NOFONT | DWRITE_E_FILEACCESS |
DWRITE_E_FILENOTFOUND
DWRITE_E_FILENOTFOUND means that DirectWrite could not open a font file because the file or the storage location that should contain it could not be found. The failure concerns the specific font resource used by the call, not DirectX installation in general.
What to identify first
- The exact font file or resource and the DirectWrite operation that first returned the HRESULT.
- Whether the font came from the system collection, an application package, a private/custom collection, a network location, or a custom font loader.
- For a custom loader, the loader key and the file identity that the loader resolved when the failing font object was created.
What to check
Verify that the expected font file still exists at the location represented by the current collection or loader and that the application is resolving the same resource it resolved when the object was created. A moved or removed file, a disconnected storage location, a stale custom-font mapping, or an application package missing the expected font can all leave DirectWrite with a valid-looking object that no longer resolves to an available file.
Compare the failing resource with a known-good font through the same loading path. If a custom loader is involved, log the key-to-resource mapping and test the loader independently rather than replacing the requested family with an unrelated fallback.
Recovery
Restore or correct the missing font resource, rebuild any collection or DirectWrite objects that were created from stale file information, and repeat the original operation. Reinstalling DirectX is not a targeted response to this HRESULT unless separate evidence shows a broader platform problem.
Technical references
Looking for a different code? Search another status or error code.