| Previous | Next |
| ERROR_BUS_RESET | ERROR_NO_UNICODE_TRANSLATION |
ERROR_NO_MEDIA_IN_DRIVE
no media in drive.
ERROR_NO_MEDIA_IN_DRIVE means that the device is present, but no readable removable medium is currently loaded. In this case, the decisive context is optical, tape, floppy, card-reader, and removable-storage operations, together with device identity, drive readiness, door/load state, and library slot assignment.
Where the result appears
- optical, tape, floppy, card-reader, and removable-storage operations.
- backup jobs waiting for a cartridge.
- applications probing empty drive letters.
- library workflows before media insertion completes.
Typical causes
- the drive is empty.
- the media is still loading, ejecting, or not seated.
- the wrong library slot or device was selected.
- hardware or firmware failed to detect inserted media.
Evidence to collect
- device identity, drive readiness, door/load state, and library slot assignment.
- operator or robotics actions and timestamps.
- sense data and device event logs.
- whether the application selected a drive path rather than a mounted volume path.
For this condition, begin the investigation with device identity, drive readiness, door/load state, and library slot assignment. Correlate it with operator or robotics actions and timestamps and check whether the drive is empty. Capture the original this result immediately after the failing call so later cleanup does not replace the thread-local error value.
Handling and recovery
Prompt for or load the expected medium and verify its identity before resuming. Avoid rapid polling that keeps a device or library busy; use device notifications or bounded backoff. Distinguish an empty drive from an absent or failed device.
Any retry policy for this Win32 error should be tied to evidence that the media is still loading, ejecting, or not seated has changed. Before another attempt, verify sense data and device event logs. If hardware or firmware failed to detect inserted media still applies, stop the retry sequence and preserve the first diagnostic event.
Common misinterpretation
The drive itself can be installed and healthy. The error refers to the removable medium, not device enumeration.
Guidance for developers
When surfacing this result through another layer, retain its Win32 domain, numeric value, and the operation described by backup jobs waiting for a cartridge. A useful telemetry record also includes whether the application selected a drive path rather than a mounted volume path. For the-related handling, decisions must use the numeric value and documented API contract rather than localized wording.
A focused test should reproduce the condition in which the wrong library slot or device was selected, assert this result, and confirm that the program releases resources associated with applications probing empty drive letters. The recovery test should also verify that device identity, drive readiness, door/load state, and library slot assignment is refreshed before the operation resumes.
References
Looking for a different code? Search another status or error code.