Windows 11 — spoolsv.exe 100% CPU stops all printing (fixes & cleanup)

Joe B.

Reviewed for technical accuracy

Specialities: Windows 11/10, Print Spooler, enterprise print servers, driver isolation, spoolsv.exe CPU/memory issues

Windows 11 spoolsv.exe 100% CPU — print spooler service hang, stuck queues, corrupt drivers & print monitors

Technician

Hey! We’ll walk through why spoolsv.exe (Print Spooler) is hitting 100% CPU on Windows 11 and blocking every print job — and how to clean it up safely without breaking your printers.
A few details help us target the fix: Is this a single Windows 11 PC or a print server? Do you see lots of stuck print jobs in the queue, or specific printers (HP, Kyocera, Canon, etc.) freezing it? And did this start after a Windows update, new printer driver, or label software install?

Customer

Small office, mixed printers. Since a recent Windows 11 update, spoolsv.exe runs at 90–100% CPU as soon as someone prints. All queues show “Printing” but nothing comes out, and the PC becomes unusable until we kill the Print Spooler service.

Technician

Understood. Classic Windows 11 spoolsv.exe 100% CPU pattern.
The Spooler SubSystem App (spoolsv.exe) manages print queues and talks to printer drivers and ports. High CPU usually means it’s stuck looping over:
• Corrupted spool files in %systemroot%\System32\spool\PRINTERS.
• A bad or outdated printer driver (often shared/network drivers or legacy PCL/PS packages).
• Buggy port monitors / print processors from vendor software, label apps, or “all-in-one” printer suites.
• Massive event logging or spooler.xml-style logging hammering the service.
• In rare cases, malware pretending to be spoolsv.exe outside C:\Windows\System32.
Our plan: 1) Safely stop Print Spooler and clear stuck jobs. 2) Identify the printer/driver causing the spoolsv.exe high CPU. 3) Remove or update bad drivers/monitors. 4) Harden settings so Windows 11 printing stays stable.

Customer

Makes sense. What’s the safe way to stop spoolsv.exe and clear those stuck jobs? We don’t want to break all our printers.

Technician

Great question — we’ll do it in a controlled way.
Step 1 — Stop Print Spooler and flush corrupt spool files
1) Open Services (services.msc) and locate Print Spooler.
2) Right-click → Stop. This will temporarily kill spoolsv.exe and free up CPU.
3) Browse to C:\Windows\System32\spool\PRINTERS and delete all files inside (these are stuck print jobs, not drivers). A bloated PRINTERS folder is a top cause of spoolsv.exe high CPU and 100% disk/CPU spikes.
4) Go back to Services and Start the Print Spooler again.
This alone often brings spoolsv.exe CPU down immediately. If it jumps back to 100% as soon as someone prints, we know a specific printer or driver is poisoning the spooler.

Customer

We cleared the PRINTERS folder. CPU dropped, but as soon as we print to our network HP, spoolsv.exe shoots back to 100% and all printing stops again.

Technician

Perfect — that tells us this is not a generic Windows 11 issue but a driver/queue-specific cause.
Step 2 — Find which printer or driver is spiking spoolsv.exe
• Open Print Management (printmanagement.msc) → Printers. Pause all queues, then resume one by one while watching Task Manager for spoolsv.exe 100% CPU returning.
• When enabling a particular queue instantly pegs CPU, note its Driver Name (e.g., universal driver, class driver, vendor “full solution”).
• In Print Management → Drivers, identify old or duplicate Windows 10-era drivers, universal drivers, or vendor add-ons known to cause spooler hangs.
• Check Event Viewer → Applications and Services Logs → Microsoft → Windows → PrintService for repeated errors tied to one device, port, or print processor.
The culprit is usually a buggy or incompatible driver or print monitor repeatedly failing inside the Print Spooler service.

Customer

One of the queues uses an older HP driver and that’s the one that triggers spoolsv.exe to max out. How do we cleanly remove or replace that without nuking everything?

Technician

Good, now we surgically remove the problem.
Step 3 — Uninstall the problematic printer driver package
1) Stop the Print Spooler again.
2) In Print Management → Printers, delete the bad queue(s) that rely on that driver.
3) Go to Print Management → Drivers, right-click the suspect driver → Remove Driver Package. Choose “Remove driver and driver package” where available.
4) Start the spooler and confirm spoolsv.exe is stable.
5) Re-add the printer using a fresh Windows 11-compatible driver from the vendor or a lightweight Type 4 / class driver. Avoid bloated suites and unnecessary port monitors that hook deeply into the spooler.
This replaces the corrupt driver path that was locking your Print Spooler service at 100% CPU.

Customer

That helped a lot, but sometimes spoolsv.exe still spikes when users print from certain apps. Anything else that can cause high CPU in the print spooler on Windows 11?

Technician

Yep — a few more advanced culprits to rule out.
Step 4 — Check print processors, port monitors & spoolsv.exe location
• In the printer’s Advanced tab, ensure you’re using the default WinPrint processor unless your environment requires a custom one.
• Avoid unnecessary vendor port monitors (bi-di services, legacy status monitors) known to loop and cause spoolsv.exe high CPU on Windows 11 — disable or uninstall their utilities if not needed.
• Confirm the real file path: spoolsv.exe must live in C:\Windows\System32. If Task Manager shows it running from anywhere else, treat it as malware and scan immediately.
• Keep Windows 11 and printer firmware updated — some spoolsv.exe CPU spikes are patched via cumulative updates and vendor driver updates.
If after this the spikes only happen with one line-of-business app, we can tune that app’s print settings or drivers directly.

Customer

We’re also an RDS/remote environment for some users. Can one bad user or queue take down printing for everyone with spoolsv.exe at 100%?

Technician

Definitely — in multi-user or print server scenarios, one bad driver can hammer spoolsv.exe for everyone.
Step 5 — Harden spoolsv.exe in business / RDS setups
• Enable Print Driver Isolation (Isolated or Shared) where supported so a crashing driver doesn’t take down the entire Print Spooler service.
• Limit installed drivers to a small, tested set; remove legacy and duplicate packages.
• Use Type 4 drivers or vendor-certified Windows 11 drivers instead of random “universal” packages from third parties.
• Monitor Event Viewer for recurring PrintService errors tied to the same driver or print processor and remove it.
• Consider centralizing printing on a server and keeping endpoints lean, or vice versa, depending on where spoolsv.exe 100% CPU appears.
We can map this for your environment in a live session if you’d like.

Customer

Ok, after cleaning the queues and removing the bad drivers, spoolsv.exe is stable around 0–2% and printing works. Any final checks so this doesn’t come back?

Technician

Final checklist to keep spoolsv.exe from spiking again:
• Make sure no jobs sit “hung” in queues; clear them quickly so the spool folder doesn’t bloat.
• Standardize on a small set of Windows 11-compatible drivers and uninstall everything unused.
• Avoid installing printer software that adds toolbars, status daemons, or custom monitors unless truly needed.
• Keep regular updates, and if you use print servers, document which drivers/queues were approved.
Follow this and random Windows 11 spoolsv.exe 100% CPU incidents become rare.

Customer

Got it. CPU is normal and printing is back. If it spikes again, can you help us pinpoint which driver or queue is to blame?

Technician

Summary: When spoolsv.exe hits 100% CPU on Windows 11 and all printing stops, it’s almost always stuck spool files, a bad printer driver, or a buggy print monitor — not “Windows being slow”. Safely stop the Print Spooler, clear PRINTERS, identify the offending queue via Print Management and Event Viewer, remove or update that driver, and simplify your print stack. Want help tracing exactly which driver is killing your spooler? Open the chat and an expert will walk through it with you.

Quick answer: the accepted fix for spoolsv.exe 100% CPU

Accepted fix when Windows 11 spoolsv.exe is stuck at 100% CPU and printing stops: stop the Print Spooler service, delete all files in C:\Windows\System32\spool\PRINTERS, restart the spooler, then isolate which printer driver / queue re-triggers high CPU. Remove or update the bad driver, disable unnecessary print monitors/processors, and keep only stable Windows 11-compatible drivers.

FAQ — Windows 11 spoolsv.exe 100% CPU & Print Spooler

Step-by-step: Fix spoolsv.exe 100% CPU on Windows 11

1. Open Services, stop the Print Spooler service.
2. Delete all files from C:\Windows\System32\spool\PRINTERS to clear stuck jobs.
3. Restart the Print Spooler and confirm spoolsv.exe returns to low CPU.
4. Use Print Management to identify queues tied to problematic drivers; remove those queues.
5. Remove unstable or duplicate printer driver packages, then reinstall using current Windows 11-compatible drivers.
6. Standardize print processors (WinPrint), reduce third-party port monitors, and enable driver isolation where supported.
7. If issues persist, review Event Viewer → PrintService logs and consult an expert to avoid blind changes.

Mixed environments & print servers

1. Remember that spoolsv.exe high CPU on a shared Windows 11 PC or server can affect all clients printing through it.
2. Keep server-side drivers lean and stable; let macOS/Linux devices print via IPP/RAW to a clean queue rather than installing heavy drivers everywhere.

Sources

• Microsoft — Spooler.xml file growth and high CPU in spoolsv.exe
• Microsoft — Troubleshoot printer problems in Windows 10/11
• Microsoft — Printer and Print Spooler management overview

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.