| Previous | Next |
| STATUS_INVALID_PARAMETER | STATUS_NO_SUCH_FILE |
STATUS_NO_SUCH_DEVICE
Validate device identity and topology before retrying I/O
STATUS_NO_SUCH_DEVICE is most useful when treated as an identity or topology failure. The request names or retains a device target that is not available in the current configuration. That differs from STATUS_DEVICE_BUSY, where a present target refuses work temporarily, and from STATUS_DEVICE_UNRESPONSIVE, where communication with a target fails to produce a response.
Plug and Play is responsible for adapting the Windows device tree to hardware additions and removals. Storage also has explicit identifier descriptors and device unique identifiers that can be obtained during discovery. When a stale handle, cached path, or persisted device mapping is involved, compare the identity used by the failing request with the identities present after current enumeration.
Do not assume that rescanning is the fix. A rescan can confirm current topology, but software must still stop using stale device objects or old mappings. On multipath systems, also distinguish loss of one path from loss of the logical device itself.
What to inspect
- The device instance or storage identifier used when the handle or mapping was created.
- PnP arrival/removal events and storage path changes at the same timestamp.
- Whether a new enumeration produces the same stable device identity or a different device behind a reused symbolic path.
References
Looking for a different code? Search another status or error code.