Print Server Queue Deadlock – Fix in 30 Seconds or 15 Minutes

30-Second Fix – Restart the Print Spooler

This fixes 80% of deadlocks. Don't overthink it. Open Command Prompt as Admin — right-click Start, select Command Prompt (Admin) or PowerShell (Admin). Then run these two commands:

net stop spooler
net start spooler

That's it. The spooler stops, clears its memory, and restarts. Go check your printer queue. If it's empty now, you're done. If the queue still shows stuck jobs, move to the next fix.

Why this works: The print spooler is a Windows service that holds print jobs in memory and sends them to the printer. When a job gets stuck — usually from a corrupt print driver or a network timeout — the spooler locks up. Restarting it dumps everything and starts fresh.

5-Minute Fix – Manually Clear the Print Queue

If the spooler restart didn't clear the queue, the jobs are stuck in the spool folder. You'll need to delete them by hand. Here's how:

1. Open Services: press Win + R, type services.msc, hit Enter.
2. Find Print Spooler in the list. Right-click it, select Stop.
3. Open File Explorer, go to C:\Windows\System32\spool\PRINTERS.
4. Delete everything in that folder. Don't worry, it's just temp print files.
5. Go back to Services, right-click Print Spooler, select Start.
6. Check your printer queue — it should be empty now.

If you get a permissions error deleting files, run File Explorer as Admin. Right-click the Start button, pick Windows Explorer (Admin), then navigate to the folder again.

When this happens: I see this most often with network printers (HP, Brother, Canon) on Windows 10 and 11 after a print job is canceled midway. The spool file is corrupt and won't let go.

15+ Minute Fix – Clear the Queue Manually via Command Line (For Stubborn Jobs)

Still stuck? The queue might have a job that won't delete because it's tied to a specific user session or a corrupt registry entry. Here's the nuclear option:

Step 1: Stop the Spooler and Delete Files

Run these commands as Admin:

net stop spooler
del /Q /F /S C:\Windows\System32\spool\PRINTERS\*.*
net start spooler

The /Q (quiet) and /F (force) flags remove files without confirmation. If a file is locked, this won't work — skip to the next step.

Step 2: Remove Stuck Jobs from the Registry

Sometimes the spooler remembers jobs in the registry. You'll need to clear those too. Open Registry Editor (type regedit in Start, run as Admin).

Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers

Under Printers, you'll see keys for each installed printer. Look for the printer with the stuck job. Inside that key, find Jobs. Delete the Jobs key entirely. Be careful — don't delete the printer key itself.

Now restart the spooler again:

net stop spooler
net start spooler

Check your queue. If the job is still there, the issue is likely a corrupt print driver. Uninstall and reinstall the printer.

Step 3: Reinstall the Printer Driver

Go to Settings > Bluetooth & devices > Printers & scanners. Click on the stuck printer, then Remove device. Don't delete the driver yet — just remove the printer.

Then open Print Server Properties (type printmanagement.msc in Start). Go to the Drivers tab, find the driver for your printer, right-click, and Remove. Reboot, then add the printer fresh.

Pro tip: If you're on a network, make sure the printer is powered on and connected before adding it again. A dead printer will cause the same deadlock.

When to Call It Quits

If you've done all three fixes and the queue is still stuck, the problem is likely hardware. Check the printer's display for error codes. A paper jam, low ink, or a bad network card can cause the spooler to hang. On the server side, check Event Viewer under Applications and Services Logs > Microsoft > Windows > PrintService for clues.

One more thing — if this is happening regularly, look at the printer driver version. Older drivers (pre-2020) are notorious for causing deadlocks on Windows 11 and Server 2022. Update to the latest manufacturer driver, not the one Windows Update pushes.

That's it. Start with the 30-second fix, work your way down. You'll save yourself an hour of frustration.