What does HRESULT 0xC00D1BB2 (NS_E_INVALID_VBR_COMPAT) mean?

NS_E_INVALID_VBR_COMPAT

How to interpret the code in a real encoding session

0xC00D1BB2 is named NS_E_INVALID_VBR_COMPAT. Its practical scope is VBR rate control conflicts with the selected Windows Media Player 7.1 compatibility target, which belongs to legacy player compatibility rules rather than to every part of Windows Media playback or Windows itself.

Mechanism and point of failure

Windows Media Encoder profiles can be checked for compatibility with older Windows Media Player generations. VBR, multiple audiences, audio/video format variation, interlace and non-square pixels can move a profile beyond the version 7.1 compatibility envelope.

The profile may be valid for Windows Media 9 or later and still be intentionally rejected when an older compatibility target is required. A typical reproduction is: a modern VBR profile is marked for Player 7.1 playback. This makes the first result from the Encoder more valuable than a later generic message.

Minimal experiment

1. Record 0xC00D1BB2, the Encoder version and the exact API call or property access that returned it.
2. Export the current .wme or .prx configuration, then capture DetectCompatibility result and VBRMode for each stream.
3. Verify the legacy player compatibility rules precondition without changing the source, profile and output sink at the same time.
4. Run one controlled comparison that changes only the identified precondition: use CBR for the legacy target or raise the minimum supported player version.

Do not collapse these results together

What to change—and what to leave alone

Do not describe a compatibility result as codec corruption; first decide whether support for the older player is a real requirement.

Authoritative documentation

• Detecting profile compatibility.
• IWMEncProfile2.VBRMode.
• Selecting a video codec for an audience.
• Adding an audience to an encoder profile.