| Previous | Next |
| MF_E_SIGNATURE_VERIFICATION_FAILED | MF_E_CODE_EXPIRED |
MF_E_DEBUGGING_NOT_ALLOWED
MF_E_DEBUGGING_NOT_ALLOWED is a deliberate protected-content restriction. The protected environment exists to reduce tampering and inspection of decrypted media; running the protected path under a debugger conflicts with that trust model.
Separate protected-path diagnostics from debugger attachment
- Confirm which process has a debugger attached. A PMP pipeline can run media processing in a separate protected process rather than solely in the application process.
- Reproduce the protected-content case without a debugger and collect normal application, Media Foundation, and event logs instead.
- Use an unprotected test asset when source-level debugging of ordinary topology or decoder logic is required.
Do not infer that the media license or codec is invalid from this HRESULT. The restriction is about the execution environment. Microsoft also documents that a PMP process can be created as an unprotected process for isolation, but that mode cannot be used for DRM playback. Switching to an unprotected process therefore is not a valid workaround for protected content that requires PMP.
Microsoft: protected and unprotected PMP process modes · Microsoft: Protected Environment threat model · Microsoft: protected-process requirements
Looking for a different code? Search another status or error code.