| Previous | Next |
| STATUS_UNKNOWN_REVISION | STATUS_INVALID_OWNER |
STATUS_REVISION_MISMATCH
Both sides may understand versions, but the selected revisions cannot work together
STATUS_REVISION_MISMATCH should be separated from STATUS_UNKNOWN_REVISION. A mismatch can occur when the revision values are individually meaningful but incompatible with the receiving component, the target structure, or the running platform. The evidence to collect is therefore both sides of the version contract rather than only the rejected number.
HidRegisterMinidriver returns this status when the HID revision in HID_MINIDRIVER_REGISTRATION is unsupported by the HID class driver. StorPortInitialize documents it for an initialization structure version invalid for the current operating system. ACL helpers use it when the requested ACE revision is not compatible with the ACL revision. RtlVerifyVersionInfo also uses the value as a comparison result when the running OS does not satisfy the requested version condition.
Diagnose the exact contract that generated the status. Log the producer revision, consumer or platform version, and structure size. Do not assume the status always means “upgrade Windows”: the correct repair can be to select an older registration revision, rebuild against the target WDK contract, or avoid emitting a newer ACE form into an older ACL revision. A compatibility decision should follow the specific API documentation.
What to inspect
- Identify both revision levels or the revision and runtime version being compared.
- Check the structure initialization macro and WDK/SDK used by the producer.
- Use a documented downgrade or capability path; do not modify a revision field without changing the associated layout.
References
- Microsoft: HidRegisterMinidriver
- Microsoft: StorPortInitialize
- Microsoft: RtlAddAccessAllowedAce
- Microsoft: RtlVerifyVersionInfo
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.