| Previous | Next |
| MF_E_BYTESTREAM_NOT_SEEKABLE | MF_E_CANNOT_PARSE_BYTESTREAM |
MF_E_DISABLED_IN_SAFEMODE
What the code tells you
MF_E_DISABLED_IN_SAFEMODE means Media Foundation platform startup is intentionally unavailable in Windows Safe Mode.
The result comes from MFStartup before any media graph exists. A representative case is a diagnostic tool launched during Safe Mode tries to initialize playback and fails before loading any codec.
Build a useful incident record
| Observation | What to capture |
|---|---|
| Primary discriminator | the boot mode, MFStartup arguments, OS edition and build, and confirmation that the same binary starts after normal boot |
| Owning object | MFStartup before any media graph exists, including its object identity and generation |
| Timeline marker | the call immediately before Media Foundation platform startup is intentionally unavailable in Windows Safe Mode and the completion event, callback, or state change that followed |
| Comparison artifact | one known-good run that changes only this condition: boot normally and call the same MFStartup sequence without changing the application |
The relevant condition is Media Foundation platform startup is intentionally unavailable in Windows Safe Mode. Preserve the original MFStartup before any media graph exists and the first result in the chain: a later UI message can replace this precise code with a generic playback, setup, network, or device failure.
Reproduce without erasing context
- Record this result,
0xC00D36EF, the returning method, process architecture, Windows build, and component version. - Capture the boot mode, MFStartup arguments, OS edition and build, and confirmation that the same binary starts after normal boot before retry logic changes the object.
- Perform this narrow comparison: boot normally and call the same MFStartup sequence without changing the application.
- Keep the input, account, URL, device, media type, and requested action unchanged unless one is the single tested variable.
- After correcting this result, create a fresh object or process where lifecycle state may have been retained, then repeat the original call.
What the result does not prove
This result does not by itself prove a machine-wide media-platform failure. In this case, MF_E_BAD_STARTUP_VERSION occurs in a normal boot when the startup version is incompatible. The result evidence does not justify deleting license stores, clearing every proxy setting, installing codec packs, or rewriting media files before its producer is identified.
Comparison with adjacent conditions
| Result | Different condition |
|---|---|
MF_E_OPERATION_CANCELLED | The operation is cancelled. |
MF_E_MEDIAPROC_WRONGSTATE | MediaProc is in the wrong state. |
MF_E_NO_BITPUMP | Internal; Bitpump not found. |
Resolution and proof
The supported corrective direction is to perform media processing after a normal boot; do not attempt to bypass Safe Mode component restrictions.
For an incident, keep the symbolic constant together with 0xC00D36EF. That pairing preserves the exact failure identity when signed integer fields or wrapper logs obscure the original Media Foundation or Windows Media facility.
Technical references
Looking for a different code? Search another status or error code.