How to Clear the Print Spooler and Fix Stuck Print Jobs

When your printer stops responding and jobs pile up in the queue, the culprit is almost always the print spooler — a Windows service that manages the line of documents waiting to be printed. Knowing how to clear it is one of the most practical troubleshooting skills any Windows user can have.

What Is the Print Spooler?

The print spooler (officially called the Print Spooler service) is a background process built into Windows that acts as a traffic controller between your applications and your printer. When you hit "Print" in any program, Windows doesn't send the job directly to the printer. Instead, it writes the job as a temporary file to a spooler folder, then feeds it to the printer in an orderly queue.

This design lets you queue multiple documents, print while your computer does other things, and manage jobs before they reach the printer. The downside: if a job corrupts, gets stuck, or the service crashes, the entire queue can freeze — and new jobs pile up behind the broken one.

The spooler stores its temporary files in:

C:WindowsSystem32spoolPRINTERS 

Clearing the spooler means stopping the service, deleting those temporary files, and restarting the service.

How to Clear the Print Spooler on Windows 🖨️

There are three main methods, ranging from point-and-click to command line.

Method 1: Using Windows Services (Most Reliable)

This is the most thorough approach and works on Windows 10 and Windows 11.

1. Press Windows + R, type services.msc, and hit Enter
2. Scroll down to Print Spooler, right-click it, and select Stop
3. Open File Explorer and navigate to C:WindowsSystem32spoolPRINTERS
4. Delete all files inside the folder — do not delete the folder itself, only its contents
5. Return to Services, right-click Print Spooler, and select Start
6. Try printing again

Stopping the service before deleting the files is essential. If the spooler is still running, Windows will lock those files and you won't be able to remove them.

Method 2: Using Command Prompt (Fastest for Power Users)

Open Command Prompt as Administrator (search for cmd, right-click, select Run as administrator), then run these commands in order:

net stop spooler del /Q /F /S "%systemroot%System32spoolPRINTERS*.*" net start spooler 

Each line stops the service, clears all spooler files, and restarts the service. This is identical to Method 1 but faster if you're comfortable with the command line.

Method 3: Task Manager + Print Queue (Quick Fix for Minor Jams)

For a stuck job that isn't caused by a deeper spooler problem:

1. Open Settings → Bluetooth & devices → Printers & scanners
2. Select your printer and click Open print queue
3. Right-click each stuck job and select Cancel
4. If jobs won't cancel, use Method 1 or 2 instead

This lighter approach works for minor queue issues but won't resolve cases where the spooler service itself has crashed or become unresponsive.

Why the Spooler Gets Stuck in the First Place

Understanding the root cause helps you decide how aggressively to intervene.

Variables That Affect How This Plays Out

Clearing the spooler is a consistent process, but several factors determine whether it fully resolves your problem:

Windows version and edition — The steps above apply to Windows 10 and 11. Windows Server environments have the same spooler architecture but may have permission restrictions that prevent standard users from stopping the service or accessing the PRINTERS folder.

Driver quality and age — If an outdated or incompatible printer driver is generating corrupted spool files repeatedly, clearing the spooler will fix the symptom but the queue will jam again. In that case, the driver is the real issue.

Network vs. local printers — On a locally connected printer (USB), you control everything. On a network or shared printer, the spooler may be managed by a print server, and clearing your local spooler may not be enough if the server-side queue is also stuck.

User account permissions — Standard Windows accounts may not have the rights to stop system services or delete files in system directories. Administrator access is required for Methods 1 and 2.

Frequency of the problem — A one-time spooler jam usually clears cleanly. If the spooler freezes repeatedly — weekly or after every few print jobs — that points to an underlying issue: driver incompatibility, a specific application generating malformed output, or hardware problems with the printer itself.

What Gets Deleted (and What Doesn't) 🗂️

A common concern is whether clearing the spooler deletes anything important. It doesn't. The files in the PRINTERS folder are temporary spool files — they're automatically recreated when new print jobs are sent. Your original documents are untouched. The only thing lost is whatever was already stuck in the queue, which couldn't print anyway.

Printer settings, preferences, and installed drivers are stored elsewhere in the registry and driver directories, completely separate from the spooler temp files.

When the Spooler Keeps Coming Back Corrupted

Some users find that after clearing the spooler, the same printer or the same application consistently generates stuck jobs. The factors that typically drive this pattern include the age of the printer driver, whether the driver is a manufacturer-supplied package or a generic Windows driver, and whether the application sending jobs outputs a print format the driver handles cleanly.

In those cases, the troubleshooting path branches — clearing the spooler is step one, but driver reinstallation, checking for firmware updates, or testing with a different application becomes the next variable to isolate. Whether that's the right next step depends on your specific printer model, how it's connected, and what software you're printing from.