Quick fix: Print Spooler crashing usually means a corrupt print job or bad driver. Stop spooler: net stop spooler. Delete all files in C:\Windows\System32\spool\PRINTERS. Start spooler: net start spooler. Set service recovery: services.msc → Print Spooler → Recovery tab → First failure: Restart the Service. Removes problem permanently.
Print Spooler service stops on its own. Print jobs hang. Restarting service helps briefly, but it stops again. Cause: stuck print job, corrupt driver, or third-party print add-on crashing the spooler.
Affects: Windows 11 (and Windows 10) Print Spooler service.
Fix time: ~15 minutes.
What causes this
Print Spooler service queues and processes print jobs. Crashes happen when: stuck/corrupt job in queue, bad print driver, broken print monitor (DLL hook), or PrintNightmare-related vulnerability mitigations failing. Standard fix: clear queue + ensure auto-restart on crash.
Method 1: Clear stuck jobs and configure auto-restart
The standard fix.
- Open Terminal (Admin).
- Stop the service:
net stop spooler - Delete spooled jobs:
del /f /s /q C:\Windows\System32\spool\PRINTERS\*.* - Start the service:
net start spooler - Configure auto-restart on crash:
services.msc→ Print Spooler → Properties → Recovery tab. Set all three failure actions to Restart the Service. Apply. - Test print. If still crashes: identify cause via Methods 2/3.
Standard recovery sequence.
Method 2: Identify and remove bad printer driver
For driver-induced crashes.
- Open Event Viewer (
eventvwr.msc). - Navigate to Windows Logs → Application. Filter for source Application Error or spoolsv.exe.
- Look at recent crashes. Often shows faulting module name — specific driver DLL.
- Identify the driver: search filename online or check Printer Properties → Advanced for the driver name.
- Remove the printer using that driver: Settings → Bluetooth & devices → Printers & scanners → pick printer → Remove device.
- Remove the driver itself: Print Management (
printmanagement.msc) → Print Servers → [local PC] → Drivers → right-click driver → Remove Driver Package. - Reboot. Spooler should be stable.
- Re-add printer with fresh driver from manufacturer’s site (not Windows generic if possible).
This targets the root cause.
Method 3: Remove third-party print monitors and ports
For exotic crashes.
- Open Registry Editor. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors. - List of installed print monitors: BJ Language Monitor, Local Port, Standard TCP/IP Port, USB Monitor, WSD Port.
- For each non-default entry (anything besides the above): suspect. Common culprits: PDF print monitors, Canon language monitors, third-party fax monitors.
- Right-click suspect monitor key → Export (backup). Then delete.
- Restart Print Spooler.
- Test print stability.
- If stable: monitor was the cause. Keep removed.
- If still crashes: investigate
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Print Processors. Similar approach — keep only winprint; remove others.
This is the right path for exotic crashes.
How to verify the fix worked
- Run
Get-Service Spooler | Format-Table Name, Status, StartType. Status: Running, StartType: Automatic. - Print a test page. Completes without spooler crash.
- Event Viewer → Application log: no new spoolsv.exe errors in past hour.
If none of these work
If spooler still crashes: Damaged spooler binary: run sfc /scannow. Repairs system files including spoolsv.exe. For PrintNightmare-related issues: Microsoft mitigations stricter on driver installation. Reinstall driver from latest manufacturer release. For network printers via WSD port: WSD can be flaky. Re-add printer using static IP and TCP/IP port instead. For PCs with many printers installed: cumulative driver bloat. Remove printers you don’t use. Less attack surface for crashes. For corporate environments: Print Server may be the actual cause. Contact IT. Last resort — reset Print subsystem: complete spooler reset via PowerShell:
Stop-Service Spooler -Force
Remove-Item C:\Windows\System32\spool\PRINTERS\* -Recurse -Force
Remove-Item HKLM:\SYSTEM\CurrentControlSet\Control\Print\Printers\* -Recurse -Force
Start-Service Spooler
Caution: removes all installed printers. Re-add fresh.
Bottom line: Stop spooler, clear PRINTERS queue, start spooler, set Recovery to Restart the Service. Identify problematic driver via Event Viewer. Remove non-default print monitors. Reinstall printer with fresh driver.