| Previous | Next |
| MILERR_QUEUED_PRESENT_NOT_SUPPORTED | MILERR_NO_REDIRECTION_SURFACE_RETRY_LATER |
MILERR_NOT_QUEUING_PRESENTS
MILERR_NOT_QUEUING_PRESENTS is a Windows Media Integration Layer (MIL) HRESULT. It indicates that the requested operation expects queued presents but the current presentation path is not configured to use them.
What to check for MILERR_NOT_QUEUING_PRESENTS
- Check the selected presentation mode and whether queued presentation was actually enabled for the target.
- Use an API path that matches the current non-queued presentation configuration.
- Avoid relying on queued-present timing or latency assumptions unless the feature is active.
Microsoft documentation about WPF hardware-accelerated rendering
Diagnostic interpretation of MILERR_NOT_QUEUING_PRESENTS
MILERR_NOT_QUEUING_PRESENTS has the HRESULT value 0x88980094. AllStat records the condition as “Queued Presents are not being used.”. For MILERR_NOT_QUEUING_PRESENTS, 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_NOT_QUEUING_PRESENTS
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x88980094 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_NOT_QUEUING_PRESENTS or the milerr / queuing / presents operation.
- Preserve the first failure in the call chain; a later HRESULT can describe cleanup rather than the original milerr / queuing / presents condition.
Retry and recovery for MILERR_NOT_QUEUING_PRESENTS
Retry MILERR_NOT_QUEUING_PRESENTS only when the owning API documents a transient state or after the condition described as “Queued Presents are not being used.” has changed. For MILERR_NOT_QUEUING_PRESENTS, 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.