Print Spooler
Also called spooler, spoolsv, print spooler
The Windows service that queues print jobs and talks to printers.
What you need to know
This is the print queue.
Print Spooler holds jobs until the printer is ready. A stuck job is a common reason people restart this service. If you never print, you can leave it off.
- Need it?
- Only if you print or use some scanners
- Stuck jobs?
- Restart the service, then clear the queue
- Safe to disable?
- Yes, if you do not print
What does this service do?
Display name: Print Spooler. Service name: Spooler.
The spooler accepts print jobs, stores them, and sends them to the printer driver. Some scan workflows still depend on it.
History on Windows
Still present
The Print Spooler has been a Windows service since Windows NT. The service name Spooler and the host spoolsv.exe are still the contract on Windows 10 and Windows 11.
| Present since | Windows NT |
|---|---|
| Still present | Yes, including Windows 10 and Windows 11 |
| Discontinued | No |
Why does Windows need it?
Windows needs a queue so an app can finish a print without waiting for every page to leave the printer.
When does it run?
It often stays running so the next job is fast. It wakes hard when a job is stuck or a driver fails.
Should it always be running?
If you print, keep it available. If this PC has no printer and no scan workflow, manual or disabled is a valid choice.
Can I disable it?
Yes, if you do not print
A PC that never prints can disable the spooler. A home office printer needs it. Restarting a stuck spooler is the usual fix, not a permanent disable.
What happens if I disable it?
Print and some scan functions stop. Apps may error when they look for a printer.
Process host
The spooler usually has its own host, spoolsv.exe, rather than a generic svchost.exe group. See spoolsv.exe.
Dependencies
| Depends on | RPC and HTTP on some configurations |
|---|---|
| Used by | Printers, some scanners, and print-to-PDF stacks |
Resource behavior
- CPU
- Low unless a driver loops
- Disk
- Queue files live under System32\spool
- Memory
- Modest
- Network
- Active for network printers
Common problems
Job stuck at "deleting"
Stop the spooler, clear the PRINTERS queue folder, start the spooler. That is the textbook fix.
High CPU
A broken driver can loop. Update or remove that printer. Do not delete spoolsv.exe.
Troubleshooting
Safe steps first.
Restart the service
Services.msc or an admin command to restart Spooler is the first step.
Clear the queue
After the service is stopped, remove leftover files in the spool PRINTERS folder.
Technical details
Technical details
| Display name | Print Spooler |
|---|---|
| Service name | Spooler |
| Host executable | spoolsv.exe |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Microsoft Learn: Print Spooler · Print spooler documentation
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.