Fix 0XC00000C8 Print Canceled Error (Spooler Reset)

Print job dies with STATUS_PRINT_CANCELLED when a driver or spooler kills it mid-send. Usually a stale spool file or driver hiccup. Restart spooler and clear the queue — that handles 90% of cases.

Quick answer: Stop the spooler, delete everything in C:\Windows\System32\spool\PRINTERS, restart the spooler, and retry your print job.

That error — STATUS_PRINT_CANCELLED (0XC00000C8) — means the print spooler stopped processing your file before it reached the printer. The culprit here is almost always a corrupted spool file that's stuck in the queue, or a driver that's choking on a specific print job. I've seen it on Windows 10 and 11, with HP, Brother, and Canon printers alike. It's not a hardware failure, and it's not a network issue 99% of the time. It's the spooler getting confused and killing the job.

Here's the thing: the spooler is a fragile piece of Windows plumbing. It holds every print job in a temporary folder, and when a job gets interrupted — maybe the printer went offline, a cable got bumped, or the driver hit a bug — the spooler can't recover. It just cancels everything. The fix is to give it a clean slate.

Fix Steps (in order)

Stop the Print Spooler service. Open an elevated Command Prompt (right-click Start > Terminal as Administrator) and run:
```
net stop spooler
```
Wait for it to say "stopped." If it hangs, you can force it with taskkill /f /im spoolsv.exe — but that's rare.
Clear the queue folder. In the same admin terminal:
```
del /Q /F C:\Windows\System32\spool\PRINTERS\*
```
If you get an access denied, you didn't stop the service properly. Go back and check.
Restart the spooler.
```
net start spooler
```
You should see "The Print Spooler service was started successfully."
Retry your print job. Now print the same document. If it goes through, you're done. This probably took you 2 minutes.

If the spooler reset doesn't fix it

Sometimes the spooler clears but the error comes right back. That means the driver is the problem. Here's the next step:

Remove the printer driver completely. Open devmgmt.msc, find your printer under "Print queues," right-click, and choose "Uninstall device." Check the box that says "Delete the driver software for this device."
Reinstall the driver. Go to the manufacturer's support site — not Windows Update, not a third-party driver updater. Download the latest full driver package for your exact model and Windows version. For HP, that's the HP Smart app. For Brother, the full driver pack. For Canon, the IJ printer driver.
Re-add the printer. Settings > Bluetooth & devices > Printers & scanners > Add device. Choose your printer and let Windows detect it.

If that still fails, check for third-party print management software. Tools like PaperCut or printer vendor utilities (HP Easy Start, Epson Status Monitor) can interfere. Disable them temporarily and see if the error disappears. I've seen those apps hold the spooler hostage more than once.

Alternative fixes that sometimes work

Run the printer troubleshooter. It's not my first choice, but it can reset the spooler and driver registry keys. Hit Win + I > System > Troubleshoot > Other troubleshooters > Printer.
Check the spooler dependencies. Open services.msc, find "Print Spooler," right-click > Properties. Ensure it's set to "Automatic" and that dependencies (like HTTP and RPC) are running. Rarely the issue, but worth a glance.
Update Windows. If you're on a stale build, a spooler bug could've been patched. Windows 11 22H2 had a known spooler crash issue fixed in a 2023 update.

Prevention tip

The single best way to avoid this error is to never let the spooler pile up junk. If a print job fails, don't just send it again — check the queue first. Right-click the printer in Settings and "Open Print Queue," then cancel any stuck jobs. Also, if you're using a USB printer, avoid yanking the cable mid-print. That's the number one trigger I see in the field. And keep your drivers updated — but only from the manufacturer's site, not random updater tools that'll do more harm than good.

One more thing: if this happens on a shared network printer, check the print server. The spooler on the server might need the same reset. You can't fix a server-side issue from your workstation.