Printer Spooler Error: The Fix for 'Operation Could Not Be Completed'
This error usually means a corrupted spooler or driver mismatch. I'll show you the quick fix that works 90% of the time.
Yeah, that error is a pain. You try to print something or open the printer properties, and Windows throws up 'Operation could not be completed (error 0x00000709)'. I've dealt with this on hundreds of machines — it's almost always a bad print job stuck in the spooler or a broken driver.
First, the fix that works every time
Don't waste time with the 'Troubleshoot printer' button. It rarely helps. Open an admin Command Prompt (right-click Start > Windows Terminal (Admin) or cmd as admin), and run these commands one at a time:
net stop spooler
del /q /f /s %systemroot%\System32\spool\PRINTERS\*
net start spooler
That stops the print spooler, deletes every stuck print job from the PRINTERS folder, and restarts the service. No reboot needed. Now try to print again.
Why this works
The spooler stores print jobs as temporary files in C:\Windows\System32\spool\PRINTERS\. If a job gets corrupted — usually from a driver crash, a network timeout, or a user closing an app mid-print — the spooler can't process it. It hangs, and then any new print attempt fails with that error. Clearing the folder forces the spooler to start fresh. The /q flag suppresses prompts, /f forces deletion of read-only files, and /s handles any subfolders (though normally there aren't any).
Less common variations
Sometimes the files won't delete because the spooler didn't actually stop. Check Task Manager to confirm the spoolsv.exe process is gone. If it's still running after net stop spooler, you might have a service that auto-restarts it — like a third-party printer management tool (HP, Brother, Canon's port monitoring software). Kill the process manually from Task Manager, then delete the files.
Another variation: The error pops up only when connecting to a network printer, not a local one. This usually points to corrupted printer drivers on the client machine. After clearing the spooler, remove the printer completely:
- Open Settings > Bluetooth & devices > Printers & scanners
- Click the problem printer, then click 'Remove device'
- Run the spooler clear commands above again
- Add the printer back fresh
If that still fails, you'll need to nuke the driver cache. Open Device Manager, go to View > Show hidden devices, expand Print queues, right-click the printer, and select Uninstall device. Check 'Delete the driver software for this device' if prompted. Then add the printer from scratch.
On rare occasions — especially with legacy printers (like HP LaserJet 4000 series on Windows 11) — the driver itself is incompatible. Download the latest driver from the manufacturer's site. Yes, the built-in Windows driver might work, but it often causes this exact error when it tries to negotiate spooler settings. A proper vendor driver fixes it.
How to prevent it from coming back
Three things:
- Don't close apps mid-print. Wait for the print job to finish before closing Word, Excel, or whatever you're printing from. Abrupt app shutdowns orphan spool files.
- Keep printer drivers updated. Set your manufacturer's update tool to auto-check. Old drivers misbehave with Windows updates.
- Limit print queue size. If you share a printer over a network, configure the spooler to 'Start printing after last page is spooled' instead of 'Immediately'. It prevents half-printed jobs from jamming the queue. You'll find this setting in Printer Properties > Advanced tab.
That's it. The spooler clear is your go-to. If you're still stuck after all that, the printer itself might have a hardware jam or network issue — check the printer's front panel for error lights. But for the software side, you're covered.
Was this solution helpful?