| Previous | Next |
| MILERR_COLORSPACE_NOT_SUPPORTED | MILERR_DISPLAYID_ACCESS_DENIED |
MILERR_PREFILTER_NOT_SUPPORTED
MILERR_PREFILTER_NOT_SUPPORTED is a Windows Media Integration Layer (MIL) HRESULT. It indicates that the current rendering path cannot apply the selected bitmap prefiltering mode.
What to check for MILERR_PREFILTER_NOT_SUPPORTED
- Check the bitmap effect, scaling mode, and graphics-device capabilities used by the request.
- Disable or replace the prefiltering option with a rendering mode supported by the target device.
- Do not force the unsupported state after a device or display configuration change.
Microsoft documentation about WPF hardware-accelerated rendering
Diagnostic interpretation of MILERR_PREFILTER_NOT_SUPPORTED
MILERR_PREFILTER_NOT_SUPPORTED has the HRESULT value 0x889800A0. AllStat records the condition as “The requested bitmap pre-filtering state is not supported.”. For MILERR_PREFILTER_NOT_SUPPORTED, in practice, interpret that wording at the boundary owned by the Windows component or COM interface that returned the HRESULT, rather than treating the value as a generic Windows message.
Evidence to capture for MILERR_PREFILTER_NOT_SUPPORTED
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x889800A0 value before a wrapper converts it to an exception or Boolean result.
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions MILERR_PREFILTER_NOT_SUPPORTED or the milerr / prefilter / supported operation.
- For MILERR_PREFILTER_NOT_SUPPORTED, check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.
Retry and recovery for MILERR_PREFILTER_NOT_SUPPORTED
Retry MILERR_PREFILTER_NOT_SUPPORTED only when the owning API documents a transient state or after the condition described as “The requested bitmap pre-filtering state is not supported.” has changed. For MILERR_PREFILTER_NOT_SUPPORTED, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.
Looking for a different code? Search another status or error code.