| Previous | Next |
| WU_E_METADATA_XML_MISSING | WU_E_METADATA_XML_MODE_MISSING |
WU_E_METADATA_XML_FRAGMENTSIGNING_MISSING
WU_E_METADATA_XML_FRAGMENTSIGNING_MISSING means the XML configuration did not include the fragment-signing section needed to verify metadata fragments.
Why it matters
- This is a server-side metadata configuration issue more than a local update-cache issue.
- Check the update source that supplied the configuration and whether it supports the expected metadata-signing format.
- Do not disable metadata verification to make the scan continue; correct the catalog or service configuration instead.
Fragment signing is metadata-integrity configuration
Windows Update integrity telemetry explicitly refers to FragmentSigning data and uses identifiers from that data when reporting certificate failures. This code says the required fragment-signing configuration is absent from XML, so the failure is in metadata structure before a normal installation result can be produced.
For a managed or private update source, capture the update revision and service GUID and compare the metadata returned for that revision with a successful source. If synchronization was interrupted, verify the synchronized metadata before touching client package caches. A client-side retry can obtain corrected metadata after the server is fixed, but it cannot manufacture missing signing configuration.
References
References
- Microsoft: FragmentSigning fields in Windows Update integrity events
- Microsoft Open Specifications: update metadata synchronization
Looking for a different code? Search another status or error code.