Fix Printer 'Operation failed' Error (Spooler Stuck)

You hit Print, the little printer icon pops up in the notification area, then nothing. Or you open the print queue and see a document stuck with an error that reads "Operation failed". Sometimes you get a specific code like 0x00000bc4 or 0x00000709. This happens most often when you're printing from an app that holds the printer handle open—like Microsoft Word or Excel—or after a Windows update tweaks the printer driver. I had a client last month whose entire office stopped printing at 9 AM because one user's stuck job froze the shared queue.

Why this happens

Windows routes every print job through the Print Spooler service. That service takes the data from your app, writes it to a temporary file on disk, and then sends it to the printer. When the spooler gets tangled—either because a driver hangs, a previous job didn't finish, or the spooler itself crashed—new jobs pile up and eventually throw an "Operation failed" message.

The root cause is usually a corrupted spooler cache or a driver that's stuck in memory. The spooler holds onto the temp files and won't let go. Think of it like a traffic jam—the first car (your stuck job) blocks the intersection, and everyone behind it just sits there. The fix is to clear the jam, which means stopping the spooler, deleting the temp files, and starting it fresh.

The fix: clear the spooler and restart

Here's the exact process that works 90% of the time. Do this on the machine that's having the problem, or on the server if the printer is shared.

First, close any app that has a print dialog open. Word, Excel, your browser—all of them. This releases the printer handle.
Press Win + R to open the Run box, type services.msc, and hit Enter.
Scroll down to Print Spooler. Right-click it and select Stop. Wait a few seconds.
Now open File Explorer and go to this folder: C:\Windows\System32\spool\PRINTERS
Delete everything inside that folder. Don't worry, these are just temp files for pending print jobs. If you get a permission error, you didn't stop the spooler properly—go back and make sure it's stopped.
Go back to the Services window, right-click Print Spooler again, and choose Start.
Now go to your printer in Settings > Bluetooth & devices > Printers & scanners (or Control Panel > Devices and Printers). Right-click the printer and select See what's printing. The queue should be empty.
Try printing a test page. If that works, you're golden.

If it still fails: the driver is the culprit

Clearing the spooler fixes the jam, but if the driver is rotten, the next print job will crash it again. I've seen this more times than I can count. The driver gets corrupted after a Windows feature update, or a vendor's "enhancement" breaks something. Here's what to check:

Remove and re-add the printer. Go to Settings > Bluetooth & devices > Printers & scanners, click the printer, hit Remove device. Then add it back using the same method. If it's a network printer, make sure you know its IP address.
Install the latest driver from the manufacturer's site, not from Windows Update. Windows Update often gives you a generic driver that lacks the full features. For HP, Brother, or Epson, go to their support page, search for your model, and download the full driver package.
Run the built-in troubleshooter as a last resort—it rarely fixes the root issue but sometimes it clears a stuck device setting. Press Win + I, go to System > Troubleshoot > Other troubleshooters, and run Printer. Don't waste too much time here.

When the problem is on the network

If you're connecting to a shared printer on another PC, the spooler on that host machine is the one that's stuck. You'll need to run the same steps on the host. If the host is a server, you might need admin rights. And if you're using a network printer with its own IP address (not shared through a PC), the spooler issue is on your machine only—skip the server part.

Still broken? Try a clean boot

Sometimes third-party software interferes with the spooler. I had a client where a backup tool was locking the spooler files. To check, do a clean boot:

Press Win + R, type msconfig, and hit Enter.
Under the Services tab, check Hide all Microsoft services, then click Disable all.
Under the Startup tab, click Open Task Manager and disable every startup item.
Restart the PC, then try printing. If it works, re-enable services and startup items one by one until you find the offender.

This is diagnostic only—don't leave your PC in clean boot mode forever. Once you find the culprit, uninstall or update that software.

Last resort: delete the printer and start over

If none of that works, I'd nuke the printer from Windows entirely. Remove it, delete the driver from Print Server Properties (under the Drivers tab), then reboot and reinstall. This wipes out any hidden driver remnants that survive a normal removal. It's a pain, but I've rescued systems this way that were about to get a flat-out OS reinstall.

The spooler is the heart of Windows printing. Keep it clean and you'll avoid most of these headaches. And when a client calls you with an "Operation failed" error, you now know exactly what to do.