| Previous | Next |
| STATUS_MESSAGE_LOST | STATUS_REQUEST_CANCELED |
STATUS_INVALID_MESSAGE
The ALPC message layout is not valid for this operation
ALPC messages contain a native port-message header plus operation-specific data and optional attributes. Validation can fail when lengths are inconsistent, alignment is wrong, the message type is inappropriate, an attribute mask does not match the attached buffer, or a message is reused after its ownership state changed.
Do not fix this by increasing an arbitrary buffer size. The total length, data length, architecture-specific alignment, attribute allocation, and exact send or reply API must agree. Private native structures can also vary between Windows versions, so hard-coded layouts are especially fragile.
What to inspect
- Log header fields, total allocation size, architecture, message type, and every enabled ALPC attribute.
- Verify that data length excludes the header while total length includes the complete message representation expected by the API.
- Initialize attribute buffers with the matching native helper and avoid copying pointers between processes.
- Compare the structure definitions against the target Windows build rather than an unrelated SDK snapshot.
References
- Microsoft Open Specifications: NTSTATUS values
- System Informer PHNT: native ALPC definitions
- Microsoft Windows SDK metadata: ntstatus.h
Looking for a different code? Search another status or error code.