The printer didn't show any indication of a jam other than to simply be 'processing' a print job. This worked for me on Windows Server R2, but I chose only to delete today's files and nothing older.
I am not sure if this folder stores jobs if a printer has such functionality with its drivers. The exe files were tied to a couple of TMP files somehow. I skipped those and my printer queue was fixed. If you want to surgically delete only files associated with the problem printer's queue, then delete files with matching timestamps rather than the entire directory's contents.
Home Windows General Windows How-tos. Clearing a Print Queue when Jobs won't Delete. General Windows. David Scammell This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Last Updated: Aug 22, 1 Minute Read. Reply 8. Facebook Twitter Reddit LinkedIn. Main Areas of Contribution:. Track Progress.
Earn Credits. They arrive first in the spooler, which is a program that manages all print jobs. The spooler is useful as it enables you to change the order of pending print jobs or delete them. Unplug all wire connections and plug them back before the system reboot is complete. You have tried the simple fixes outlined above to no avail. Have no fear. This is a common issue. You have to manually disable the Print Spooler service and delete the files in the queue.
The process is easy. The fastest way to clear the print queue is through the command prompt. All you have to do is enter and run a few commands:. Any other possibilities? I believe so. It is just an object. If the spool file is generated by a batch job under the current user , is it possible to change its authority as well? Do I need to specify library name then?
No, a spool file is not a first-class object at the OS level. It is created in a job, also not a first-class object, and a completed job will continue to exist on the system until all its spool files are gone. People sometimes confuse spool file with print files, which might perhaps be thought of as templates for the creation of spool files.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses.
Featured on Meta. Any behavior that appears to violate End user license agreements, including providing product keys or links to pirated software. Unsolicited bulk mail or bulk advertising.
Any link to or advocacy of virus, spyware, malware, or phishing sites. Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct. Any image, link, or discussion related to child pornography, child nudity, or other child abuse or exploitation. User Replied on January 31, Sometimes failed print jobs get stuck in the print queue and just won't delete the way you would like Sometimes when print jobs fail they clog up the print queue and they might not show up when you check to see what's printing.
In that case you need to delete the clogged up print jobs manually but first you have to stop the Print Spooler Service. Then from the Command Prompt Window enter the following commands one at a time pressing the Enter key after each:. Open Windows Explorer and navigate to this folder, select all the files in the folder and choose to delete them:. Close all the windows and dialog boxes and choose to restart your system which will automatically restart the Print Spooler Service.
0コメント