Spooler subsystem app has stopped working

Print spooler keeps stopping? Here's the real fix

Windows Errors Intermediate 👁 1 views 📅 May 29, 2026

Your print queue dies mid-job or Windows keeps saying the spooler stopped. Usually a corrupt driver or a hung print job.

You're in the middle of printing invoices and suddenly Windows pops up: "Spooler subsystem app has stopped working." Or maybe the printer queue shows a document stuck at "Deleting" for ten minutes. This happens most often when a network printer driver crashes mid-job, or when a corrupt print job gets stuck in the queue. I had a client last month whose entire print queue died because a bad HP universal driver loaded a wrong DLL. The fix isn't complicated, but you have to be surgical.

What's actually happening

The print spooler (spoolsv.exe) is a Windows service that holds your print jobs and sends them to the printer. When a driver or a corrupt job causes a crash, the service stops. Windows tries to restart it automatically, but if the bad job sits in the queue, it crashes again immediately. That's why you see the error pop up over and over.

Step-by-step fix

Skip the "restart the service" advice. You need to clear the bad data first. Here's the order that actually works.

  1. Stop the spooler service. Open Command Prompt as Administrator. Type net stop spooler and hit Enter. The service stops. Now it won't crash while you clean up.
  2. Delete the stuck print jobs. Go to C:\Windows\System32\spool\PRINTERS. Delete everything inside that folder. Yes, all of it. That's where the corrupt .SPL files live. If Windows says a file is in use, go back and make sure the spooler is stopped. I've seen a half-deleted job cause the same crash loop.
  3. Clear the event log junk. This isn't always needed, but if the spooler keeps dying, old event log entries can trip it up. Open Event Viewer, go to Windows Logs > System, right-click, and clear all events. Not critical, but I've had a case where a corrupt event log entry kept re-triggering the crash.
  4. Delete the printer driver from the registry. This is the part people skip. Run regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3. Delete any driver entries for the printer that's crashing. Be careful—only delete the one you know is bad. I usually delete the entire driver key for the problematic printer model. Then restart the spooler with net start spooler.
  5. Reinstall the printer driver fresh. Download the latest driver from the manufacturer's site. Avoid the "universal" drivers if you can—they're bloated and often cause this exact issue. Use the model-specific driver. Install it, restart the spooler, and test.

If it still fails

Check for third-party print management software. I've seen tools like PaperCut or even some antivirus add-ons interfere with the spooler. Disable them temporarily. Also check if the printer is set as the default—Windows sometimes crashes when you have multiple network printers and one is unreachable. Unplug the printer's USB cable if it's a USB printer—bad cables can send garbage data that crashes the spooler.

If you're still stuck, run a system file check: sfc /scannow in an admin Command Prompt. That's rare, but I've had a corrupt win32k.sys file cause this once. Good luck.

Was this solution helpful?

print spooler keeps stopping spooler subsystem app has stopped working fix print spooler Windows 10 print spooler error print queue stuck clear print spooler spoolsv.exe crash printer driver corruption Windows print spooler service fix printer not printing