0X00000BC1 printer has jobs queued – real fix

1. Printer still has pending jobs in the queue

The most common reason for 0X00000BC1 is simple: you've got documents sitting in the print queue that Windows hasn't flushed yet. This happens when you try to remove a printer, change its driver, or edit printer properties while there's still work lined up.

What's actually happening here is that the print spooler service holds onto job metadata until each document finishes printing or is explicitly canceled. Windows refuses to touch the underlying configuration while jobs exist — it's a safety measure to prevent corruption. You're not stuck, you just need to empty the queue.

How to clear the queue manually

1. Open Settings > Bluetooth & devices > Printers & scanners (or Devices and Printers in Control Panel).
2. Click the printer showing the error, then select Open print queue.
3. Right-click each job and choose Cancel. If nothing cancels, go to step 4.
4. In the print queue window, click Printer in the menu bar, then Cancel All Documents.

If jobs won't clear — and this happens more often than it should on Windows 11 — you need to stop the spooler service and delete the files by hand.

net stop spooler
del /q /f C:\Windows\System32\spool\PRINTERS\*
net start spooler

The del command wipes everything in the PRINTERS folder. Don't worry, those aren't backed up anywhere — they're temporary files. Once the spooler restarts, Windows rebuilds the queue empty. Now you can retry your operation.

One real-world trigger: someone clicks Print, the document fails with an Access Denied on a network printer, and the job stays stuck in the queue. Later they try to remove the printer and hit 0X00000BC1. The fix above handles it every time.

2. Corrupted print spooler holding orphaned jobs

If you've cleared the queue visually and through the filesystem but still see the error, the spooler itself is likely corrupted. The symptoms are identical — job listings show zero, but Windows still thinks jobs exist. This happens because the spooler's internal job database (stored in memory or in the registry) gets out of sync with the file system.

The fix is restarting the spooler with a full reset, not just a stop/start.

net stop spooler
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\Spooler" /v Environment /f
net start spooler

The reg delete command removes the printer environment key that Windows uses to track installed printers. On restart, the spooler recreates it clean. You'll need to re-add any network printers after this, but local printers usually reappear automatically.

I've seen this most often on Windows 10 version 22H2 after a failed print job from Adobe Reader — something about how Acrobat holds the file handle seems to trip up the spooler's job counter. The registry reset clears the phantom count.

3. Third-party print manager overriding the queue

Some enterprise environments run print management software — HP Universal Print Driver, PaperCut, or PrinterLogic are the usual suspects. These tools intercept the print queue and can hold jobs in a hidden state that Windows doesn't show in the UI. You'll see zero jobs in the queue but still get 0X00000BC1.

The fix: check the vendor-specific management console and manually release or delete those jobs. For HP Universal, that's in the HP Print Manager app. For PaperCut, log in to the admin interface and look for held jobs under the printer name.

If you can't find a console, stopping and restarting the spooler (as in cause #1) often flushes those hidden jobs too, because the third-party tool can't hold a reference after the spooler resets its process.

Skip trying to use PowerShell to force-remove jobs in this case — that only touches Windows-managed jobs, not the hidden ones from third-party software.

Quick-reference summary