The Print Spooler service has been a source of both stuck print jobs and serious security vulnerabilities (PrintNightmare being the most infamous) for decades. Most printing problems on Windows trace back to this one service misbehaving, and the fix is almost always the same handful of steps.
The Classic Fix: Clear the Queue and Restart
# Stop the spooler service Stop-Service -Name Spooler -Force # Clear stuck print jobs from the spool folder Remove-Item "C:\Windows\System32\spool\PRINTERS\*" -Force -ErrorAction SilentlyContinue # Restart the service Start-Service -Name Spooler # Confirm it's running Get-Service -Name Spooler
When It Keeps Crashing
If the spooler crashes repeatedly rather than just hanging, check Event Viewer’s Application log for the crashing module name — it’s frequently a third-party printer driver, not the spooler itself. Removing and reinstalling the driver (rather than just the printer) resolves most recurring crashes.
Security: Don’t Ignore Spooler Patches
The PrintNightmare vulnerability (CVE-2021-34527) allowed remote code execution via the spooler’s RPC interface, and several follow-up spooler CVEs have appeared since. If you don’t need network printing on a given server, disabling the spooler entirely is a legitimate hardening step:
Stop-Service -Name Spooler -Force Set-Service -Name Spooler -StartupType Disabled