What does HRESULT 0x80400003 (INPUT_E_PACKET) mean?

INPUT_E_PACKET

The scope of INPUT_E_PACKET is pointer packet, frame, and history validation. One or more fields in an individual pointer packet violate the input contract. Keep 0x80400003 beside the returning method because a wrapper can replace this distinction with a generic subsystem message.

Do not hide the original condition

INPUT_E_FRAME and INPUT_E_HISTORY arise after packets are grouped; this result means at least one packet is invalid on its own. Do not log only selected fields or the formatted message. A padding, size, or flag problem can be invisible in a simplified application log.

Subsystem context

Windows validates input at several nested levels. A packet describes one pointer observation, a frame groups simultaneous observations, and history links frames over time. The diagnostic task is to locate the first level at which identity, flags, timing, device information, or lifecycle becomes inconsistent; repairing only the last packet can leave an invalid frame or history chain unchanged.

The defect is local to a packet or its required field combination. Common classes include invalid flags, impossible button or contact state, missing coordinates, unsupported pointer type, inconsistent device identity, or a size/version mismatch in the submitted structure.

Evidence to preserve

• Complete structure bytes and declared structure size
• Pointer ID, frame ID, type, flags, coordinates, and timestamp
• Device handle and any HID-derived properties
• The first API validation result before wrapper conversion

Isolation procedure

Capture the submitted structures before Windows modifies counts or output buffers. Reduce the sequence from history to one frame and then to one packet while preserving the original pointer IDs, flags, and time base so the level that first fails remains observable.

1. Start from a known valid packet for the same pointer type.
2. Change one field at a time until the error reproduces.
3. Validate required flag combinations for DOWN, UPDATE, and UP transitions.
4. Check zero initialization and structure version against the target SDK and OS.

Technical references

• Microsoft: COM error codes for Input and graphics.
• Microsoft: Pointer Input Messages and Notifications.
• Microsoft: POINTER_INFO structure and pointer lifetime.
• Microsoft: GetPointerFrameInfoHistory.
• Microsoft: Interaction Context API.