| Previous | Next |
| MF_E_HW_MFT_FAILED_START_STREAMING | MF_E_HARDWARE_DRM_UNSUPPORTED |
MF_E_OPERATION_IN_PROGRESS
What the code tells you
MF_E_OPERATION_IN_PROGRESS means a second request conflicts with an asynchronous operation that has not completed.
The result comes from the object serializing open, start, stop, seek, reconfiguration, or shutdown work. A representative case is two seek commands are issued before the first seek posts its completion event.
Evidence to preserve
the pending operation type, cookie, callback generation, start time, completion event, and the method that issued the duplicate request.
Build a useful incident record
Reproduce without erasing context
- Record and verify: the pending operation type, cookie, callback generation, start time, completion event, and the method that issued the duplicate request.
- Run the controlled comparison: wait for the matching completion event and then issue the second request once.
Comparison with adjacent conditions
| HRESULT | Meaning in the standard description |
|---|---|
MF_E_HW_MFT_FAILED_START_STREAMING | Hardware MFT failed to start streaming due to lack of hardware resources. |
MF_E_HARDWARE_DRM_UNSUPPORTED | No Hardware DRM support is available. |
MF_E_INVALID_CODEC_MERIT | The registered codec merit is not valid. |
Here, MF_E_OPERATION_CANCELLED is the completion of cancelled work; this code rejects new work while old work remains active.
Resolution and proof
For this occurrence, serialize commands at the application boundary and discard stale UI requests instead of overlapping them.
Authoritative references
Looking for a different code? Search another status or error code.