Document Stuck In Print Queue – How To Fix

An easy fix for a document stuck in print queue. This is a common problem with printers and means that the submitted document will not print – and stops any further documents from printing.

You will not receive an error message and the status of the document in the print queue will stay as ‘printing’ forever…

It is always worth trying to delete the document first but often that will not work – the status may change to ‘deleting in progress’ but never actually delete.

Until it is deleted properly, no further documents can be printed because they are in a queue (the first job submitted must be printed before any subsequent jobs can progress). So if you keep trying to print more to ‘test things’ you will just end up with lots more print jobs queued up.

How To Fix A Document Stuck In Print Queue

You will need to clear the print queue manually so that all the print jobs currently in the queue are deleted properly. Once the queue is empty you should then be able to print new documents without any problems.

To do this, follow the 5 steps below – they are the same for Windows 10, Windows 8, Windows 7 and Vista:

1. Click ‘Start’ and type CMD into the search box. Right click on the ‘CMD’ program in the search results and select ‘Run as administrator’.

2. You may now see a User Account Control message asking “Do you want to allow the following program to make changes to this computer?”. Click on ‘Yes’ to confirm.

This will open an elevated (Administrator) level Command Prompt window (as shown below, with all subsequent steps completed).

restart print spooler
Clearing the print queue

3. Type net stop spooler then press the Enter key.

[Tip: if you see a ‘System Error 5‘ error message then you didn’t choose ‘Run as administrator’ in step 1 – start over again]

4. Type del %windir%\system32\spool\printers\*.* /q then press the Enter key (Note: the only spaces in this command are a single space between del and %, and a single space between * and /q)

5. Type net start spooler then press the Enter key.

Close the Command Prompt window. This should have cleared the print queue (all print jobs have been deleted) and you can now submit new jobs for printing :-)

What Do These Commands Do?

The CMD program is a legacy program from the pre-Windows days of Microsoft DOS but it is still a very useful way to enter system commands:

‘net stop spooler’ – stop print spooler service (basically the ‘print queue’). We need to stop this service from running before we can delete any documents in it.

‘del’ command – deletes everything currently held in the print queue folder, including any ‘stuck’ documents.

‘net start spooler’ – restart print spooler service, so that it is ready to accept new print requests.

What If This Keeps Happening?

If you occasionally get a document stuck in print queue error, it is likely just due to an incompatibility with the actual data you sent to be printed.

This is especially common when trying to print a whole webpage because it may have unusual fonts or styles that the printer is unable to convert into printed output – run the above fix to clear the print queue.

Note: if you then try to print the same webpage again it will likely just get stuck again – because the printer still can’t convert it… Always look for a ‘print friendly’ or ‘click to print’ button on the webpage which will convert the page into a format more suitable for printing.

However, if you regularly encounter this error then it is most likely an issue with your printer drivers (software) – the ideal solution is to download/update new drivers direct from your printer manufacturer’s website.

If you have an old printer and there are no driver updates available, it may be the right time to upgrade to a new printer – about $50 buys a basic WiFi printer with good reviews.

Other causes of a document stuck in print queue may include a misconfigured printer e.g. trying to network print to an IP address that doesn’t exist – uninstalling the printer software then downloading the latest version and installing from scratch should fix this.

You could also try running a Windows Troubleshooter for printers – this could repeat our fix above but may also fix any other Windows errors that could stop printing, or at least inform you of the cause.

56 thoughts on “Document Stuck In Print Queue – How To Fix”

  1. Here is what works for me. I have a new HP PageWide inkjet 452dn printer connected via USB to my computer. Print jobs were consistently getting stuck in the queue. Sometimes they would print but not leave the queue. Once stuck there, nothing else would print. There are lots of procedures using Services, Print Spooler, clear the queue but the problem just occurs again after you clear the queue. Well, first of all HP has a neat little application called HP Print and Scan Doctor. Run that and it will clear the print queue and get you back in business printing. Problem still arises afterwards, so you may have to run the application often. Then I discovered that by selecting “Customize your printer”, “Advanced”, “Spool print docs …”, and select the option to “Start printing after last page is spooled” that I now very rarely get a document stuck in the print queue. Hope it works for you.

  2. This worked for me…shut down your computer. Unplug everything,,,wait 60 seconds. Plug everything back in, turn your computer back on and voila…it’s not stuck in queue anymore, print what you need to.

  3. The problem I had was the latest IE browser. It was causing the problem so uninstalled the latest update and that fixed it and now I use motzilla without any issues.

  4. This is great it works! I feel like a pro! My Lenovo lap top is now printing to my HP printer. Thanks.

    • @Blanche – ‘start’ refers to what used to be called the Start button but is now just the Windows button – it’s the button at the very bottom left of your screen (which you click on to shut down or open a program etc)

  5. This method *worked* today on my laptop running Windows 8.1.
    And the printer was an HP psc 1350 all-in-one printer (about 11 years old).

    Just wanted Windows 8.1 users to know.

Comments are closed.