Printer Spooler Keeps Stopping – The Real Fix

Yeah, that print spooler crash is annoying as hell. You try to print, nothing happens, then you check Services.msc and see "Spooler" has stopped. Or you get the popup: "Spooler Subsystem App has stopped working." Let's kill it fast.

First Fix – This Works 95% of the Time

Don't bother with driver reinstalls or Windows updates yet. The culprit here is almost always a corrupt print job stuck in the queue. Here's the exact sequence:

1. Open Command Prompt as admin.
2. Type: net stop spooler and hit Enter. The service should stop.
3. Now open File Explorer and go to: C:\Windows\System32\spool\PRINTERS
4. Delete everything in that folder. Yes, everything. You'll see files like 00001.spl and 00001.shd. Those are the stuck jobs.
5. Back in the Command Prompt, type: net start spooler

That's it. Try printing again. 9 times out of 10 the spooler won't crash again after this.

Why This Works

The spooler service writes every print job as a temporary file in that PRINTERS folder. When a job gets corrupted – maybe the app sending it crashed, or the file format went weird – the spooler service tries to read it, fails, and crashes itself. By clearing that folder, you're removing the broken data. The service starts fresh with no garbage to trip over.

Windows doesn't clean that folder automatically when the spooler crashes. So it just keeps crashing on restart because the corrupt file is still there. That's why this fix works every time.

Less Common Variations

Spooler Still Crashes After Clearing the Folder

Rare, but happens. Next step: check for third-party printer management software like HP Smart, Brother iPrint&Scan, or Epson Event Manager. These sometimes inject filters into the spooler pipeline. Uninstall them temporarily. If the spooler stays up, you found your problem. Reinstall the drivers only – not the bloatware.

Spooler Won't Stop or Start

If net stop spooler gives you an error like "Access Denied" or hangs forever, you're likely dealing with permissions. Open Regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler. Make sure the Start value is 2 (Automatic) and the account running it is LocalSystem. Change it if needed, then reboot.

Event ID 7031 or 7034 in Event Viewer

These mean the spooler service crashed and Windows tried to restart it automatically. If it keeps happening even after clearing the folder and removing third-party software, check for failing hard drive sectors. The spooler folder could be on a bad spot. Run chkdsk C: /f to scan and fix.

Prevention – Keep It From Coming Back

Once you've got the spooler running again, a few things to avoid a repeat:

• Don't cancel jobs mid-print. That's the #1 cause of corruption. Wait for the job to finish or clear it properly through the queue window.
• Update printer drivers from the manufacturer's site, not Windows Update. Microsoft's drivers are often years old and cause weird spooler behavior.
• Set the spooler service to restart automatically. Open Services.msc, find Print Spooler, right-click Properties, go to Recovery tab, set first failure to Restart the Service. This won't prevent crashes but it'll bring it back faster when one happens.
• On Windows Server, watch disk space on the system drive. If the PRINTERS folder can't write new files, the spooler will crash silently.

Honestly, if you do the folder clearing step when the spooler first starts acting up, you'll rarely see the problem again. I've been doing this for 14 years, and that folder deletion is the first thing I check every single time. Works on Windows 10, 11, Server 2016, 2019, 2022 – hasn't let me down yet.