I'd like to open this question up to the community, as my revised question has yet to be answered. The 'method 2' procedure did work ....... but the problem persists. My revised question is stated after the method 2 solution.
Pinaki Mohanty posted on April 2, 2013 -
If the documents have got stuck in the queue, you can turn off the print spooler service, delete the pending documents and then restart the service again to print the documents.
b) Type “Services.msc” inside the box and press Enter.
c) Click on Print Spooler service and right click on it.
d) Click the "Stop" button to stop the Print Spooler Service if it is running.
e) Check whether the Startup type is set to Automatic. If not, then set it to Automatic.
f) Go to the following location and delete all the pending documents from the “Printer”. “C:\WINDOWS\system32\spool\PRINTERS”
g) Delete all the queued print jobs (select and delete all the files) in the folder so the folder is devoid of pending print jobs. The folder should be empty when you are done.
h) Restart your system and check the Print Spooler Service again to be sure the Print Spooler Service restarts automatically on reboot (since the Startup type is set to Automatic).
Thanks - I too was having the same problem as Ann concerning my new Windows 8 laptop with
documents stuck in the print queue. Your method 2 corrected clearing out the print queue.
To answer your initial questions to Ann - I'm using a HP Officejet J6480 as a networked printer attached to my router. I am not having this problem on the Windows 7 laptop which is also on my network. So, it appears to be a problem with Windows 8
My issue is this - after printing some documents (word, printer test pages, etc.), I still receive a message stating 'error printing document to printer', even though the document printed. I then have to go into the print queue and delete the document that printed. Once a document gets stuck in the print queue, all subsequent documents will not print.
Will Windows 8.1 correct this or is 'method 2' continue to be a work-around for this problem while an update is released to correct this problem?