| Previous | Next |
| ERROR_CAPAUTHZ_SCCD_INVALID_CATALOG | ERROR_CAPAUTHZ_SCCD_PARSE_ERROR |
ERROR_CAPAUTHZ_SCCD_NO_AUTH_ENTITY
Package family or signature hash does not match an SCCD authorization
ERROR_CAPAUTHZ_SCCD_NO_AUTH_ENTITY means the descriptor parsed, but none of its authorized-entity entries matched the application being installed. The comparison can involve package family names and signature hashes, so a package rebuilt under another publisher certificate can fail even when its manifest declares the same custom capability.
Calculate the actual package family name from the current manifest and publisher, inspect the package signature, and compare both with the SCCD issued by the capability owner. Watch for using a descriptor for a test publisher in a production build or for signing after the SCCD was generated. The correct fix is a descriptor authorizing the real package identity, not editing the signed XML.
What to inspect
- Compare the installed PFN with every authorized entity in the SCCD.
- Verify the current package certificate and signature hash.
- Request a newly issued SCCD when the publisher identity changes.
References
- Microsoft: matching PFN and signature hash for SCCD
- Microsoft: issuing a custom capability descriptor
- Microsoft: package identity fields
Looking for a different code? Search another status or error code.