| Previous | Next |
| D2DERR_MAX_TEXTURE_SIZE_EXCEEDED | D2DERR_BAD_NUMBER |
D2DERR_UNSUPPORTED_VERSION
D2DERR_UNSUPPORTED_VERSION belongs to Direct2D runtime, version, or lower-system failure. The application requested a Direct2D version or interface level unavailable on the current runtime or device path.
What the status establishes
Internal, unsupported-version, and mapped Win32 errors sit at different layers. One can require rebuilding a Direct2D instance, another means the requested interface contract is unavailable, and the third demands recovery of a lower system status. The exact factory, device, method, and nested result determine which response is valid.
factory or interface creation and the version-specific feature being requested.
Evidence to preserve
- OS build and Direct2D DLL version
- Requested interface IID or feature version
- Device feature level and creation flags
- Fallback interface result
Reduce the scenario safely
Use a fresh factory and minimal operation, record runtime and interface versions, enable the debug layer, and capture device-removal or Win32 evidence immediately. Do not apply render-target recreation to errors that are not documented as target loss.
- queryInterface progressively for the needed version.
- Use capability checks before version-specific calls.
- Test the baseline Direct2D interface.
- Avoid shipping private system Direct2D binaries.
Keep neighboring failures separate
INSUFFICIENT_DEVICE_CAPABILITIES concerns GPU capability after the API exists; UNSUPPORTED_VERSION concerns the requested Direct2D contract. Do not respond with a universal render-target recreation loop unless the returned status specifically documents device-loss recovery; graph, property, numeric, lifetime, and print-state errors require correcting their contract.
Technical references
Looking for a different code? Search another status or error code.