Print queue clears but printer reprints old job — NVRAM purge
Joe B.
Reviewed for technical accuracy
Specialities: Windows 11/10, Printers, Networking, Group Policy, Print Servers
Print queue clears but printer reprints old job — stuck memory, stored jobs, NVRAM reset
Quick answer: the accepted fix
Accepted fix when the print queue shows empty but the printer reprints an old job: hard-clear the Windows print spooler (stop service and delete files), turn off “Keep printed documents,” delete any stored/secure jobs from the printer control panel or Embedded Web Server, then perform a cold reset / NVRAM initialization to purge corrupt job data in memory. Finally, re-add the printer with a clean driver and test with a simple document.
Why the print queue clears but the printer keeps reprinting old jobs
When you see an empty Windows print queue but the device reprints the same document repeatedly, the job is usually stuck in the printer’s own memory, not in the PC spooler. Features like Job Storage, Quick Copy, Proof & Hold, Reprint Last Job or “reprint after jam” can keep a copy of the last job in NVRAM. If the firmware glitches or the job gets corrupted, the printer may replay that job on every reboot or whenever it receives new data, creating a ghost-print loop until you delete the stored job and/or reset NVRAM.
How to verify the print memory and NVRAM purge worked
After clearing queues and doing a printer NVRAM reset, power the device back on and wait. It should sit at Ready without pulling paper. Send a single test page (Windows test page or one-page PDF) and confirm that only that job prints once, with no surprise reprints. Leave the printer idle for a few minutes and reboot it again. If no old jobs come out and the print queue stays empty, your stuck job in printer memory has been successfully purged.
Stuck jobs reprinting — quick troubleshooting tips
Most “queue empty but printer still prints” issues come from stored jobs in device memory or a corrupted NVRAM record.
Quick path: reset the Windows print spooler → disable “Keep printed documents” → clear stored/secure jobs on the printer panel or Embedded Web Server → update firmware → if the printer still reprints old jobs, perform a controlled cold reset / NVRAM initialization following the vendor’s instructions. This clears ghost jobs from non-volatile memory and stops repeated printing loops on HP, Brother, Canon, Xerox and other models.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment or printer model, please consult a verified expert on Whizz-Tech before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.
Expert will respond in minutes
We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.
Save time & money
No scheduling hassles or expensive consults. Membership can save you significant time and money each month.
FAQ
Why does my printer keep reprinting an old document when the queue is empty?
In many cases the job is stuck in the printer’s own memory, not in Windows. Features like Job Storage, Quick Copy, Reprint Last Job or “reprint after jam” can save a copy in NVRAM. If that record becomes corrupt, the device can reprint the same job every time it powers on until you clear stored jobs or perform an NVRAM reset.
Will an NVRAM reset delete my printer’s network settings?
Often yes. A full NVRAM initialization or cold reset typically restores factory defaults — including IP configuration, tray settings, language and sometimes the admin password. Always print a configuration page and note your current IP and options before resetting so you can re-enter them afterwards.
Can I fix repeated print jobs without touching NVRAM?
Sometimes. Start by resetting the Windows print spooler, deleting all files in C:\Windows\System32\spool\PRINTERS, disabling “Keep printed documents,” and deleting any stored/secure jobs from the printer menus. If the printer still reprints the old job on boot, an NVRAM purge is usually required.
What if the printer is shared from a server?
For a shared printer, clear jobs and restart the Print Spooler on the print server and on clients, remove duplicate direct-IP queues, then perform the NVRAM reset on the device. If any server queue keeps resending the bad job, the printer will fall back into the same loop.
| Symptom | Likely cause | Quick fix |
|---|---|---|
| Print queue empty but old job reprints on boot | Job stored in printer memory / NVRAM | Delete stored jobs on panel/EWS; perform cold reset / NVRAM init |
| Old document reprints after every new job | “Reprint last job” or Job Storage enabled | Disable reprint features; clear stored jobs; update firmware |
| Multiple users see the same ghost job | Stuck job on print server or direct-IP queues | Clear server spooler; remove duplicate queues; then purge printer NVRAM |
| Queue shows jobs, but deleting doesn’t help | Corrupt Windows spool files | Stop spooler; delete files in ...\spool\PRINTERS; restart spooler |
Step-by-step (Windows 10/11)
- On each affected PC (and any print server), stop the Print Spooler service, delete all files in
C:\Windows\System32\spool\PRINTERS, then restart the service. - Open Devices and Printers → Printer properties → Advanced and uncheck “Keep printed documents” so successful jobs aren’t retained in the queue.
- Remove and re-add the printer using a clean driver; avoid old or duplicate drivers that may replay cached jobs.
- On the printer panel or Embedded Web Server, delete stored/secure jobs and, if the device still reprints old documents, perform a vendor-recommended NVRAM / cold reset and then reconfigure IP and settings.
Note for macOS and mixed environments
- On macOS, open System Settings → Printers & Scanners, select the printer and choose Open Print Queue. Delete all jobs, then test. If jobs won’t clear, consider Reset printing system… to remove all printers and queues.
- In mixed Mac/Windows networks, clear queues on all platforms first, then purge stored jobs and NVRAM on the printer so it doesn’t re-play a job from device memory when any OS sends new prints.
Sources
- HP Support — Print jobs stuck in print queue (Windows/macOS)
- PaperPapers — Do printers have memory? How to clear history
- Metrofuser — NVRAM reset for HP laser printers
Filed under: Print queue & spooler (Windows/macOS)
Related articles
- Print queue stuck — full spooler reset for Windows 11/10
- Print job stuck on “Processing” — why won’t it start printing?
- Can print Word but PDF won’t print — Acrobat/Edge fixes (spooler, driver, “Print as Image”)
- Print job stuck as “Deleting” — hard spooler reset
- My printer queue is stuck and won’t clear — what can I safely check?
- Printer queue is full and nothing prints — what happened?
- Printer queue says “Rendering” forever — WSD → TCP/IP swap
- Printer stuck on “Sending to printer” — nothing comes out. What do I check first?