Clear the Queue and Get Your Printer Working Again
A stalled print queue can make an otherwise healthy printer appear offline or unresponsive. This guide explains what the Windows Print Spooler does, when restarting it is appropriate, and how to safely clear pending jobs through Settings, Services, Command Prompt, or PowerShell. It also covers the difference between a one-time stuck job and a recurring spooler failure, with practical checks for drivers, network connections, permissions, storage, and printer firmware. A comparison table helps you choose the right recovery method, while preventive steps reduce future queue problems.
When a document remains on “Printing,” a queue refuses to clear, or every new job fails immediately, the problem is often the Windows Print Spooler rather than the printer itself. Restarting that service can restore normal printing in minutes, but it works best when paired with a deliberate cleanup of stuck files and a quick check of the underlying cause. This guide explains how to restart the spooler safely, choose the right recovery method, and avoid repeated queue failures.
What the Print Spooler does
The Print Spooler is a Windows service that receives print jobs, stores them temporarily, and passes them to a local, shared, or network printer. This lets applications continue working after you click Print instead of waiting for the printer to finish each page.
On most Windows PCs, queued job data is held in the spool folder at C:\Windows\System32\spool\PRINTERS. If a damaged job file, interrupted connection, incompatible driver, or unavailable printer blocks that queue, later jobs may be unable to proceed. Restarting the service releases the processing pipeline; deleting the pending spool files removes jobs that cannot be canceled normally.
A spooler restart is a queue recovery action, not a repair for every printing fault. If the same issue returns, investigate the driver, printer connection, print server, or application that created the failing job.
Recognize when a spooler restart is appropriate
Start with the printer queue whenever the printer is powered on and reachable but Windows will not send work to it. Open Settings > Bluetooth & devices > Printers & scanners, select the printer, and choose Open print queue. On Windows 10, the comparable path is Settings > Devices > Printers & scanners.
- A job is stuck on Printing, Deleting, Spooling, or Error.
- Canceling a document has no effect.
- All printers fail after one problematic print job.
- A printer shows online, but documents never leave the queue.
- The Print Spooler service has stopped or repeatedly terminates.
Do not assume the spooler is responsible if the printer display reports paper, toner, door, or hardware errors. Likewise, a network printer that cannot be reached may need its Wi-Fi, Ethernet, IP address, or print-server connection corrected before a queue reset will help.
Choose the right way to clear a printing blockage
Use the least disruptive method first. A standard queue cancellation preserves the service and is ideal for one ordinary document. Service-level methods are more useful when the queue itself is frozen.
| Method | Best use case | What it removes or changes | Administrative access |
|---|---|---|---|
| Cancel from print queue | One job still responds to cancellation | Selected document only | Usually no |
| Restart from Services | Queue is stalled but jobs are not corrupted | Restarts the service; queued jobs may remain | Usually yes |
| Stop, clear spool folder, start | Jobs are stuck on Deleting or Printing | Deletes all locally queued pending jobs | Yes |
| Command Prompt or PowerShell | Repeatable support workflow or remote administration | Depends on commands used | Yes |
Restart the Print Spooler using Services
This graphical approach is suitable for most home and office PCs. Before proceeding, note that restarting the service can interrupt every pending job for every printer installed on the computer.
- Save work in applications that may be printing or preparing to print.
- Press Windows + R, type
services.msc, and press Enter. - Find Print Spooler in the services list.
- Right-click it and select Restart. If Restart is unavailable, choose Stop, wait until its status changes, then choose Start.
- Return to the printer queue and remove any remaining documents, then send a small test page.
If the service will not start, open its properties and confirm that Startup type is set to Automatic. A service that starts and then stops again often points to a damaged driver, a dependency problem, or a system issue that needs broader troubleshooting.
Fully clear stuck print jobs from the spool folder
When a document cannot be canceled, simply restarting the service may not be enough. Clear the local spool files only after stopping the spooler. Deleting files while the service is running can cause access errors or leave the queue in an inconsistent state.
Manual file cleanup
- Open Services with
services.mscand stop Print Spooler. - Open File Explorer and enter
C:\Windows\System32\spool\PRINTERSin the address bar. - Approve the administrator prompt if Windows requests permission.
- Delete the files inside the
PRINTERSfolder, but do not delete the folder itself. - Return to Services and start Print Spooler.
- Open the queue, confirm it is empty, and print a Windows test page or a one-page document.
Those files represent unsent local jobs. They are not documents saved in your usual folders, but you may need to reprint anything that was pending after the cleanup.
Use Command Prompt or PowerShell
Administrative command tools provide a fast and consistent option, especially for technical support staff. Open Windows Terminal (Admin), Command Prompt (Admin), or PowerShell (Admin). To restart only the service, run:
net stop spooler
net start spoolerTo stop the service, remove local pending job files, and start it again, use Command Prompt commands:
net stop spooler
del /Q /F %systemroot%\System32\spool\PRINTERS\*.*
net start spoolerIn PowerShell, an equivalent sequence is:
Stop-Service -Name Spooler
Remove-Item "$env:windir\System32\spool\PRINTERS\*" -Force
Start-Service -Name SpoolerRun these only on a computer you administer. In a managed workplace, jobs may be processed through a print server instead of the individual PC; clearing the local queue may not remove a server-side job. Contact the organization’s IT team if you do not control that server.
Fix recurring spooler failures
If clearing the queue solves the problem once but not repeatedly, look beyond the queue. A print driver is a common source of instability, particularly after an operating system update or when an older printer uses a legacy driver. Download the current driver or supported universal driver from the printer manufacturer’s official support site. Avoid third-party driver download sites.
Checks that prevent the next blockage
- Restart the printer and, for network models, restart the router only if other connectivity checks support that step.
- Confirm the correct printer is selected and that Use Printer Offline and Pause Printing are not enabled in the queue menu.
- For Wi-Fi or Ethernet printers, verify that the printer has a stable network address and remains reachable from the PC.
- Remove and re-add a printer that has an obsolete port, duplicate entry, or outdated shared-printer connection.
- Install Windows updates and the manufacturer’s current firmware when the vendor recommends it for your specific model.
- Check free space on the system drive; the spooler needs room for temporary job data.
For a printer that fails only from one application, test printing from Notepad or another simple application. If the test succeeds, the original file, application add-in, font, or document content may be the real trigger. Exporting a complex document to PDF, simplifying graphics, or updating the application may be more effective than repeatedly restarting the spooler.
When to escalate the problem
Escalate when the Print Spooler repeatedly stops, Windows displays access-denied errors in the spool folder, or multiple users cannot print to the same shared device. In business environments, an administrator may need to inspect the print server, remove a failing driver package, review event logs, or update deployment settings. For home users, manufacturer support is appropriate when the printer cannot complete its own built-in test page or remains unreachable after its connection has been verified.
Keep a short record of the printer model, Windows version, connection type, exact error message, and the application involved. This information makes it much easier to distinguish a local spooler problem from a device, network, or driver fault.
