HP Printer Prints Test Pages but Nothing from My Computer: Fix

It is one of the most confusing printer faults: your HP printer happily prints its internal test page, a configuration report, even a cleaning page — but your document from Word, your browser, or your email just vanishes. No error, no jam, nothing comes out. The good news hidden in that symptom is that the printer hardware is almost certainly fine. The problem sits in the chain between your computer and the printer: the queue, the driver, the port, or the app doing the printing. This guide walks that chain in order.

Quick Answer

If an HP printer prints test pages but not your documents, the print hardware works — the fault is on the computer side. Clear the print queue and restart the Print Spooler, check you are printing to the correct printer (not a “Copy 1” or an old offline queue), reinstall the official HP driver, and make sure the printer is using a working TCP/IP or USB port. Also test printing from a different app to rule out a single program.

Why Test Pages Print When Documents Do Not

There are two kinds of test page, and the difference matters:

• Internal test pages printed from the printer’s own buttons or menu never leave the printer. They only prove the print engine, paper path, and ink or toner work.
• The Windows test page from Printer Properties travels from the PC to the printer, so it also proves the cable, network, port, and basic driver path.

If the internal page prints but the Windows test page does not, the connection or port is broken. If the Windows test page prints but your document does not, the driver is mostly fine and the fault is the app, the file, or the queue. Knowing which one you have halves the troubleshooting.

Step 1: Clear the Queue and Restart the Spooler

1. Open the printer queue and cancel every document — one corrupt job at the front blocks everything behind it.
2. Press Windows key + R, type services.msc, and find Print Spooler.
3. Restart the service. If jobs still show as stuck, stop the service, delete the files in C:\Windows\System32\spool\PRINTERS, and start it again.
4. Try the Windows test page from Printer Properties, Advanced or General tab.

Step 2: Check You Are Printing to the Right Printer

Windows collects duplicate printer entries over time — the same printer on a WSD port, a TCP/IP port, and an old USB entry, sometimes marked “Copy 1”. Apps remember the last printer used, which may be a dead entry. In your app’s print dialog, look at the exact printer name. Then in Windows Settings set the correct entry as default, and turn off “Let Windows manage my default printer” so it stops switching. Deleting the unused duplicate entries removes the trap permanently. If your correct entry shows as offline, fix that first with our guide to a printer that keeps showing offline.

Step 3: Reinstall the Driver Cleanly

1. Remove the printer from Windows Settings.
2. Open Print Server Properties (from Printers & scanners, or run printui /s), go to Drivers, and remove the HP driver package for your model.
3. Restart the PC.
4. Download the full-feature driver for your exact model from HP’s official driver downloads and install it, connecting the printer only when the installer asks (for USB) or letting it find the printer on the network.
5. Print a document from Notepad first — it is the simplest possible test — then from the app that failed.

Step 4: Test by App and by File

If Notepad prints but Word, a PDF reader, or your browser does not, the problem is local to that program:

• PDFs: try “Print as Image” in the advanced print options — this flattens complex PDFs that choke printer drivers.
• Browsers: use the system print dialog (Ctrl+Shift+P) instead of the built-in preview, or save the page as PDF and print that.
• Office apps: check the print range and that a real printer, not “Microsoft Print to PDF”, is selected; repair the Office install if prints fail from every document.
• Every app fails for one file only: the file is corrupt. Copy its content into a fresh document and print that.

Step 5: Check the Port

In Printer Properties, open the Ports tab. For a network printer, the port should be a Standard TCP/IP Port with the printer’s current IP address. If the printer’s address changed and the port still points to the old one, jobs disappear silently. For USB, the port should be a USB virtual printer port — if several exist, the job may be going to the wrong one; the clean driver reinstall in Step 3 fixes this too.

Common Mistakes to Avoid

• Assuming the printer is broken — a printer that prints internal pages has a working engine; look at the PC side.
• Cleaning print heads or changing cartridges for this fault — output quality is not the problem, so don’t waste ink.
• Reinstalling over the top of a corrupt driver — remove the old driver package first or the fault often survives.
• Ignoring the queue — a single stuck job silently blocks everything and mimics a dead printer.

One More Test: Print from Another User Account or Device

If you have worked through the queue, driver, and port and documents still refuse to print, borrow another angle. Log into a different user account on the same PC and print from there. If the second account prints fine, your original profile has a corrupt printer configuration or app setting, and you can rebuild just that profile’s printer setup instead of the whole machine’s. Similarly, if a second computer prints to the same printer happily, compare the two machines: driver version, port type, and how the printer was added. The difference between a working machine and a broken one is almost always visible in that comparison, and it is faster than continuing to guess. In offices, this is also how you discover that one PC is still using a driver from three models ago. Whatever the outcome, write down what finally worked — this fault has a habit of returning after updates, and future-you will be glad of the note.

One small setting deserves a final mention: some HP drivers include a booklet or manual-duplex default inherited from a previous job that can make jobs appear to vanish while the printer waits for manual sheet handling. If pages seem to disappear without error, check the queue for a job paused awaiting manual duplexing before assuming the worst.

Conclusion

When test pages print but documents do not, work the chain between computer and printer: clear the queue and spooler, print to the correct printer entry, reinstall the official driver cleanly, and verify the port. Then narrow down by app and file. Almost every case is solved by one of those steps, without touching the printer hardware at all.

Frequently Asked Questions

The Windows test page prints but my PDF does not. Why?

The driver path works, so the PDF itself is the problem — complex layers, fonts, or transparency. Use Print as Image, or re-save the PDF from another app.

Jobs appear in the queue, say “printing”, then vanish. What does that mean?

The spooler believes the job was sent successfully but the printer never received it — typically a wrong port or a stale WSD connection. Reinstall using a TCP/IP port with the printer’s real IP.

Can antivirus software block printing?

Occasionally, security software blocks the spooler from reaching a network printer. Test by printing with real-time protection briefly paused, and whitelist the spooler if that proves to be it.

My printer prints from my phone but not my PC. Same cause?

Yes — the printer and network are proven good by the phone, so concentrate fully on the PC’s driver, queue, and port.

Should I use HP Smart or the full driver?

For stubborn problems, the full-feature driver from HP’s site is the more reliable fix. HP Smart is fine for a healthy setup but its simplified driver can be the weak link.