| Previous | Next |
| STATUS_INVALID_KERNEL_INFO_VERSION | STATUS_HANDLE_REVOKED |
STATUS_INVALID_PEP_INFO_VERSION
The plug-in side of the PoFx registration contract has the wrong version
STATUS_INVALID_PEP_INFO_VERSION is specifically tied to the version of PEP_INFORMATION supplied during Platform Extension Plug-in registration. Microsoft documents this return from PoFxRegisterPlugin when PEP_INFORMATION.Version is invalid. It should be separated from STATUS_INVALID_KERNEL_INFO_VERSION, which concerns the kernel-information structure in the same registration relationship.
PEP_INFORMATION carries the PEP's notification callbacks and version data. The structure is part of a versioned interface between the platform plug-in and PoFx. An incorrect version can result from mismatched headers, stale private copies of WDK definitions, or a wrapper that initializes the wrong structure revision.
What to inspect
- The exact
PEP_INFORMATIONdefinition compiled into the failing PEP. - The
Versionvalue and callback table supplied toPoFxRegisterPluginor its extended form. - Build/deployment mixing between the PEP binary and platform support components.
- Any compatibility layer that serializes or copies the registration structure.
Do not infer a device power-policy failure from this status; registration has not established a valid PEP interface. Fix the structure contract first, then investigate device notifications or power-state behavior only after PoFx accepts the plug-in.
References
- Microsoft WDK: PoFxRegisterPlugin
- Microsoft WDK: PEP_INFORMATION
- Microsoft WDK: PoFxRegisterPluginEx
- Microsoft: Platform Extension Plug-ins
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.