| Previous | Next |
| SL_E_INVALID_LICENSE_STATE_BREACH_GRACE_EXPIRED | SL_E_INVALID_XML_BLOB |
SL_E_INVALID_TEMPLATE_ID
What the constant narrows down
HRESULT 0xC004C2F6 is exposed as SL_E_INVALID_TEMPLATE_ID by Genuine Validation. The code says more than the friendly message: the validation request names a template that the validation engine does not recognize.
Windows reports “Genuine Validation determined the validation input template identifier is invalid”.
From input to HRESULT
| Different result | If the experiment instead proves “the validation evidence is expected to be XML but fails structural or schema validation”, diagnose that condition separately rather than treating it as this HRESULT. |
What successful remediation must prove
To correct this using supported mechanisms, obtain the template from the matching validation workflow and record its identifier and producer.
Changes that make this code harder to diagnose
- Avoid using unofficial activation patches during integrity investigation.
- Avoid rebuilding stores before preserving hashes and event history.
- Avoid hand-editing signed blobs, protected files or firmware tables.
Technical references
Looking for a different code? Search another status or error code.