Site icon EfmSoft

What does HRESULT 0x80400006 (INPUT_E_DEVICE_INFO) mean?

 
Previous Next
INPUT_E_HISTORY INPUT_E_TRANSFORM

INPUT_E_DEVICE_INFO

The scope of INPUT_E_DEVICE_INFO is pointer-device metadata and capabilities. Windows could not obtain the device metadata needed to interpret the pointer data. Keep 0x80400006 beside the returning method because a wrapper can replace this distinction with a generic subsystem message.

Subsystem context

A pointer identifier is interpreted through device metadata supplied by the input stack. Capabilities such as contact dimensions, pressure, orientation, physical scale, and HID usage can be optional, but values that are advertised must still satisfy their units and ranges. A stale device record after removal or session change is different from a live device that reports one malformed property.

The packet may contain an identifier, but the pipeline also needs a live and compatible device record. Removal, stale handles, driver failure, session changes, or unsupported synthetic devices can break that lookup.

Do not hide the original condition

INPUT_E_DEVICE_PROPERTY means a particular property is absent or malformed after device information was reached; this code means the broader device-information lookup failed. Do not retain device handles indefinitely or map a new device onto a stale cached record merely because the numeric handle was reused.

Evidence to preserve

  • Device handle or source identifier and Plug and Play instance ID
  • Device arrival/removal timestamps and session or desktop
  • Pointer type and API used to obtain device information
  • SetupAPI, HID, or input-service error preceding the HRESULT

Isolation procedure

Compare the same property query on the same physical device before and after reenumbering, resume, or reconnect. Then compare a second device without changing the application build; this separates device-specific metadata from caller structure and version errors.

  1. Query the device before starting the interaction.
  2. Repeat with a known built-in mouse, touch, or pen device.
  3. handle device removal by ending affected pointer lifetimes.
  4. Recreate cached device mappings after session, desktop, or hot-plug changes.

Technical references


Looking for a different code? Search another status or error code.

Exit mobile version