Printer Only Prints Test Pages, Documents Do Not Print, Queue Clears, Blank Pages, and App Printing Fails

A printer only prints test pages problem usually means the printer can respond to at least one local or diagnostic path, but normal document printing is breaking somewhere else. 

Problem: HP printer prints a test page but documents do not print on Windows 11

What users observed: A Windows 11 user with an HP ENVY 4511 reported that the printer was ready, set as the default printer, and could print a test page. Normal documents did not print. HP Smart popped up and hung, and the print queue showed no waiting documents. The user could print an HP Welcome page but still could not print documents from File Explorer.

What was tried: Users hid the printer, uninstalled and reinstalled HP Smart, uninstalled and reinstalled the printer, checked the print queue, and compared the diagnostic page with normal document output. The case stayed with the Windows 11 printer path, print queue, HP Smart, and wireless setup rather than a paper feed failure.

How this played out: The working path was a full rebuild of the printer setup rather than another simple test-page attempt. The user removed and reinstalled the printer and HP Smart, then completed wireless setup from the printer’s own touch panel by selecting the router and entering the router password directly on the printer. After the printer was reattached to the correct Wi-Fi network from the device side, normal document printing started working again.

Problem: HP printer prints a test page but HP Smart hangs before documents print

What users observed: In the same HP ENVY 4511 case, the printer could produce a test page, but HP Smart opened and hung when the user attempted normal document printing. The print queue did not show pending documents, which made the failure different from a print queue freeze where jobs remain visibly stuck.

What was tried: Users removed and reinstalled HP Smart, removed and reinstalled the printer, and tried to print from File Explorer again.

How this played out: The practical repair was not limited to HP Smart. The working sequence combined app reinstall, printer reinstall, and wireless setup from the printer panel itself. The final usable state came after the printer joined the router again through its own network setup screen, which restored the document-printing route that HP Smart alone had not fixed.

Problem: Printer prints test page but documents output blank pages after a computer upgrade

What users observed: A Windows 10 user reported that the printer worked before a computer upgrade, then only printed the test page afterward. When printing from an Office application or browser, the output was blank. The printer status showed the job in the queue, but nothing useful came out.

What was tried: The user checked the printer status and compared the working test page with Office and browser output. The case stayed with printer only prints test pages, application output, and Windows printing after upgrade.

How this played out: The working direction was to treat the upgrade as having broken the computer-side print path, not the printer engine. Users in this situation moved through driver reinstall, default printer checks, application printer selection, queue cleanup, and port verification. The printed test page kept the focus on the upgraded computer’s software route rather than the printer’s basic ability to print.

Problem: Printer prints test page but Windows update stops normal documents

What users observed: A Windows 10 user reported that the printer still printed the test page but otherwise would not print. The only known change was that Windows had updated itself. The user tried troubleshooting and restarting the print spooler, but pending documents still did not print.

What was tried: Users ran troubleshooting, restarted the print spooler, checked the pending documents count, and refreshed print tasks.

How this played out: The practical repair path was to clear the Windows print state created after the update. Users worked through restarting the spooler, clearing stalled jobs, removing and re-adding the printer, and rebuilding the driver/port association. The test page showed that the printer could still respond, so the fix stayed on Windows update aftermath, spooler state, and printer registration.

Problem: Print job leaves the queue but nothing prints

What users observed: A user with an HP Deskjet F380 connected by USB reported that web pages and Word documents entered the print queue, the printer seemed to prepare itself, and then the job left the queue as if completed, but nothing printed. A Windows test page printed successfully from printer properties. The same printer printed normally on another computer.

What was tried: Users uninstalled and reinstalled printer drivers, tried printing directly to the printer, restarted the spooler, cleared files from the spooler folder, ran SFC, cold-rebooted the printer and computer, and compared the same printer on another computer.

How this played out: The strongest repair path came from printer-port cleanup. In a similar disappearing-job case, the printer had an extra local port. The user temporarily changed the printer to another port, deleted the unnecessary USB/local port, applied the change, rebooted, and printed again. That made the job stop disappearing into a bad port path and restored normal output.

Problem: Printer has two configured ports and jobs vanish without printing

What users observed: A similar case described print jobs that vanished from the print list while the printer itself remained functional. The failure appeared across more than five desktops, suggesting a local print-port configuration problem rather than one dead printer.

What was tried: Users inspected printer ports and found two configured ports for one printer.

How this played out: The fix was to remove the duplicate or wrong local port. The printer was temporarily moved to another port so the stale USB/local port could be deleted, then the settings were applied and the machine was rebooted. After that, print jobs stopped vanishing and returned to the correct output path.

Problem: Printer only prints test page but not PDF files

What users observed: A Canon LBP631Cdw user could print a test page but could not print a PDF. The failure was narrowed to PDF printing rather than every possible print path.

What was tried: Users checked the PDF printing program, the selected printer inside that program, and whether the printer appeared more than once in the printer selection list.

How this played out: The useful fix path was inside the PDF program rather than the printer hardware. Users checked whether the PDF application was sending the document to the correct printer entry, especially when the same printer appeared more than once. Selecting the active printer connection inside the app resolved the likely mismatch between the working test-page path and the failed PDF path.

Problem: Canon MG3620 prints test page but nothing from PDF, Word, or websites

What users observed: A Canon MG3620 user reported that the installed printer could print a test page from settings, but would not print from any program, including PDF, Word, or websites.

What was tried: Users were asked to run a nozzle check so the printed pattern could be compared with a sample. The case stayed between Canon printer issues, application printing, and ink/nozzle output.

How this played out: The repair path moved in two directions at once: confirm ink output with a nozzle check, then confirm that applications were sending jobs to the correct printer entry. When every normal application failed but the test page printed, users treated the issue as either an application/driver route problem or a printhead/ink-output mismatch exposed by the nozzle pattern.

Problem: Canon TR7520 test page prints, but normal output is blank or very light

What users observed: A Canon TR7520 user reported that ink levels looked fine and the test page printed properly, but anything else printed blank or very light. Even black-and-white printing came out streaked.

What was tried: Users checked ink levels, printed a test page, changed output to black and white, and were asked to print a nozzle check for comparison.

How this played out: The useful repair path moved toward ink delivery rather than Windows alone. Users compared the nozzle check against document output, ran cleaning cycles, reseated cartridges, and checked whether the issue affected black only or all colors. When the test page and normal output did not match, the fix centered on cartridge seating, printhead cleaning, and nozzle recovery.

Problem: Canon TR8520 nozzle check prints black but applications do not print black text

What users observed: A Canon PIXMA TR8520 user reported that the nozzle-check test page printed black correctly, but black text from Word, PDF, and Excel did not print. A blue ink signature printed from a PDF, and blue text printed from Word, but black text did not print. The user tested multiple documents and later another user reported the same behavior across three computers and two Canon black cartridges.

What was tried: Users ran nozzle checks, compared black output on the test pattern with black output from applications, tried PDF and Word files, changed Word text color to blue, replaced black cartridges, and tested several computers.

How this played out: The working path was to isolate black text from general printing. Users confirmed that color output worked, then focused on the black cartridge and black-text path. In one reported result, replacing the 280 XXL black cartridge restored black application text after deep cleaning had not worked. In other similar cases, users continued through cartridge replacement, printhead cleaning, and printhead/ink delivery checks.

Problem: Canon MX922 test page is good but documents do not print in black

What users observed: A Canon PIXMA MX922 case involved a good test page but documents not printing correctly in black. The visible record later stated that if the issue continued even with Canon genuine inks, the printer might need replacement.

What was tried: Users compared the test page with document output and discussed ink type and cartridge behavior.

How this played out: The repair direction was cartridge and printhead validation. Users compared output with genuine cartridges, ran cleaning cycles, reseated the black cartridge, and treated continued failure as a printhead or printer-side ink delivery issue rather than only a Windows document-printing issue.

Problem: Epson product check page prints but normal computer jobs do not

What users observed: Epson printer records separate a product check from normal computer printing. If the product check or test page prints but normal jobs do not, the issue is treated as software, default-printer, port, queue, or driver state rather than a completely dead printer.

What was tried: Users checked that the product software was installed correctly, confirmed the product was the default printer, matched the printer port to the connection port, cleared stalled print jobs, and checked that the queue was not paused.

How this played out: The product check shifted the fix toward the computer-side print setup. Users corrected the default printer, matched the port to the real connection, cleared stalled jobs, checked pause/offline state, and reinstalled the driver if the software path stayed broken. The printer’s internal output confirmed that the device could print when the computer route was correct.

Problem: Epson test page prints but large images do not print

What users observed: Epson records note that if a test page prints but a large image does not, the computer may not have enough memory for that print job.

What was tried: Users reduced image resolution or checked whether the computer met the requirements for the print job.

How this played out: The repair path was to reduce job complexity. Users lowered image resolution, printed from another application, simplified the document, or tried a less memory-heavy output path. Since the test page printed, the issue stayed with the size or complexity of the job rather than the printer being unable to print at all.

Problem: Epson printer has many queued jobs and stops printing documents

What users observed: Epson records note that Windows may not print when a large number of print jobs are sent. This can leave the printer looking responsive during tests but unreliable during normal printing.

What was tried: Users selected Print directly to the printer on the Advanced tab in printer properties, updated product software, and used driver reinstall if the problem persisted.

How this played out: The useful fix was queue cleanup and spooler bypass. Users cleared stalled jobs, selected Print directly to the printer, updated the Epson software, and rebuilt the driver if the queue kept blocking normal documents. This overlapped with print spooler not working, but the working test page kept the focus on Windows job handling.

Problem: Printer sounds like it is printing but the page comes out blank

What users observed: Epson records separate “printer sounds like it is trying to print” from computer communication failure. In that condition, the printer moves as if output is happening, but the page is blank or not properly printed.

What was tried: Users ran the head cleaning utility and replaced ink cartridges if cleaning did not restore output.

How this played out: The fix moved to ink and nozzle recovery. Users ran head cleaning, replaced weak or empty cartridges, reseated ink, and checked the nozzle pattern. Because the printer physically moved paper and acted like it was printing, the issue was treated as ink delivery or printhead output rather than a missing computer connection.

Problem: Printer prints test page but one application sends jobs to the wrong printer entry

What users observed: In the Canon PDF case, the test page printed, but PDF output did not. The recorded explanation focused on the printer selected inside the PDF program, especially where the printer appeared more than once or another connection was selected.

What was tried: Users checked the printer selection window inside the PDF printing program and tested printing the PDF from another program.

How this played out: The fix was to select the correct printer entry inside the application. Users checked for duplicate Canon entries, stale ports, and wrong connection types. When the application was pointed back to the same printer entry that produced the test page, the print route matched again.

Problem: Printer test page prints but normal document jobs show no queue activity

What users observed: In the HP ENVY 4511 case, the user could print a test page and HP Welcome page, but normal document printing did not leave waiting jobs in the queue. HP Smart opened and hung instead.

What was tried: Users reinstalled HP Smart, reinstalled the printer, and reconnected wireless from the printer panel.

How this played out: The working fix was to rebuild the printer’s network path from the printer itself. After the router was selected and the Wi-Fi password was entered on the printer panel, normal jobs started traveling through the correct route instead of disappearing before they reached the queue.

Problem: Printer only prints test pages after a new computer or new setup

What users observed: Several cases began after a new computer, computer upgrade, Windows update, or reinstallation. The printer itself could still print diagnostics, but the new system’s normal document path failed.

What was tried: Users reinstalled printers, reinstalled apps, compared old and new computers, checked queues, restarted spoolers, and tested the same printer on another computer.

How this played out: The fix was to rebuild the new computer’s print path from the ground up. Users checked default printer selection, driver package, port, queue, wireless registration, and application printer choice. The printer working on another computer or through a test page kept the focus on the new setup rather than the printer hardware.