Print Job Error 0x00000874: Fix That Stuck Job in Windows

That print job isn't going anywhere — here's the fix

You hit Cancel, nothing happens. You right-click the job, get 0x00000874 — This operation cannot be performed on the print job in its current state. I know this error is infuriating. It usually pops up when a job gets corrupted mid-print — maybe the network dropped, the printer ran out of paper, or you force-cancelled a job at the wrong moment. The job is stuck in limbo, and Windows refuses to touch it. Skip the dicking around with drivers or restarts. The real fix is clearing the spooler cache manually.

Step-by-step: clear the spooler cache

1. Press Windows Key + R, type services.msc, hit Enter.
2. Find Print Spooler in the list. Right-click it, select Stop. Leave the window open.
3. Press Windows Key + R again, type %systemroot%\System32\spool\PRINTERS, hit Enter.
4. That folder contains every stuck print job. Delete everything inside — all .SHD and .SPL files. Don't delete the folder itself, just its contents. If Windows says a file is in use, you didn't fully stop the spooler. Go back and make sure it's Stopped.
5. Back in the Services window, right-click Print Spooler, select Start.
6. Try printing again. The error should be gone.

That's it. You're done. The whole thing takes 90 seconds.

Why this works

The spooler is Windows' print traffic cop. It stores print jobs as files in that PRINTERS folder. When a job gets corrupted — say part of a PDF was missing when the spooler wrote it — Windows flags it as invalid. Any action on that job returns error 0x00000874. By deleting the files manually, you're wiping the slate clean. The spooler rebuilds that folder when it restarts, so safe to empty it.

Less common variations

If the above doesn't work, a few edge cases:

• Registry corruption: Open Registry Editor (regedit), go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers. Find your printer's subkey. Right-click it, select Delete. Reboot, then re-add the printer. This nukes any bad driver configs that might mimic the error.
• Driver stuck in sandbox: On Windows 10/11 21H2+, print drivers run in isolated mode. Sometimes that isolation process (PrintIsolationHost.exe) hangs. Open Task Manager, find that process, end it. Then stop and start the spooler again.
• Network printer authentication: If it's a network printer and Windows lost the session token, the spooler can't access remote spool files. Restart both the print server and your machine. Sounds dumb, but I've seen token expiry cause this exact error code.

Prevention

You can't stop every corrupt job, but you can reduce the odds:

• Don't print directly from a browser to cancel mid-stream. Save the PDF locally first, then print. Browsers send partial data if you cancel too fast.
• Keep your spooler folder on an SSD if possible. Slow mechanical drives can cause write delays that corrupt job files.
• Update your printer driver monthly — but only from the manufacturer's site, not Windows Update. I've seen WU push driver versions that trigger this error on Canon and Brother models specifically.
• If you see this error repeatedly, check your printer's firmware. HP and Epson released updates in 2023 that fixed spooler-handshake bugs tied to this error code.

That's the full picture. You'll be back to printing in under two minutes. If you're still stuck, drop a comment with your printer model and OS build — I've debugged this on everything from Windows 7 to the latest 24H2 preview builds.