| Previous | Next |
| STATUS_NO_SUCH_FILE | STATUS_END_OF_FILE |
STATUS_INVALID_DEVICE_REQUEST
The target device does not implement this request
A handle can refer to the correct device while the submitted operation is still unsupported. The request may use the wrong IOCTL, transfer method, file-object state or device role, or it may have been sent to a filter or control device instead of the intended functional device.
Do not convert this status into a generic retry. Record the complete request contract and determine which driver returned it. For IOCTLs, verify the device type, function number, access bits and input/output buffer rules. A different firmware revision can expose a different feature set even with the same broad device class.
What to inspect
- Log major/minor function, IOCTL value, buffer lengths and target device stack.
- Find the first driver that completes the request with this status.
- Compare the request with the documented interface and negotiated device capabilities.
References
- Microsoft: Framework request objects
- Microsoft: Device objects and device stacks
- Microsoft: Using NTSTATUS values
- Microsoft Open Specifications: NTSTATUS values
- ReactOS source: IRP allocation and completion
Looking for a different code? Search another status or error code.