Printer Spooler Stuck: Fix in 30 Seconds or 15 Minutes

Why the Printer Spooler Stops

When a print job gets corrupted—usually from a oversized PDF, a bad driver, or a network interruption—the spooler service (spoolsv.exe) crashes. Windows then shows the "Spooler subsystem app has stopped working" dialog. The fix is to restart the service and clear the stuck jobs. Here's the order I'd attack it.

30-Second Fix: Restart the Print Spooler Service

This works about 60% of the time. You're just bouncing the service back up.

1. Press Win + R, type services.msc, hit Enter.
2. Scroll down to Print Spooler. Right-click and select Restart.
3. If the service is already stopped, right-click and Start it.

Why it works: Corrupted jobs live in memory. Restarting the service flushes that memory. But if the corrupt job was still in the queue on disk, it'll crash again on the next print. That's the next fix.

5-Minute Fix: Clear the Print Queue Manually

If restarting didn't stick, the queue has a stuck job on disk. You need to delete it.

1. Stop the spooler service first: Open Command Prompt as admin and run net stop spooler.
2. Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS.
3. Delete everything in that folder. Don't worry—these are just pending print jobs, not system files.
4. Restart the spooler: net start spooler.

What's actually happening here: The spooler saves print jobs as .SHD and .SPL files in that folder. A corrupt file prevents the whole service from starting. Deleting them clears the blockage. This also solves the "print queue won't clear" problem you see when jobs are stuck with "Deleting — Printed" status.

15+ Minute Fix: Replace Corrupt Spooler Registry or Drivers

If you still see the error after clearing the folder, something deeper is wrong. Two common causes: a corrupt registry key or a bad printer driver.

Fix 1: Rebuild the Spooler Registry Key

The spooler's registry can get corrupted after repeated crashes. Here's the surgical approach:

1. Open Registry Editor (regedit) as admin.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler.
3. Right-click the Spooler key, choose Export to back it up.
4. Delete the Spooler key entirely.
5. Reboot. Windows will recreate the key with defaults.

Skip this if: You're not comfortable in regedit. The default key is usually fine—corruption here is rare. I've only seen it after a failed printer driver install or a malware cleanup.

Fix 2: Remove and Reinstall All Printer Drivers

Bad drivers are the real culprit behind spooler crashes that keep coming back. Here's how to nuke them cleanly:

1. Open Devices and Printers. Right-click each printer and select Remove device.
2. Open Print Server Properties: In the Printers window, click Print server properties in the toolbar.
3. Go to the Drivers tab. Select each driver and Remove it. If it says "in use", reboot and try again.
4. Unplug the printer. Restart Windows.
5. Reinstall your printer driver fresh from the manufacturer's site. Don't use Windows Update—it often pulls stale versions.

Why step 3 matters: Removing a driver through Devices and Printers leaves the driver binaries in the driver store (%WINDIR%\System32\DriverStore). Windows will keep loading them. Removing from Print Server Properties actually deletes them from the store. This is the difference between a temporary fix and a permanent one.

One real-world scenario: I once spent an hour chasing a spooler crash on Windows 10 22H2 that only happened when printing from Adobe Acrobat. Turned out the Adobe PDF driver was conflicting with a Canon driver. Removing both and reinstalling the Canon one first fixed it. Order matters: install the system driver before any PDF virtual driver.

When to Give Up and Use a Different Printer

If none of this works, try printing to a different printer on your network or a virtual printer like "Microsoft Print to PDF". If that works fine, the issue is specific to your printer driver or hardware. If even PDF printing crashes the spooler, you've got a corrupted Windows component. In that case, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system files. That's your last resort before a repair install of Windows.