H.264-only UVC camera reported as "Custom" frame source: Windows Camera app and Settings preview show no video (MediaCapture 0xC00DABE7)

Daniel SERCY 0 Reputation points
2026-10-20T14:10:33.01+00:00

Hello,

We develop a USB Video Class camera whose only VideoStreaming format is H.264.

We tested it with UVC 1.1 frame-based H.264 descriptors and with UVC 1.5 VS_FORMAT_H264 descriptors.

On Windows 11 25H2 (build 26200), the in-box usbvideo.sys driver enumerates the device, and Media Foundation Source Reader and DirectShow stream it.

The Windows H.264 decoder MFT decodes it correctly.

However, the Windows Camera app and the Settings > Bluetooth & devices > Cameras preview show no video.

MF_DEVICESTREAM_ATTRIBUTE_FRAMESOURCE_TYPES is reported as 128 (Custom), and MediaCapture.InitializeAsync fails with 0xC00DABE7.

Please confirm that the Windows Camera app and the Settings camera preview cannot display a UVC camera that exposes only an H.264 stream, with no MJPEG or uncompressed format, and that this is by design.

Is classifying an H.264-only UVC stream as Custom instead of Color the expected behavior of the Windows camera stack (usbvideo.sys / Frame Server)?

Is it the same for UVC 1.1 frame-based and UVC 1.5 VS_FORMAT_H264 descriptors?

Is there a supported device-side mechanism for this stream to be reported as Color while remaining H.264-only?

Examples include a descriptor field, an MS OS 2.0 descriptor registry property such as a frame source type declaration, or an INF setting.

If an additional uncompressed or MJPEG format is required, which format, resolution and frame-rate combinations are the minimum for the Camera app and Settings preview to work?

Will the Camera app then use the H.264 format for recording, or only the uncompressed/MJPEG format?

Do you recommend another in-box Windows 11 application or API for live viewing of an H.264-only UVC camera?

Regards

Windows for home | Windows 11 | Devices and drivers
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-20T14:12:27.3733333+00:00

    The best-supported compatibility approach is to expose at least one YUY2 or NV12 preview mode alongside H.264, then validate Camera, Settings, MediaCapture, and the camera HLK tests on Windows 11 25H2.

    What can be confirmed

    Question Supported conclusion
    Is H.264-only failure in Camera/Settings documented as by design? No public Microsoft document explicitly confirms that. usbvideo.sys supports discovery, negotiation, and streaming of H.264, but this does not guarantee compatibility with every MediaCapture-based application.^1^
    Does 128 mean Custom? Yes. 128 (0x0080) is MFFrameSourceTypes_Custom; Color is 0x0001.^2^
    Must an H.264-only UVC stream be classified Custom? Not publicly specified. The attribute documentation says an undefined frame-source type defaults to Color, but it does not define H.264-only classification rules.^3^
    Is behavior guaranteed identical for UVC 1.1 frame-based and UVC 1.5 H.264 descriptors? Not documented. Windows supports stream-based/frame-based formats, UVC 1.1, UVC 1.5, and H.264, but no public document states that both descriptor paths receive identical Frame Server classification.^4^
    Can firmware, MS OS 2.0, or INF force this stream to Color? No supported property for overriding an H.264 stream’s frame-source type is documented. SensorCameraMode and SkipCameraEnumeration control color/sensor device-category registration, not MF_DEVICESTREAM_ATTRIBUTE_FRAMESOURCE_TYPES on an individual stream.^5^
    Is there a documented minimum fallback mode? No universal minimum resolution or frame rate is published for Camera or Settings preview.
    Will Camera record native H.264 after adding a raw format? Not guaranteed. Selection is application- and topology-dependent. Microsoft’s HLK includes a supported scenario using an uncompressed preview media type and H.264 recording, but that does not prove the retail Camera app will select native H.264.^6^

    The documented Capture Engine requirement for “at least one uncompressed stream” appears in the Frame Server Custom Media Source documentation. It explains your observed MediaCapture behavior, but its stated scope is Custom Media Sources, not a formal universal rule for inbox UVC devices.^7^

    1. Retain the existing H.264 media type.
    2. Add at least one standard preview-compatible media type:
      • Prefer YUY2 or NV12.
      • Alternatively, expose MJPEG. Windows supports MJPEG and can decode it within the camera pipeline.^8^
    3. As an engineering starting point—not a Windows requirement—test:
      • YUY2 or NV12, 640×480 at 30 fps;
      • then 1280×720 at 30 fps if USB bandwidth permits.
    4. These may be advertised as additional media types on the existing capture pin. Do not introduce separate preview and record pins solely because the HLK scenario uses that terminology; no cited requirement makes a multi-pin topology mandatory here.
    5. Recheck:
      • Camera preview;
      • Settings → Bluetooth & devices → Cameras;
      • MediaCapture.InitializeAsync;
      • Source Reader and DirectShow;
      • HLK Camera Driver Basic, Functional, and Reliability tests.

    If legacy DirectShow compatibility matters, Microsoft specifically recommends making YUY2 available because many legacy clients assume YUY2 or MJPEG.^7^

    H.264-only viewing

    There is no documented in-box Windows 11 application guaranteed to preview an H.264-only UVC source. Since Source Reader and DirectShow already stream and the decoder MFT works, the supported engineering path is a desktop viewer built on Media Foundation Source Reader or DirectShow, or a compatible third-party capture application. MediaFrameReader is not a workaround when the required MediaCapture.InitializeAsync operation itself fails.

    Obtain an authoritative design ruling

    Only Microsoft camera/driver engineering support can confirm whether the exact Windows 11 25H2 build-26200 classification and 0xC00DABE7 result are intentional or a stack defect. Open a hardware/driver support case through the Microsoft Hardware Developer or Partner Center support channel and attach:

    • complete UVC 1.1 and UVC 1.5 descriptor dumps;
    • Probe/Commit and USB traces;
    • Camera Frame Server/Media Foundation ETW traces;
    • the frame-source attributes and enumerated media types;
    • exact reproduction code and HRESULT;
    • comparison results with an added YUY2/NV12 mode;
    • relevant HLK results.

    No supplied public documentation defines 0xC00DABE7 for this particular initialization path, so assigning a more specific cause from that code alone would be speculative.

    References

    1. USB H.264 video cameras support
    2. MFFrameSourceTypes enumeration (mfapi.h)
    3. MF_DEVICESTREAM_ATTRIBUTE_FRAMESOURCE_TYPES attribute
    4. USB Video Class driver overview
    5. USB Video Class (UVC) camera implementation guide
    6. Camera Driver Test - Preview, Record H.264 Video and AAC Audio
    7. Frame Server Custom Media Source
    8. MJPEG at source autodecode for USB video class (UVC)
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.