| Previous | Next |
| ERROR_DEVICE_REINITIALIZATION_NEEDED | ERROR_DEVICE_DOOR_OPEN |
ERROR_DEVICE_REQUIRES_CLEANING
The device reports that cleaning is required.
ERROR_DEVICE_REQUIRES_CLEANING has value 1165 (0x48D). It is a device-reported maintenance condition, commonly relevant to tape drives and automated libraries. The code should be handled as a physical-service requirement rather than hidden by repeated read, write, load, or unload retries.
Why the condition matters
Contaminated heads or a drive's internal cleaning threshold can cause increasing read/write retries, reduced throughput, and media errors. The device is providing an actionable warning before or alongside more general I/O failures. Ignoring it can make later data-integrity incidents harder to attribute.
Information to collect
- drive and library serial numbers, firmware, and logical drive identifier
- media volume tag loaded when the condition appeared
- device status, cleaning-request flag, and preceding sense or I/O events
- mount count, operating hours, and last successful cleaning when available
- identity and usage history of the cleaning cartridge
Separating drive identity from slot identity is important in multi-drive libraries. A cleaning request follows the affected drive even if the cartridge is moved elsewhere.
Maintenance response
- finish or stop the active operation according to the device vendor's guidance
- reserve the affected drive so new data jobs do not use it
- load an approved cleaning cartridge through the library's supported procedure
- confirm that the device clears the cleaning condition afterward
- return the drive to service only after a basic load/read diagnostic succeeds
Cleaning media has a finite service life. A worn or incompatible cleaning cartridge may fail to clear the condition, so record its identifier and remaining-use information instead of cycling it indefinitely.
When cleaning does not solve it
If 1165 returns immediately after a documented cleaning cycle, inspect the vendor event log and escalate for hardware service. The sensor or head assembly may be faulty, the cleaning medium may be expired, or another drive problem may be represented by the maintenance flag.
Automation recommendations
Library management software can schedule a cleaning workflow, but it should use reservations and explicit state transitions: requested, cleaning media allocated, cycle running, verification, and completed or failed. Do not let several backup jobs independently load the same cleaner. Alerting should identify the physical drive and whether data jobs have been paused.
Related codes
ERROR_IO_DEVICE describes a failed I/O request without prescribing cleaning. ERROR_DEVICE_REINITIALIZATION_NEEDED means the device's operational state must be rebuilt after hardware errors. ERROR_DEVICE_DOOR_OPEN is an interlock condition. Error 1165 is specifically the device's request for cleaning maintenance.
Example
A tape drive completes backups but its retry count rises and the next mount reports 1165. The scheduler removes that drive from the pool, loads a valid cleaning cartridge once, verifies that the maintenance flag clears, and then runs a test read. This controlled response preserves the original evidence and avoids repeatedly exposing production tapes to a degraded drive.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: IOCTL_CHANGER_GET_STATUS
- Microsoft: Device Management Control Codes
Looking for a different code? Search another status or error code.