Fix ERROR_DEVICE_REQUIRES_CLEANING (0x0000048d)

Your drive thinks it's dirty. This error means the heads need cleaning or the drive is failing. Don't just retry — clean first, then check if it's dying.

Quick answer: Run a cleaning cartridge through the drive. If that doesn't clear the error, the drive heads are probably worn out or the tape is bad.

This error (0x0000048D) shows up mostly on tape drives — LTO drives, DDS, or older DAT drives. What's actually happening here is the drive's internal sensor detected that the read/write heads have too much debris or oxide buildup. The drive refuses to operate until you clean it because dirty heads cause data errors and can damage tapes. You'll see this on Windows Server backup jobs, or when trying to read a tape in an external drive.

The error code is 1165 in decimal. Windows gives you this instead of ERROR_BUSY or ERROR_IO_DEVICE because the drive firmware is smart enough to ask for cleaning before it breaks something.

Step-by-step fix

Get the right cleaning cartridge. Each drive type needs its own cleaner. LTO-5 drive needs an LTO-5 cleaning cartridge. Using an LTO-6 cleaner in an LTO-5 drive won't work. Check the drive label or manual.
Insert the cleaning cartridge while the drive is powered on. The drive should see it automatically and start cleaning. This takes 30 seconds to a few minutes. You'll hear clicks and whirs — that's normal.
Remove the cleaning cartridge after the drive ejects it. Don't leave it inside. Cleaning cartridges have a limited number of uses (usually 20-50).
Try your data tape again. If the error is gone, you're done. If it comes back, the heads are still dirty. Try cleaning again with a fresh cartridge.
Still failing? The drive's cleaning cycle may have timed out or the heads are physically damaged. Run wmic tape drive get status in Command Prompt to check if Windows reports the drive as 'cleaning required' even after cleaning.

If cleaning doesn't help

Your drive might be dying. Here's how to tell:

Check the cleaning cartridge itself. If it's expired or already used up, it won't clean anything. Most LTO cleaning cartridges have a bar code that the drive reads — if it's been used 50 times, the drive ignores it.
Try a different tape. One bad tape can leave gunk on the heads. The drive might be clean but that one tape is shedding oxide. If the error disappears with a different tape, throw the bad tape away.
Check the drive's error log. Many enterprise drives (IBM, HP, Quantum) have a small web interface or SCSI command tool. Look for 'head usage' — if the drive has 20,000+ hours on the heads, they're worn. The cleaning won't fix worn heads.
Restart the server or reconnect the drive. Sometimes the error sticks in Windows even after the drive is clean. Unplug the USB or SAS cable, wait 10 seconds, plug it back in. This forces a re-enumeration.

Prevention

Don't let tapes sit in the drive when not in use. Dust gets in. Also, clean the drive every 200 hours of tape use — not when it throws errors. If you wait for the error, the heads are already getting damaged. Use a cleaning schedule in your backup software (most like Veeam or Backup Exec let you set recurring cleaning jobs).

One more thing: cheap tapes cause more head buildup. Stick to known brands (Fuji, Sony, HP) for LTO. Generic tapes shed more oxide and trigger this error faster.

If you keep seeing this error weekly even after cleaning, the drive is telling you it's dying. Replace the heads or buy a new drive. A $200 cleaning cartridge won't fix a worn drive.