HRESULT 0xC00D7179 (MF_E_TEST_SIGNED_COMPONENTS_NOT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Protected-content policy rejected one or more components signed with test credentials.

Previous	Next
MF_E_HIGH_SECURITY_LEVEL_CONTENT_NOT_ALLOWED	MF_E_ITA_UNSUPPORTED_ACTION

MF_E_TEST_SIGNED_COMPONENTS_NOT_ALLOWED

MF_E_TEST_SIGNED_COMPONENTS_NOT_ALLOWED is a signing-policy failure for protected content. A development or test signature can be sufficient for ordinary code loading, but Protected Media Path applies a stronger trust model to components that can access decrypted premium media.

Find the test-signed module in the protected path

Record the complete module list for the resolved protected topology and the full file path of every non-system transform or sink.
Check signing chains on custom media components and locally deployed dependencies.
When revocation information is reported, look for the documented MF_TEST_SIGNED_COMPONENT_LOADING reason and the user-mode/kernel-mode component flag.

Disabling signature checks is not an appropriate remediation for protected playback. Replace the test-signed component with the properly signed production component or remove it from the protected topology. The same component may work with unprotected content, which is why testing only a clear asset can miss this trust-policy difference.

Microsoft: test-signed component revocation reason · Microsoft: trusted signed components in a Protected Environment · Microsoft: loading PE-signed libraries

Looking for a different code? Search another status or error code.