Computer Repair · October 27, 2026 · ComputerKing Team

Clicked Print and Nothing Happens? A Complete Guide to Stuck Print Jobs and Queues

Clicked Print and nothing happens? Very often the printer is not broken — one job stuck in the print queue is blocking the whole line: open the queue to see which job is stuck and its status, then work from gentlest to strongest — cancel, restart the print service, and only then consider stopping the service and clearing the spool folder, confirming both the computer queue and the printer panel.

Key Summary

• A stuck print queue is not the same as a broken printer: one damaged or stuck print job can block the whole queue, so nothing behind it prints.
• The first step is not reinstalling the driver. Open the print queue and see which job is stuck, and whether its status is Waiting, Printing, Deleting, Error, or Paused — each status calls for a different response.
• Clear in order from gentlest to strongest: cancel one job, then cancel all jobs, then restart the print service; only then stop the service and clear the spool folder. That last step needs administrator rights, and cleared jobs must be printed again.
• Cancelling on the computer and cancelling on the printer panel are two different things: a job already inside the printer may keep printing until you cancel it on the panel.
• Paper jams, empty ink, and network dropouts are already covered in earlier articles and are only cross-referenced here; this article is about the queue itself, a gap in the earlier coverage. All repair and consumable prices are quoted individually.

Introduction

You have probably met this situation: you click Print, wait a full minute, and the printer does not move at all. You click Print a few more times, and things get worse — a dozen jobs are now lined up in the queue and none of them moves. It printed fine yesterday, and today the whole queue has stopped dead. Many people's first reaction is that the printer is broken, or they immediately reinstall the driver, and after an hour of trying they still cannot print.

Very often, the problem is not the printer at all, but the print queue: one job has got stuck and is blocking the whole queue, so every job behind it is waiting in vain. This is completely different from a paper jam, empty ink, or a printer the computer cannot see, and it needs a different fix. Earlier articles have already covered basic paper-jam steps (#81), network dropouts and post-update changes (#84), and buying, maintaining, and retiring a printer (#106); this article does not rewrite those. It covers one thing only: why a print queue gets stuck, how to clear it from gentlest to strongest, how to tell a queue problem apart from other problems, and how to stop it happening all the time.

1. What Is a Print Queue? Why One Stuck Job Blocks Everything

When you click Print, the document does not go straight to the printer. Your computer first hands the print job to a background service — Print Spooler on Windows — which lines the jobs up in a queue and sends them to the printer one at a time. The printer handles only one job at a time, finishing one before it starts the next. So the queue is like a single-lane road: if the first car breaks down, every car behind it is stuck, however small or urgent those later documents are.

A job can get stuck for many reasons: a damaged file, a very large file, a driver that does not handle the file format, the printer going offline halfway through, or the printer being paused. The awkward part is that a stuck job does not always disappear by itself. It can sit in a "Printing" or "Deleting" state for a long time, freezing the whole queue. Clicking Print again only makes the queue longer; it solves nothing.

Table 1: Queue Status Guide

Remember one principle: a job in the queue is not your original document. Cancelling a queue job only cancels that print request; the original file on your computer is not deleted and can be printed again later. Conversely, clearing the queue does not reprint anything automatically — you have to click Print again yourself afterwards.

2. Triage First: Four Questions Before You Touch the Queue

Before clearing the queue, answer four questions. Otherwise you may clear the wrong queue, or clear it and still not print, because the real cause was never in the queue at all.

Question 1: Is the printer itself responding?

Check the printer panel for errors, out-of-paper, out-of-ink, or paper-jam messages. If the panel already says there is a paper jam or no ink, clearing the queue will not help; deal with what the panel says first. Paper-jam basics are in article #81, and ink and toner diagnosis is in section 1 of article #84.

Question 2: Is it only one computer, or all devices?

Try printing one page from another computer or phone. If another device prints, the problem leans towards the first computer's queue, driver, or settings. If no device prints, the problem leans towards the printer itself or the network, and you should go back to the network triage steps in section 4 of article #84 instead of working only on one computer's queue.

Question 3: Which job in the queue is stuck?

Open the print queue and look at the first job: which file is it, what is its status, and how long has it been stuck? Very often the whole queue is blocked by a single huge document or one oddly formatted file at the front. Identify the culprit before cancelling, and do not clear the whole queue at once without thinking — especially on a shared printer, where clearing everything also cancels other people's jobs.

Question 4: Did the job go to the wrong queue?

Article #84 describes an easily missed situation: the computer shows two printers with the same name, one a driverless queue and one a manufacturer-driver queue, and a job sent to the unused one looks as if it has "disappeared" or "never prints". Before you open a queue, confirm that the queue you are looking at is the same printer you chose when you clicked Print; do not clear the wrong queue.

3. Windows: Clear the Queue from Gentlest to Strongest

The steps below run from gentlest to strongest. After each step, print a one-page test document; if it prints, stop — do not run through all the steps at once. The steps follow Microsoft's official support documentation, listed under Sources at the end.

Step 1: Cancel one job in the queue

Go to Settings, Bluetooth and devices, Printers and scanners, choose your printer, then choose Open print queue. In the queue, right-click the stuck job and choose Cancel. If only one job is stuck, cancelling it should let the jobs behind it start moving. This is the gentlest step, needs no administrator rights, and any user can do it.

Step 2: Cancel all jobs

If many jobs are jammed, or you cannot tell which one is the culprit, use Cancel all in the queue window to clear everything at once. Remember that every queued document then has to be printed again; nothing reprints automatically. On a shared printer, tell other users first, so you do not cancel a document someone is rushing to submit.

Step 3: Restart the print service

If a job says "Deleting" and never goes away, or the queue still does not move after cancelling, restart the Print Spooler service. Press the Windows key plus R, type services.msc, find Print Spooler, right-click it, and choose Restart. Restarting the service refreshes the queue, and many "Deleting" cases are fixed at this step. This step does not delete your original files; it only refreshes the queue.

Step 4: Stop the service and clear the spool folder (last resort)

If the first three steps all fail, Microsoft's official documentation suggests this method: in services.msc, Stop the Print Spooler service, then in File Explorer open C:\Windows\System32\spool\PRINTERS, delete all files inside it, then go back to services.msc and Start the service. Three points must be made clearly. First, this step needs administrator rights; on a company computer, ask IT first and do not stop the service on a managed computer on your own. Second, delete only the files inside the PRINTERS folder — never delete the PRINTERS folder itself. Third, the files inside that folder are the queued print jobs; once deleted they are gone and must be printed again.

After step 4, do not immediately resend a document hundreds of pages long. Print a one-page test document first to confirm the queue is moving and the printer is producing paper, and only then resend the original document. This habit stops one faulty large file from blocking the whole queue again at once.

4. macOS: Queue, Restart, and Resetting the Printing System, in That Order

The macOS order is similar to Windows, but the last step costs much more, so never shuffle the order.

Step 1: Open the print queue and cancel the job

Go to System Settings, Printers and Scanners, choose your printer, click Open Print Queue, select the stuck job, and click Cancel or Delete. Wait a little after cancelling to see whether the jobs behind it start moving.

Step 2: Restart the printer and the Mac

If cancelling does not help, restart the printer and the Mac one at a time, waiting for each to finish starting before starting the next. Restarting both at once, or in the wrong order, can leave network discovery and queue state more confused. Article #84, section 4, makes the same point about restart order for network dropouts.

Step 3: Resetting the printing system is a last resort, not a first step

If none of the above works, macOS offers a Reset printing system option: Control-click in an empty area of the printer list and choose Reset printing system. But the consequence must be clear: this deletes all printer and scanner settings, and every printer has to be added again afterwards, with previous print presets gone too. Article #84 already stresses that this is a last resort, not a first step. Before doing it, make sure you have the setup details for every printer, especially network addresses and drivers, or the reset may leave you worse off than before.

5. Phone, Network, and Shared Printing: Queue Details People Miss

Where did a phone print job go?

A job printed from a phone through AirPrint or a manufacturer app may not appear in your computer's queue at all. If a phone print fails, do not look only in the computer queue; check the phone's print settings or the printer panel for the job's status. Phone jobs and computer jobs going to different queues is a very common misunderstanding.

Cancelling on the panel and cancelling on the computer are two different things

Once a job has started entering the printer, the printer itself holds an internal queue or memory buffer. Cancelling on the computer at that point may only cancel the computer's side of the transfer, while the part already inside the printer keeps printing until it finishes. If the computer queue is already empty but the printer keeps printing, cancel on the printer panel, following your model's manual for cancelling a job in progress. The reverse also applies: cancelling on the panel may leave the computer queue job still sitting there. Confirm both sides are clear before calling the queue clean.

Shared printing: a stuck host queue blocks everyone

Article #84 explains that a shared printer depends on its host computer staying on; if the host shuts down or sleeps, nobody else can print. The same logic applies to queues: if the host's queue is stuck, every computer printing through the share is stuck too. In that case, clearing your own computer's queue does little; check the host computer's queue, clear it there, and only then will others get through. In a company, hand this kind of problem to IT rather than cancelling jobs on someone else's host computer.

What if a job stops halfway through?

If a document stops halfway, reprinting may start from the beginning or resume after the stuck page, depending on the model and driver. To avoid wasting paper and ink, check how many pages already printed, then in the print dialogue choose only the page range that has not printed yet, instead of reprinting the whole document. Many people miss this detail and end up printing a long document twice.

6. Five Deeper Reasons a Queue Keeps Getting Stuck

Clearing a queue once does not mean the problem is solved. If the same machine keeps getting stuck, find the deeper cause, or the queue will block again next week.

Reason 1: One particular file is faulty

If one file blocks the queue every time while other files print smoothly, the file itself is suspect: a damaged file, an oddly formatted file, or a file with missing fonts can all stop the driver from processing it. The test is simple: convert that file to PDF and print it again, or print a brand-new one-page test document. If the converted version prints, the problem was the original file, not the machine.

Reason 2: The file is too large to send in one go

A document hundreds of pages long with high-resolution images puts heavy pressure on the queue and the printer's memory in one go. The practical approach is to print in sections: print the first few pages to confirm everything is right, then print the rest in sections. Sending a whole large file at once when you are rushing to meet a deadline is the easiest way to block a queue.

Reason 3: Drivers are duplicated or out of date

Two queues for the same printer on one computer, or a driver that has not been updated for a long time, can send jobs to the wrong queue or fail to handle a new format, so the queue keeps getting stuck. Article #84 covers how to tell two identical printers apart and how to download the driver from the manufacturer's site for your exact model; this article does not repeat those steps, but this is the most worthwhile item to check for a queue that keeps blocking.

Reason 4: The printer's address changed, but the queue still points at the old one

A network printer given an address by DHCP may get a different address after a restart or when its lease expires, and a computer queue remembering the old address can no longer find the machine, so jobs sit in the queue indefinitely. Article #84, section 4, explains the fix — giving the printer a fixed address from the router, or setting a fixed address on the printer. This article only notes the point: a job stuck on "Printing" for a long time while the machine shows no reaction at all is one case where a changed address belongs on the checklist.

Reason 5: The printer itself is stuck in a paused or offline state

Some printers enter a paused or offline state because of out-of-paper, an open cover, or deep sleep power saving, and jobs in the queue just keep waiting. Before clearing a queue, confirm the printer panel says it is ready; do not keep clearing and reprinting while the machine itself is not ready.

Table 2: Symptom and Response Guide

7. Six Things Not to Do

• Do not keep clicking Print. While the queue is blocked, every extra click adds another job to the line, making the queue longer and harder to clear.
• Do not delete spool folder files while the service is still running. Files may fail to delete, or reappear at once, and the queue state may become more confused.
• Do not delete the wrong folder. Delete only the files inside the PRINTERS folder — never the folder itself, and never files in other system folders.
• Do not treat resetting the printing system as a first step. On macOS, resetting deletes all printer settings, at a high cost, so it belongs last.
• Do not stop the print service or clear a whole queue on a company computer without asking. On a managed computer or a shared printer, the queue may hold other people's jobs; ask IT or tell other users first.
• Do not open the machine up to fix a queue problem. A queue problem is a software and settings problem. Taking apart the machine, the fuser, or the power board has nothing to do with it, and hot or live parts must be left to professionals.

8. Prevention: A Three-Second Check Before Every Print

Preventing stuck queues needs nothing complicated. Three habits are enough:

1. Before clicking Print, check you chose the right printer. This matters most when the computer shows two printers with the same name: choosing the wrong queue sends the job to the unused side, which looks like "nothing prints".

2. Print one page of a large file first. For a document dozens of pages long, print the first page to confirm format, paper, and copy count are all right, then print the rest — do not send everything at once.

3. For shared printing, confirm the host is on. When printing through a share, if the host is off or asleep, everyone else's jobs pile up in the host queue. Asking whether the host is on before printing saves a lot of time.

One more good habit is to glance at the queue after printing and confirm it is genuinely empty. If a queue permanently holds old "Error" or "Deleting" jobs, something has been left unresolved; deal with it while you have time, not when you are rushing to meet a deadline.

FAQ

Q: I clicked Print but my job does not appear in the queue at all. Is the printer broken?

A: Not necessarily. First confirm that the queue you are looking at is the same printer you chose when you clicked Print — with two printers of the same name on one computer, it is easy to look at the wrong queue. Then confirm the job did not go to a phone's queue or another computer's queue. Only after both checks should you suspect a driver or network problem and go back to the triage steps in section 4 of article #84.

Q: A job says "Deleting" and has stayed there for a long time. What should I do?

A: Do not keep clicking Cancel. Wait a little, then restart the print service; that step alone fixes many cases. If it still will not delete after a service restart, then consider stopping the service and clearing the spool folder. That step needs administrator rights, so ask IT first on a company computer, and cleared jobs must be printed again.

Q: Will clearing the spool folder delete my original documents?

A: No. Clearing removes only the print jobs waiting in the queue; the original files on your computer are not deleted. But note that cleared jobs do not reprint automatically — you have to click Print again yourself, and you should first print a one-page test document to confirm the queue is moving again.

Q: The queue is already empty, but the printer keeps printing. How do I stop it?

A: Because the job has already entered the printer, the printer's own internal queue is still processing it. Cancel the job in progress on the printer panel, following your model's manual. The computer queue and the printer panel both have to be confirmed clear before the queue counts as clean.

Q: Why does one particular file block the queue every time, while other files print fine?

A: The problem is very likely in that file — for example a damaged file, an odd format, or missing fonts. Test by converting the file to PDF and printing it again, or by printing a brand-new one-page test document. If the converted version prints, the problem was the original file, not the machine or the queue.

Q: Before resetting the printing system on macOS, what must I prepare?

A: Prepare the setup details for every printer, including network addresses and drivers, because resetting deletes all printer and scanner settings and every printer has to be added again afterwards, with previous print presets gone too. That is why resetting is only a last resort, never a first step.

Q: On a shared printer, the host queue is stuck. Does clearing the queue on my own computer help?

A: Very little. Shared print jobs ultimately go through the host's queue to the printer, so while the host queue is stuck, nobody else gets through no matter how much they clear on their own computers. Check the host computer's queue, clear it there, and only then will others get through. In a company, hand this kind of problem to IT.

Q: When should I stop immediately instead of clearing the queue or trying again?

A: If the printer smells strange, smokes, leaks ink or toner seriously, has a damaged power cable or plug, or has a jam you cannot remove, switch it off and unplug it at once, do not try printing again, and get a professional. A queue problem itself never involves opening the machine, and any work on hot or high-voltage parts must stop. Repair and consumable prices are quoted individually.

Summary

The most common mistake with a stuck print queue is not that the technique is hard, but that the order is wrong: reinstalling the driver straight away, resetting the printing system straight away, or clicking Print over and over only makes the queue longer. The correct order is actually simple: first look at which job in the queue is stuck, then work from gentlest to strongest — cancel, restart the service, and only then consider clearing the spool folder or resetting the printing system. After each step, print a one-page test document to confirm. Once you separate the computer queue from the printer panel, the phone queue from the computer queue, and a shared host's queue from your own computer's queue, many queue problems can be solved without opening the machine. If a queue will not clear no matter what, the same file blocks it every time, or the machine shows a hardware error, that is when to stop and get help.

Sources

• Microsoft Support: Fix print job stuck in queue errors in Windows — https://support.microsoft.com/en-us/windows/hardware/printer/fix-print-job-stuck-in-queue-errors-in-windows
• Microsoft Support: Fix print spooler service not running errors in Windows — https://support.microsoft.com/en-us/windows/hardware/printer/fix-print-spooler-service-not-running-errors-in-windows
• ComputerKing earlier article: Printer common issues — https://www.computerking.hk/blog/printer-common-issues/
• ComputerKing earlier article: Printer common issues, part 2 — https://www.computerking.hk/blog/printer-common-issues-part2/
• ComputerKing earlier article: Printer buy, maintain, retire guide — https://www.computerking.hk/blog/printer-buy-maintain-retire-guide/

*This article is general information only. Actual steps depend on your model; always follow your own machine's manual. Work involving heat, live parts, or opening the machine should be left to professionals. Repair and consumable prices are quoted individually.*