| Previous | Next |
| MF_E_MEDIA_EXTENSION_APPSERVICE_CONNECTION_FAILED | MF_E_MEDIA_EXTENSION_PACKAGE_INTEGRITY_CHECK_FAILED |
MF_E_MEDIA_EXTENSION_APPSERVICE_REQUEST_FAILED
MF_E_MEDIA_EXTENSION_APPSERVICE_REQUEST_FAILED is later in the app-service flow than a connection failure. The media extension has an app-service communication path, but request processing did not complete successfully.
Capture the request result and service lifetime
- Record the status returned by the app-service message operation, not just the final Media Foundation HRESULT.
- Distinguish a generic processing failure from resource exhaustion, an oversized message, an unavailable app, authentication failure, missing network access, or policy restrictions.
- Monitor the
ServiceClosedevent and correlate it with the request that was active when the service endpoint closed.
AppServiceResponseStatus explicitly separates Failure, ResourceLimitsExceeded, MessageSizeTooLarge, AppUnavailable, and several connectivity or policy states. That distinction is valuable because retrying the same request is reasonable for some transient states but does not fix an oversized payload or deterministic decoder failure. Do not treat this code as proof that the input media itself is corrupt without the app-service response and extension-side diagnostics.
Microsoft: AppServiceResponseStatus · Microsoft: AppServiceConnection · Microsoft: media-extension app-service registration
Looking for a different code? Search another status or error code.