| Previous | Next |
| ERROR_XML_PARSE_ERROR | ERROR_RESTART_APPLICATION |
ERROR_XMLDSIG_ERROR
The XML signature could not be processed or validated.
ERROR_XMLDSIG_ERROR is Win32 error 1466 (0x5BA). It identifies failure in XML Digital Signature processing, not merely malformed XML. The document may parse successfully while signature canonicalization, reference resolution, digest calculation, key extraction, or cryptographic verification fails. The originating API and its more detailed status are essential because this value alone does not say whether the signature is invalid, unsupported, incomplete, or attached to changed content.
Typical failure points
- a referenced element cannot be located because its ID, namespace, or URI changed
- canonicalization produces bytes different from those used when the signature was created
- a digest or signature algorithm is unsupported, disabled, or incorrectly identified
- the public key or certificate is missing, untrusted, expired, or unrelated to the signer
- the signed XML was reformatted, normalized, truncated, or modified after signing
Evidence to preserve
Record the CryptXML operation, HRESULT or security status returned nearest the failure, signature and digest algorithm URIs, reference URIs, canonicalization method, key source, certificate thumbprint, document length, and a hash of the original byte stream. Preserve a redacted copy before any DOM save or pretty-print operation, because serialization can alter namespace declarations and whitespace that participate in canonicalization.
Diagnostic sequence
First verify that the XML is well-formed and that the expected Signature, SignedInfo, Reference, and key information are present. Resolve each reference exactly as the verifier does and calculate its digest independently. A reference-digest mismatch points to changed content or transform behavior before public-key verification is considered.
Next inspect canonicalization, transforms, and algorithm policy. Confirm that namespace context has not been lost when a subtree was copied. Then validate the signing certificate or supplied key separately, including chain, usage, and time. When using CryptXmlVerifySignature, retain the returned HRESULT instead of replacing it with error 1466 in application telemetry.
Recovery and prevention
Regenerate the signature from authoritative content only after identifying why validation changed. Do not accept the document by skipping signature checks. Producers should use a tested XMLDSIG library, stable element identifiers, explicit supported algorithms, and deterministic serialization. Consumers should limit external references and transforms, reject ambiguous duplicate IDs, and keep trust validation separate from mathematical signature verification.
Difference from a parse error
ERROR_XML_PARSE_ERROR means Windows could not parse the requested XML data. Error 1466 is specifically about XML signature processing and can occur after the document is syntactically valid. A valid cryptographic signature also does not by itself prove that the signer is trusted; certificate policy remains a separate decision.
Example
A deployment service verifies a signed policy document. An editor preserved all visible values but moved a signed element under a node with different namespace declarations. The XML still parses, yet canonicalization changes and the reference digest no longer matches. Restoring the original namespace context resolves 1466; disabling verification would have hidden a real integrity failure.
References
Looking for a different code? Search another status or error code.