Cancel or Clear a Stuck Print Queue in Windows 11 & 10

To clear a stuck print queue in Windows 11 or 10, open Settings > Bluetooth & devices > Printers & scanners (Windows 11) or Settings > Devices > Printers & scanners (Windows 10), select the printer, choose Open print queue, and try Cancel on the stuck job first — but if that does nothing, the fix that actually works is restarting the Print Spooler service, either from PowerShell with Restart-Service spooler or from the Services app; here's the part almost nobody tells you: the Cancel button in that queue window doesn't stop anything by itself, it just asks the Print Spooler to drop the job, and if the spooler has already hung, your click goes nowhere — which is exactly why the same two-command trick has worked on every version of Windows since long before Windows 10 existed.

Jake called about this on a Saturday, which is his busiest day, because a customer's repair invoice was stuck "Printing — 1 of 1" for eleven minutes while three more people queued up at the counter behind her. Clicking Cancel did nothing. Unplugging the printer did nothing. By the time he got it sorted, the customer had already left to pay somewhere else, and Jake spent the rest of the day annoyed that a two-minute fix had cost him a sale.

That's the story behind this guide. A stuck print queue is one of the oldest, dumbest problems in Windows, and it has had the same reliable fix since at least the Windows 7 era — but the menus you use to get there have moved twice since we first wrote about this in 2016, and most articles either explain the PowerShell trick without the GUI alternative, or vice versa. This one covers both, for both versions of Windows still in wide use, plus what to do when the trick itself won't run.

Which one is actually happening to you?

Before you start restarting services, it helps to know which of two things is going on, because the fix is slightly different for each.

A single document is stuck, but the printer itself is fine

You print one thing, it hangs at "Printing" or "Deleting — 1 of 1" forever, but new jobs sent to the same printer either also stack up behind it or the printer stays otherwise responsive (you can still print a test page, or another device on the network can still print to it). This is a stuck job, not a dead spooler. Cancel from the queue window sometimes works here; if it doesn't within about 30 seconds, move straight to restarting the spooler.

Nothing will print, the printer icon looks wrong, or Windows says the spooler isn't running

If Devices and Printers shows every printer as offline at once, or Windows tells you "Print Spooler service is not running" when you try to open a queue, the service itself has crashed, not just one job inside it. The fix is the same restart, but you may also need to clear the spool folder by hand afterward, because a crashed spooler often leaves orphaned files behind that block the next job too.

Clear the print queue in Windows 11

Microsoft moved printer management out of the old Devices and Printers control panel and into the Settings app. On current Windows 11 (25H2), the path is Settings > Bluetooth & devices > Printers & scanners. If you'd rather skip the menu hunting, press Win + R, type ms-settings:printers, and hit Enter — that jumps straight there.

Step 1: open the print queue and try Cancel

Select your printer from the list, then choose Open print queue. Right-click the stuck document and select Cancel. Give it 15–30 seconds — the queue window doesn't always refresh instantly. If the job disappears, you're done; if it just sits there, or the whole window freezes while you wait, move to Step 2.

Step 2: restart the Print Spooler service with PowerShell

This is the two-command fix this site has recommended since 2016, and it still works exactly the same way. Open PowerShell (right-click the Start button and choose Terminal, which opens PowerShell by default in current Windows 11 builds) and run:

Restart-Service spooler

Press Enter. There's no confirmation message if it works — the prompt just returns. Go back to the print queue window; a stuck job that Cancel couldn't touch is usually gone the moment the service comes back up, because restarting the spooler doesn't ask the job to stop politely, it wipes the temporary files that describe the job and starts the service fresh. That's the actual mechanism behind why this fixes things Cancel can't: Cancel talks to a service that might already be hung; a restart doesn't ask it anything.

Step 2 (alternative): restart it from Services, no PowerShell required

Some readers would rather click than type, and on a locked-down work laptop PowerShell may be restricted anyway. Press Win + R, type services.msc, and press Enter. Scroll to Print Spooler, right-click it, and choose Restart. If you only see Start (not Restart), that means the service was already stopped; choose Start instead.

Step 3: delete the leftover files by hand (only if the job still shows up)

Occasionally a restart clears the job from the visible queue but the same document reappears a minute later, or a "phantom" job with no name sits there permanently. That means the spool files themselves survived the restart. To remove them:

Stop the Print Spooler first (Services > Print Spooler > right-click > Stop, or run Stop-Service spooler in PowerShell). Then open File Explorer and go to:

C:\Windows\System32\spool\PRINTERS

Delete everything inside that folder — every file in there is a queued job description or its data, and none of it is a system file you need to keep. Then restart the Print Spooler again the same way you stopped it, or via Services > Print Spooler > Start.

Clear the print queue in Windows 10

These steps are the same on both versions once you're inside PowerShell, Services, or the spool folder — the only real difference is how you get to the print queue window in the first place.

Open the queue

Go to Settings > Devices > Printers & scanners, select your printer, choose Open queue, and try Cancel on the stuck document. You can also get there through the older Control Panel > Devices and Printers, double-clicking the printer icon, which still works on Windows 10.

Restart the spooler and clear the folder

Everything from Steps 2 and 3 above — Restart-Service spooler in PowerShell, the Services app route, and clearing C:\Windows\System32\spool\PRINTERS by hand — works identically on Windows 10. This is the exact fix this site first published in December 2016, and it hasn't needed to change; only the menu you use to open the queue window has moved.

One honest note if you're still on Windows 10: support for it ended on October 14, 2025. It still boots, prints, and runs exactly as before — this guide keeps working either way — but Windows 10 no longer receives free security updates unless you're enrolled in Extended Security Updates (ESU), which Microsoft has kept enrollment open for. If your PC meets Windows 11's requirements, that's worth planning around separately from today's print problem; if it doesn't, ESU buys more time without forcing a decision today.

When the restart trick doesn't work

Most of the time, restarting the spooler and clearing the PRINTERS folder ends the problem. When it doesn't, it's almost always one of these five things.

"Access is denied" when you try to delete the spool files

This means the Print Spooler service is still running and holding the files open, even though you thought you stopped it. Go back to Services, confirm Print Spooler actually shows "Stopped" in the Status column (not just that you clicked Stop), and try the delete again. If it still refuses, right-click File Explorer and run it as administrator, then retry the deletion.

The spooler won't restart, or gets stuck on "Stopping"

Print Spooler has dependent services — on some setups these include the printer driver's own background components. If Windows appears to hang while stopping it, wait a full 60 seconds before assuming it's frozen; some drivers are genuinely slow to release. If it never completes, restart the PC. A full reboot restarts every service cleanly, including one that's stuck mid-stop, and this fixes the rare cases where the service itself refuses to respond to Services or PowerShell.

The Restart button is grayed out, or the service says "Disabled"

On a managed work or school laptop, IT policy can disable the Print Spooler service outright, or restrict who can restart it. If Restart is grayed out and you're not signed in as an administrator, this is what's happening — you'll need an admin account or your IT department, and no amount of PowerShell will get around a policy set at that level. This is worth knowing before you spend twenty minutes convinced you're doing something wrong.

The queue is empty, but the printer keeps producing the same page

This is the one that trips people up, because it looks like the fix failed when it actually worked. Many printers — especially networked and older laser models — hold their own copy of a job in onboard memory once Windows has sent it, separate from anything in the Windows queue. Clearing the Windows side stops any new attempts to print, but a page that already left your PC is now the printer's problem, not Windows's. Turn the printer off for about 10 seconds and back on; that clears its internal buffer. This is exactly why the original version of this guide told readers to power off the printer before touching the queue if a job had already started — that advice hasn't changed at all.

The spooler crashes repeatedly, not just once

A single stuck job is normal and forgettable. A spooler that crashes several times a week, on the same PC, usually points at a specific driver rather than bad luck. Open Event Viewer (search for it from the Start menu), look under Windows Logs > System, and filter for Source: Print Spooler — repeated errors around the same time as each crash usually name the printer driver responsible. The fix at that point isn't restarting the service again; it's removing the printer in Settings > Printers & scanners, deleting the driver too if you're offered the option, and reinstalling it from the manufacturer's current download rather than whatever Windows Update originally supplied. This is a different problem from the one this guide is mainly about, but it's the one that makes the fix above feel like it "stopped working" when really it's been correctly clearing the same recurring crash all along.

Windows 11 vs. Windows 10: what's actually different

The underlying fix hasn't moved in years. What's moved is everything around it, and it's worth knowing the traps if you're switching between the two, or upgraded recently and things "look wrong."

Devices and Printers still exists, but Windows 11 wants you elsewhere

The classic Control Panel > Devices and Printers window still opens on most Windows 11 installations, but on newer builds the Control Panel link for printers can redirect straight to the Settings app instead. If you're following an old bookmark or a habit from Windows 10 and it dumps you somewhere unfamiliar, that's expected — use Settings > Bluetooth & devices > Printers & scanners going forward, or the ms-settings:printers shortcut from the Quick Answer box.

The right-click trap

If you're right-clicking a printer icon anywhere in Windows 11 and expecting a full menu like Windows 10 gave you, you may only see a handful of icon buttons. The rest of the options are tucked under Show more options (or press Shift+F10 for the full menu directly). This isn't specific to printers — it's Windows 11's condensed right-click menu everywhere — but it catches people mid-troubleshooting more than almost anywhere else, because the option they need ("Printer properties," for example) is one extra click deeper than it used to be.

Network printers, Remote Desktop, and other edge cases

Everything above assumes the printer is connected to, or shared from, the PC in front of you. A few situations need a slightly different answer.

Shared and network printers

If the printer is shared from another PC, or is a true network printer with its own IP address, its real queue lives wherever that job is actually being processed — on the host PC's spooler, or inside the printer itself. Restarting your spooler clears your PC's copy of the request, which is often enough, but if the job is genuinely stuck on the host machine or inside the printer's own memory, you'll need to run the same restart on the host PC, or power-cycle the printer directly.

Printing through Remote Desktop

When you print from inside a Remote Desktop session to a printer attached to your local PC, Windows creates a redirected printer that only exists for that session. If a job hangs here, closing and reopening the Remote Desktop session often clears it faster than hunting for a spooler to restart, because the redirected printer and its queue are torn down and rebuilt with the session itself.

Printing from a virtual machine

A VM with printer redirection enabled has the same layered problem as Remote Desktop: the VM has its own spooler, and the host PC has another. If a job is stuck, restart the spooler inside the VM first; if that doesn't clear it, the host machine's spooler is the next place to check.

Tablets and no-keyboard devices

Everything here still works with touch and the on-screen keyboard — Settings, the print queue window, and Services are all touch-navigable. The one thing that's genuinely awkward without a physical keyboard is typing PowerShell commands; if that's you, use the Services > Print Spooler > Restart route from Step 2 instead, since it's entirely point-and-tap.

Virtual printers, like Microsoft Print to PDF

Microsoft Print to PDF and similar virtual printers still go through the same Print Spooler as a physical printer, which surprises people the first time a "print" to a PDF file hangs. If a Print to PDF job gets stuck waiting on a save-location dialog you accidentally closed, or waiting on a file name that's already in use in the destination folder, it behaves exactly like a stuck physical job and clears the same way — Cancel from the queue first, then a spooler restart if that doesn't work.

Do you need a third-party tool for this?

Search around and you'll find "print queue cleaner" utilities and general-purpose PC cleanup tools that advertise a print spooler fix among a dozen other things. Here's the honest comparison.

Ethan's take is blunt on this one: "You don't need to install anything to restart a Windows service. If a tool's entire pitch is fixing your print queue, it's running the same two commands you just read, behind a UI, for money." Jake pushed back the first time he heard this — he'd already paid for one of these tools years ago for an unrelated slowdown, and it hadn't done any harm, it just hadn't done much of anything either. That's the realistic verdict: not dangerous, just unnecessary for this specific problem.

The task you'll probably need thirty seconds from now

Once the queue is clear, the next thing people usually run into is the wrong printer picking up the job — especially right after clearing a stuck one, since Windows sometimes shifts which printer it considers "default" once you've removed or re-added something. On Windows 11, go to Settings > Bluetooth & devices > Printers & scanners and turn off Let Windows manage my default printer under Printer preferences if you want a fixed default rather than whichever one you used most recently; on Windows 10 the same toggle lives under Settings > Devices > Printers & scanners. With it off, you pick your default printer once and Windows leaves it alone, which matters if the printer that was stuck is the one you never want as default in the first place.

If the printer itself has started showing as offline since the stuck job, open the same Printers & scanners page, select it, and check that it isn't set to Use Printer Offline — a leftover status Windows sometimes applies automatically after a spooler crash, even once the printer itself is fine again.

The privacy angle: what's actually sitting in those spool files

The files in C:\Windows\System32\spool\PRINTERS aren't just placeholders. Depending on your print settings, they can hold a rendered copy of the document itself — every page, image, and line of text — sitting on disk until the spooler finishes with them. On a shared or shop PC, that matters more than it sounds like it should.

If Jake's shop prints customer ID copies, invoices with account numbers, or anything else sensitive during the day, those files can linger in the spool folder longer than the job appears "in progress" for, especially if a job stalls the way we've been describing in this guide. Clearing the folder as part of fixing a stuck job also clears whatever was sitting inside it — which, on a business PC that other staff or customers might touch, is a reasonable habit to keep even outside a troubleshooting session. It's worth pairing with a wider habit, too: if the PC in question is genuinely shared — a shop counter, a family study, a school lab — treat clearing the spool folder as part of end-of-day cleanup rather than something you only think about while chasing a stuck job.

A one-click shortcut for the next time this happens

If you fix this often enough — a busy front desk, a shared office printer, a shop counter like Jake's — typing the same commands every time gets old. You can wrap the whole fix into a shortcut you double-click.

Open Notepad and paste the following, then save it as clear-print-queue.bat (choose "All Files" as the type in Notepad's save dialog, not .txt):

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

Right-click the saved file and choose Run as administrator whenever a job gets stuck — it stops the spooler, empties the folder, and starts the spooler again in one go, in the correct order that avoids the "access is denied" problem covered earlier. You can also right-click the file, select Properties, and set it to always run as administrator, or pin it to your taskbar so it's one click during a busy Saturday. If this happens often enough to be worth automating further, you can also add the same file to Task Scheduler as a manually-triggered task set to "Run with highest privileges," which skips the administrator prompt each time — useful on a shop PC where you're the only one who'll ever run it, less useful on a shared family computer where you'd rather keep the prompt as a safety check.

Frequently asked questions

Does clicking Cancel on a print job actually stop it?

Sometimes, but not reliably. Cancel asks the Print Spooler service to drop the job; if the spooler is working normally, this usually works within a few seconds. If the spooler itself has hung, Cancel has nothing to talk to, and nothing happens no matter how many times you click it.

Why does my printer keep printing after I cleared the queue?

Because the printer received and stored its own copy of the job before you cleared anything on the Windows side. Clearing the Windows queue stops new attempts; it can't reach into the printer's own memory. Power the printer off for about 10 seconds and back on to clear that.

What is the Print Spooler, in plain terms?

It's the background service that manages every print job on the PC — receiving them, holding them in order, and feeding them to the right printer. It has nothing to do with any other part of Windows, which is why restarting it is safe.

Is it safe to delete everything in the PRINTERS folder?

Yes, as long as you stop the Print Spooler service first. Every file in that folder is queue data for a pending job, never a system file Windows needs to keep between sessions.

Why can't I delete the files in the spool folder?

Almost always because the Print Spooler service is still running and has those files open. Confirm the service actually shows "Stopped" in Services before trying again, and run File Explorer as administrator if it still refuses.

Do I need to restart my whole computer to clear a stuck print job?

No — restarting the Print Spooler service does the same job in seconds. A full reboot is only worth it if the service itself refuses to stop or start, which is uncommon.

Why does Windows 11 show a different printers screen than Windows 10?

Microsoft moved everyday printer management from the old Control Panel into the Settings app: Bluetooth & devices > Printers & scanners on Windows 11, versus Devices > Printers & scanners on Windows 10. The underlying spooler and the fix in this guide are identical on both.

Can I clear the print queue without opening PowerShell?

Yes. Press Win + R, type services.msc, find Print Spooler, right-click it, and choose Restart. It does exactly what the PowerShell command does, with no typing required.

The print queue looks empty, but the printer still says it's stuck. What now?

Check the printer's own small screen or status light if it has one — the fault may now be entirely on the printer's side (out of paper, a jam, low toner) rather than a Windows queue problem, since you've already confirmed Windows has nothing pending.

Does clearing the print queue delete the document I was trying to print?

No. It only deletes the temporary print job Windows created from that document. The original file on your PC, wherever you saved it, is untouched.

Why does the queue clear on my PC but a coworker still sees the stuck job?

Because a shared or networked printer's real queue often lives on the host PC or inside the printer, not on every individual computer that sends jobs to it. Restarting your own spooler only clears your PC's local copy of the request.

Can a stuck print job be a sign of a bigger problem?

Occasionally. If the spooler crashes repeatedly on the same PC over several days rather than as a one-off, that's worth mentioning to whoever manages the printer or PC, since a driver conflict or a failing print server can look identical to an ordinary stuck job at first.

Is there a way to stop this from happening again?

Not reliably — stuck jobs are usually caused by a momentary driver hiccup or a printer going offline mid-job, which isn't something you can prevent from the Windows side every time. Keeping the shortcut from this guide handy is the realistic answer, not a permanent fix.

Do I need third-party software to manage the print queue?

No. Everything in this guide uses tools already built into Windows. Third-party "print queue cleaner" tools generally restart the same service behind a nicer interface, which isn't worth installing extra software for.

Why does my printer keep showing as offline after I fixed the queue?

Windows sometimes leaves a printer marked "Use Printer Offline" after a spooler crash, even though the printer itself is working fine. Open Printers & scanners, select the printer, and turn that setting off.

The spooler keeps crashing on its own, not just when I print something. Is that different?

Yes. A one-off stuck job is normal; a spooler that crashes repeatedly over days usually points to a specific printer driver, checkable in Event Viewer under Windows Logs > System. The lasting fix there is reinstalling the driver from the manufacturer, not restarting the service again each time.

Revision note. Originally published December 25, 2016. Rewritten August 16, 2026 for Windows 11 and Windows 10. The fix itself — restarting the Print Spooler service — hasn't changed since we first covered it; what's moved is the menu you use to reach the print queue, as Microsoft shifted printer management from Control Panel into the Settings app over the years since. If you landed here mid-Saturday-rush like Jake did, the two-command fix above should have you back up and printing before your next customer walks in.