Fix Printer Spooler Keeps Stopping on Windows 10/11

So you're in the middle of printing a 40-page contract and suddenly the printer goes silent. You open Devices and Printers, and everything's grayed out. Then a bubble pops up: “The Spooler Service has terminated unexpectedly.” And it keeps coming back, or it won't start at all. That's the classic spooler crash loop. I see this at least once a month at small businesses—usually after a Windows update or when someone jammed a huge PDF print job and then tried to cancel it.

What's actually happening

Windows uses a background service called Print Spooler to manage all print jobs. Every document you send gets spooled to a temporary file on disk, then fed to the printer. When the spooler crashes, it usually means one of those temp files is corrupt, or a printer driver has a bug that makes the service choke. The fix is almost always the same: stop the service, clear out the junk, restart it. If that doesn't stick, you reinstall the driver.

The fix: clear the queue and restart

This works for Windows 10 and 11, and it doesn't require any registry tweaks. Follow the steps in order.

Stop the spooler service. Open an admin Command Prompt (right-click Start, choose “Terminal (Admin)” or “Command Prompt (Admin)”). Type:
```
net stop spooler
```
If it's already dead, you'll get an error—that's fine, move on.
Delete the print queue files. The spooler stores jobs in C:\Windows\System32\spool\PRINTERS. Open File Explorer, paste that path in the address bar, and press Enter. Select everything in that folder and delete it. If Windows says “file in use,” you didn't stop the service properly—go back and make sure.
Restart the spooler. Back in the command prompt, type:
```
net start spooler
```
Check if the error is gone. Print a test page from Devices and Printers.

That clears 80% of cases. The corrupt file is gone, and the service starts clean. But if it crashes again within a day, the problem is the driver, not the queue.

When the queue isn't the problem

Last month I had a client whose HP LaserJet kept killing the spooler every time they printed a PDF from Adobe. The driver was the culprit—version 2321 had a known bug with Windows 11 23H2. Here's how to fix that.

Step 1: Remove the printer and driver entirely

Go to Settings > Bluetooth & devices > Printers & scanners. Click the printer, then Remove device. Then you need to purge the driver files. Open a command prompt and run:

printui /s /t2

That opens the printer server properties. Go to the Drivers tab, find the printer driver, select it, and hit Remove. When it asks if you want to remove the driver package, say Yes.

Step 2: Delete leftover driver files

Reboot, then check C:\Windows\System32\spool\drivers\x64 (or x86 on older systems) for any folders named after the manufacturer, like HP or Canon. Delete those folders if they exist. They're orphaned remnants that can still cause the spooler to choke.

Step 3: Reinstall the printer with the fresh driver

Plug in the printer (or connect it to the network), then go back to Settings > Printers & scanners and hit Add device. Windows will find it and install the latest driver from Windows Update. If that fails, download the driver directly from the manufacturer's site. For HP, use the HP Smart app—it actually works. For Canon, grab the full driver package, not the “lite” version.

After install, print a test page. Don't skip the test—it verifies the spooler holds up.

Still crashing? Check these

If the spooler still dies after a clean install, you've got a deeper issue. Here's what I check next:

Corrupt system files. Run sfc /scannow in an admin prompt. It takes a few minutes, but it catches wonky DLLs that can break the spooler.
Third-party antivirus interference. Some security suites (looking at you, McAfee) try to sandbox the spooler and end up killing it. Temporarily disable the AV and test. If it stops crashing, whitelist the spooler service in your AV settings.
Broken print driver from Windows Update. Check Settings > Windows Update > Update history. If the crash started after a recent update, roll back the printer driver via Device Manager: right-click the printer, go to Properties > Driver, and hit Roll Back Driver.
Event Viewer details. Press Win+R, type eventvwr, and look under Windows Logs > System for “PrintSpooler” errors. The error code (like 0x800706b9) tells you if it's a permissions or dependency issue. If you see that specific code, it's often a missing service dependency—run sfc /scannow again and also check that the HTTP Print service is set to Manual.

One last thing: if you're on a domain network, check if your IT admin has applied a group policy that restricts the spooler (a common security hardening after PrintNightmare). That's beyond your control, but at least you'll know it's not your machine.

That's the whole deal. Clear the queue, nuke the driver, reinstall clean. You'll be back to printing in under twenty minutes.