Printer Spooler Crashing: Ultimate Fix

A print spooler that keeps dying leaves jobs stuck, printers greyed out, and error messages that reappear the moment you dismiss them. Yanking the printer out and adding it again usually treats the symptom, not the cause. The real fix works from the bottom up: stop the service cleanly, empty the queue that is jamming it, strip out stale printer entries, and remove the broken driver package underneath. Follow the steps in order and you should end with a stable spooler and a printer that prints on the first try.

1. 1

   Stop the Print Spooler service

   Press the Windows key, type services.msc, and open the Services console. Scroll to Print Spooler, right-click it, and choose Stop. If it refuses to stop or restarts on its own, that is a sign a stuck job or a faulty driver is dragging it down, which the next steps address. Leaving the service stopped for now is intentional: it releases its lock on the queue folder so you can clear it safely. Keep the Services window open, because you will start the service again once the cleanup is finished. Do not restart your PC yet, or Windows will simply relaunch the same crashing service.

2. 2

   Clear the stuck print queue

   Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS. This folder holds the spooled jobs waiting to print, and a single corrupt job here can crash the spooler every time it loads. With the service stopped, select everything inside the PRINTERS folder and delete it. Delete only the files inside; leave the PRINTERS folder itself in place. If Windows says a file is in use, confirm the Print Spooler service is fully stopped and try again. An empty queue gives the spooler a clean start, so the crash loop can't restart from a poisoned job left over from an earlier attempt.

3. 3

   Restart the spooler and test

   Return to the Services console, right-click Print Spooler, and choose Start. Watch it for a moment; if it stays running instead of stopping again, the stuck queue was likely the culprit. Try a small test print from a simple app like Notepad. If the job completes and the service holds steady, you may be done. If the spooler crashes again within seconds, the problem lives in a stale printer entry or a broken driver package, so continue with the steps below rather than repeating the queue cleanup, which won't help a second time.

4. 4

   Remove stale printer entries

   Open Settings, go to Bluetooth & devices, then Printers & scanners. Remove every printer you no longer use, plus the one that keeps failing. Old or duplicate entries often point at driver files that no longer match your hardware, and Windows keeps trying to load them at startup. Removing the device here clears the entry but usually leaves the driver package behind on disk, which is why the next step matters. Note the exact printer model name before you delete it so you can add it back cleanly later using the manufacturer's supported method through Windows.

5. 5

   Delete the broken driver package

   Press the Windows key, type Print Management, and open it. Expand Print Servers, select your PC, then open Drivers. Right-click the driver tied to the crashing printer and choose Remove Driver Package rather than plain Delete, so both the driver and its supporting files are pulled off the system. If Windows says the driver is in use, stop the Print Spooler service again, remove the package, then restart the service. Clearing the package here is what breaks the crash loop for good, because the spooler can no longer try to load a damaged driver every time it starts.

6. 6

   Reinstall the printer cleanly

   With the old package gone, add the printer fresh. In Settings under Printers & scanners, choose Add device and let Windows detect it over USB or the network. For most printers, allowing Windows to fetch its own driver through Windows Update gives you a clean, matched package. If your model needs the manufacturer's software, get it only from your printer maker's official support page for that exact model, and avoid third-party driver sites entirely. Once installed, print another test page from Notepad to confirm the spooler stays up and the job completes without the service falling over again.

7. 7

   Confirm stability and check the logs

   Send two or three real print jobs of different sizes to make sure the spooler handles a normal workload, not just a one-line test. If a crash sneaks back, open Event Viewer, expand Windows Logs, and look under Application and System for entries mentioning the spooler or the printer driver around the time it failed. The event details often name the exact file at fault, which tells you whether a leftover driver slipped back in. Setting a restore point now, while everything is stable, gives you a clean state to return to if a future driver update reopens the problem.