0X80000027

Fix STATUS_CLEANER_CARTRIDGE_INSTALLED (0x80000027)

This error means a cleaning tape is stuck in your tape library. Remove it or replace it with a data tape. I've seen this lock up backups for days.

Quick answer: The tape library sees a cleaning cartridge in a drive or slot. Remove the cleaning tape, or replace it with a data tape. If it won't eject, use tapeutil or the library's web interface to force it.

What's actually happening here

The error code 0x80000027 — STATUS_CLEANER_CARTRIDGE_INSTALLED — shows up when Windows or the backup software detects that a cleaning cartridge is currently loaded in a tape drive or sitting in a slot that the library thinks is a data tape. This isn't a drive failure. It's the library's firmware saying, 'Hey, there's a cleaning tape where I expected a real backup tape.'

I had a client last month whose entire backup job chain died because someone accidentally loaded a cleaning cartridge into slot 12 instead of a data tape. The library flagged it, and every subsequent backup request failed with this error. The cleaning tape doesn't have a valid backup header, so the drive rejects it.

Fix steps

  1. Identify which slot or drive has the cleaning tape. Open the tape library management software (HP Library & Tape Tools, IBM Tape Diagnostic Tool, or the web GUI). Look for a slot or drive showing a cleaning cartridge status. Check the element status report.
  2. Eject the cleaning tape manually. If it's in a drive, press the physical eject button on the drive (if accessible). If it's in a slot, use the library's 'move medium' command to move it to an I/O station or mail slot.
  3. Force-eject via command line (if buttons fail). Open an admin command prompt or PowerShell on the backup server. Use tapeutil (if available from the tape vendor) or ibmtapeutil. Example: tapeutil -f \\.\Tape0 eject. If the library has SCSI commands, use changer.exe (from Windows Server) — changer exchange can move the medium out.
  4. Replace the cleaning cartridge with a data tape. Once ejected, insert a real backup tape into the empty slot. Restart the backup service or job.
  5. Clear the error in Windows. Open Computer Management → Device Manager → Tape drives. Right-click the tape drive and select 'Scan for hardware changes'. This sometimes clears the cached error state.

If the main fix doesn't work

  • Reboot the tape library. Power-cycle the whole library (not just the server). Wait 2 minutes for the robotics to initialize, then try the eject again.
  • Use the library's front panel. On HP or IBM libraries, you can navigate to 'Commands' → 'Unload Medium' or 'Move Cartridge' using the LCD panel. I've done this on an HP MSL2024 — it's clunky but works.
  • Check for firmware bugs. Some HP LTO-5 libraries had a known bug where cleaning tapes were misidentified as data tapes. Update the library firmware (check the vendor support site). Don't skip this — I had an IBM TS3100 that needed a firmware patch to handle cleaning cartridge detection correctly.
  • Last resort: physically open the library. If the tape is stuck in a drive and won't eject, power off the library, open the door, and manually remove the cartridge by pressing the drive's release mechanism (usually a spring-loaded lever). Only do this if you're comfortable — it can void warranty.

Prevention tips

  • Label cleaning cartridges clearly. Use a bright sticker or colored tape. I keep mine in a separate storage case, never in the library.
  • Set library slot reservations. In the library's web interface, designate specific slots for cleaning tapes only. Most libraries let you mark slots as 'cleaning' — that prevents backup software from trying to write to them.
  • Automate cleaning schedules. Use the library's built-in auto-clean feature instead of manual insertion. Set it to run after a certain number of tape loads (e.g., every 100 loads). This reduces human error.
  • Train your ops team. Seriously. The person who loaded that cleaning tape into slot 12 last month didn't know what they were doing. A 5-minute walkthrough can save you a weekend of debugging.
Related Errors in Windows Errors
Service not started: Task Scheduler (Event ID 101) Task Scheduler Service Won't Start — Fix in 5 Minutes 0XC00000DB Fix STATUS_CANT_TERMINATE_SELF (0xC00000DB) on Windows 0X00000A3A Fix 0X00000A3A: Workstation name already in use 0X0000216D Fix: ERROR_DS_MACHINE_ACCOUNT_QUOTA_EXCEEDED (0x216D) domain join

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.