A single corrupt PDF document can lock the entire Windows Print Spooler service, preventing all subsequent documents from printing and rejecting the “Cancel” command.
Why This Problem Happens
- Corrupted spool file (.SPL or .SHD) locked in system32 spool folder.
- Third-party software hook causing spoolsv.exe to crash repeatedly.
Step-by-Step Troubleshooting Procedure
Step 1: Stop Print Spooler Service via Terminal
Objective: Halt the background spool process.
- Right-click the Windows Start button and select “Terminal (Admin)” or “Command Prompt (Admin)”.
- Type: net stop spooler and press Enter.
Step 2: Delete Cached Spool Files
Objective: Clear the physical queue folder.
- Press Windows Key + R, paste: %systemroot%System32SpoolPrinters and hit Enter.
- Select all files in this folder and press Shift + Delete to purge stuck print files.
Step 3: Restart the Print Spooler Service
Objective: Restore printing capability.
- In your admin terminal, type: net start spooler and hit Enter.
- Open your document and send a fresh print request.
Verified Troubleshooting Tips
- Set Print Spooler recovery options in services.msc to “Restart the Service” on First and Second failures.
Frequently Asked Questions
Is it safe to delete files inside the SpoolPrinters folder?
Yes. That folder only holds temporary cached print jobs currently waiting in the queue.