How to Fix Printer Spooler Errors on Windows

If your printer suddenly stops responding and Windows shows a job stuck in the queue, you are almost certainly dealing with a printer spooler error on Windows. The Print Spooler is a background service that manages print jobs sent to a printer, and when it crashes, hangs, or becomes corrupt, nothing prints. The good news is that most spooler problems can be fixed without reinstalling Windows or replacing your hardware. This guide walks you through every proven method to fix printer spooler errors on Windows, from a simple service restart to deeper registry and driver repairs. If you are also shopping for a more reliable machine, browse our printer reviews and recommendations to find a model with fewer driver headaches.

What Is the Print Spooler and Why Does It Fail?

The Print Spooler is a Windows system service (executable: spoolsv.exe) that acts as a buffer between your applications and your printer. When you press Print in any program, the job does not go directly to the hardware. Instead, it is written as a temporary spool file to C:\Windows\System32\spool\PRINTERS\ and the spooler feeds it to the printer at the right pace. This decoupling lets you keep working in your application while the printer works in the background.

Because the spooler sits between software and hardware, it is exposed to problems from both directions. A misbehaving application can write a malformed job that the spooler cannot process. A bad or outdated driver can cause spoolsv.exe to crash entirely. And because the spool folder accumulates files over time, a single corrupt leftover file from a previous session can block every subsequent job.

Common Causes of Spooler Errors

• Corrupt or outdated printer drivers — the single most frequent trigger. A driver mismatch after a Windows update is especially common.
• Stuck print jobs — a job that failed mid-print leaves a .SPL or .SHD file that blocks the queue.
• Malware — some threats inject code into spoolsv.exe or replace it entirely.
• Incorrect spooler startup type — if the service is set to Manual or Disabled, it may not start after a reboot.
• Registry corruption — missing or altered keys under HKLM\SYSTEM\CurrentControlSet\Services\Spooler prevent the service from loading.
• Conflicting third-party software — PDF printers, fax software, or VPN clients sometimes install their own printer ports that corrupt the shared spooler environment.

Symptoms to Watch For

• Print jobs get stuck "Deleting" or "Spooling" and never print
• The printer appears offline even when powered on and connected
• Windows shows the error "Print Spooler service is not running"
• You cannot add or remove printers in Settings
• spoolsv.exe consumes 90–100% CPU in Task Manager

Quick Fix: Restart the Print Spooler Service

Before trying anything else, restart the spooler. This clears any temporary crash state and costs you nothing if it does not work. You have two paths: the graphical Services panel or Command Prompt.

Using the Services Panel

1. Press Win + R, type services.msc, and press Enter.
2. Scroll down to Print Spooler and double-click it.
3. If the service is running, click Stop and wait for it to halt.
4. Set Startup type to Automatic if it is not already.
5. Click Start, then OK.
6. Try printing again.

Using Command Prompt

Open Command Prompt as Administrator (right-click the Start button → Terminal (Admin) or Command Prompt (Admin)) and run these three commands in order:

net stop spooler
del /Q /F /S "%systemroot%\System32\spool\PRINTERS\*.*"
net start spooler

The middle line deletes all pending spool files at the same time, so you are doing a restart and a queue clear in one step. This combination resolves the majority of everyday spooler problems.

Clear the Print Queue Manually

Sometimes restarting the service alone is not enough because a corrupt spool file immediately crashes it again. In that case you need to manually delete the files in the spool folder.

Delete Stuck Spool Files

1. Stop the Print Spooler service using either method above.
2. Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS\. You may need to enable "Show hidden items" in View options.
3. Select all files (Ctrl + A) and delete them. Do not delete the PRINTERS folder itself — only the contents.
4. Restart the Print Spooler service.
5. Reopen your document and print again.

If Windows says a file is in use, the spooler is still running. Double-check via services.msc that the service is fully stopped before deleting.

Fix or Reinstall Printer Drivers

A corrupt or incompatible driver is the root cause in a large share of persistent spooler problems. Windows updates sometimes replace a working driver with a generic one that does not fully support your model, or a partially downloaded driver update leaves broken files behind. If restarting the spooler does not hold — it crashes again within minutes or after the next print attempt — driver removal and reinstallation is the next logical step. This is also worth doing any time you have recently connected a new printer; for broader setup guidance, our article on how to set up a network printer covers the driver installation process in more detail.

Remove Corrupt Drivers

1. Stop the Print Spooler service.
2. Open Device Manager (Win + X → Device Manager).
3. Expand Printers, right-click your printer, and choose Uninstall device. Check Delete the driver software for this device if the option appears.
4. Open Print Management (search for it in Start) → Drivers. Right-click any listed driver for your printer and choose Delete.
5. Restart Windows before reinstalling.

For a deeper clean, open an elevated Command Prompt and run printui /s /t2 to open the Print Server Properties. Under the Drivers tab you can remove any leftover driver packages that Device Manager missed.

Reinstall the Correct Driver

Always download drivers directly from the manufacturer's support page rather than relying on Windows Update, especially for business-grade laser printers. Search for your exact model number and download the full driver package, not just the basic driver. Run the installer with the Print Spooler service running. After installation, print a test page from Settings → Bluetooth & devices → Printers & scanners before testing from an application.

If you are also experiencing color output issues, read our guide on how to troubleshoot a printer not printing in color — driver problems often cause both spooler errors and color failure simultaneously.

Advanced Fixes: Registry and Dependencies

If the spooler service refuses to start — you see error 1053, 1068, or a generic "Windows could not start the Print Spooler service" — the problem is deeper than a stuck job or bad driver. At this level you need to check the registry and verify that the services the spooler depends on are healthy.

Check the Spooler Registry Keys

Back up your registry before making any changes. Open Registry Editor (Win + R, type regedit) and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler

Verify that the following values exist and are correct:

• ImagePath → %SystemRoot%\System32\spoolsv.exe
• Start → 2 (Automatic). If it reads 3 (Manual) or 4 (Disabled), double-click and change it to 2.
• ObjectName → LocalSystem

If the ImagePath points anywhere other than spoolsv.exe in System32, malware may have replaced it. In that case, run a full antivirus scan before continuing and consider restoring from a clean system backup.

As an alternative to manual registry editing, run the Windows System File Checker to automatically repair corrupted system files:

sfc /scannow

If SFC reports issues it cannot repair, follow up with:

DISM /Online /Cleanup-Image /RestoreHealth

Both commands require an elevated Command Prompt and take 15–30 minutes to complete.

Verify Spooler Dependencies

The Print Spooler depends on two other services: Remote Procedure Call (RPC) and DCOM Server Process Launcher. If either is stopped or disabled, the spooler will fail to start regardless of what else you do. Open services.msc and confirm both are running and set to Automatic. You cannot manually start RPC — if it is stopped, a Windows repair installation is usually required.

You can also check dependencies from an elevated Command Prompt:

sc qc spooler

Look for the DEPENDENCIES line in the output. It should list RPCSS and http at minimum.

How to Prevent Printer Spooler Errors in the Future

Once you have resolved the immediate problem, a few habits will keep the spooler healthy long-term:

• Keep drivers current. Check the manufacturer's site after every major Windows feature update. Many spooler crashes happen in the weeks after a Windows upgrade because the old driver is no longer fully compatible. Our laser printer maintenance tips cover driver management as part of a broader upkeep routine.
• Remove printers you no longer use. Every installed printer leaves a driver in the spooler environment. Orphaned drivers from printers you no longer own are a hidden source of instability.
• Do not cancel print jobs by killing the application. Always cancel through the print queue in Windows (Settings → Printers & scanners → Open print queue). Force-quitting an application mid-print often leaves a corrupt spool file.
• Set the spooler to restart automatically on failure. Open services.msc, double-click Print Spooler, go to the Recovery tab, and set First, Second, and Subsequent failures all to Restart the Service. This will not fix an underlying driver problem, but it means a transient crash does not leave your printer offline until your next reboot.
• Run periodic malware scans. Spooler hijacking is a known attack vector. Windows Defender on a standard update schedule is sufficient for most users, but ensure real-time protection is active.
• Consider printer reliability when buying. Some printer models are notoriously more prone to driver conflicts than others. Before your next purchase, check our guide to printer duty cycle — printers rated for higher duty cycles tend to come with more mature, stable driver ecosystems.