Site icon EfmSoft

What does HRESULT 0xC00D36EF (MF_E_DISABLED_IN_SAFEMODE) mean?

 
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 (0xC00D36EF) is a failure result from Windows Media Foundation. The generated section above already contains the platform message; the useful extra information is that this result isolates Media Foundation platform startup is intentionally unavailable in Windows Safe Mode.

The producer is MFStartup before any media graph exists, so diagnosis should begin with that object and its state rather than with a broad reinstall or an unrelated codec change. A representative occurrence is a diagnostic tool launched during Safe Mode tries to initialize playback and fails before loading any codec.

Build a useful incident record

ObservationWhat to capture for it
Primary discriminatorthe boot mode, MFStartup arguments, OS edition and build, and confirmation that the same binary starts after normal boot
Owning objectMFStartup before any media graph exists, including its object identity and generation
Timeline markerthe 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 artifactone known-good run that changes only this condition: boot normally and call the same MFStartup sequence without changing the application

The decisive boundary 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

  1. Record this result, 0xC00D36EF, the returning method, process architecture, Windows build, and component version.
  2. 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.
  3. Perform this narrow comparison: boot normally and call the same MFStartup sequence without changing the application.
  4. keep the input, account, URL, device, media type, and requested action unchanged unless one is the single tested variable.
  5. 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

ResultDifferent checkpoint
MF_E_OPERATION_CANCELLEDThe operation is cancelled; compare this boundary specifically with it.
MF_E_MEDIAPROC_WRONGSTATEMediaProc is in the wrong state; compare this boundary specifically with it.
MF_E_NO_BITPUMPInternal; Bitpump not found; compare this boundary specifically with it.

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. Success means more than disappearance of a dialog: the same method must pass the same checkpoint, the expected event or output must appear, and no broader fallback HRESULT should replace it.

For a incident, keep the symbolic constant together with 0xC00D36EF. That pairing preserves the checkpoint 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.

Exit mobile version