Printer Shows Connected But Won't Print – Real Fix
Your printer says it's connected, but nothing happens when you hit print. Here's why and how to fix it in minutes.
You hit print, the little popup shows your printer is connected and ready, but the paper tray stays empty. The printer screen says "Online" or "Ready." You've checked the cables, restarted everything twice, and still nothing comes out. This happens most often after a Windows update, a power outage that interrupted a print job, or when you've switched networks and the printer didn't reconnect properly. The machine looks fine, but it's lying to you.
What's actually happening
The printer is physically connected to the computer or network, so Windows says it's there. But the print job itself is stuck in a queue that Windows treats as broken. The spooler service—the thing that sends data to the printer—has a corrupted job in line. Every new job you send just piles up behind the bad one. The printer never sees the new jobs because the spooler is holding them hostage. This is not a hardware problem. It's a software lock.
The real fix – clear the stuck spooler
Skip the generic "run the printer troubleshooter" advice. It rarely works. Here's the direct fix.
- Open Services – Press Windows + R, type
services.msc, hit Enter. Find Print Spooler in the list. Right-click it and select Stop. Leave that window open. - Delete the stuck print jobs – Open File Explorer. Paste this into the address bar:
C:\Windows\System32\spool\PRINTERS. Delete everything inside that folder. It's safe—these are just queued print jobs. Windows will recreate the folder when needed. - Restart the spooler – Go back to the Services window. Right-click Print Spooler again and select Start. Now close the window.
- Try printing again – Send a test page. If it works, you're done. If not, move to the next step.
If the queue is empty but it still won't print
The spooler fix works 80% of the time. When it doesn't, the issue is the printer driver got corrupted. Here's how to reinstall it clean.
- Remove the printer from Windows – Go to Settings > Bluetooth & devices > Printers & scanners. Click your printer, then Remove device. Confirm the removal.
- Delete the old driver – Open Device Manager (right-click Start). Expand Print queues. Right-click your printer and select Uninstall device. Check the box that says Delete the driver software for this device if it appears. This step kills the cached bad driver.
- Re-add the printer – Back in Printers & scanners, click Add device. Windows will scan for printers. Select yours. If it doesn't find it, click The printer that I want isn't listed and choose Add a local printer or network printer with manual settings. Use the correct port (usually USB001 for USB printers or WSD for network ones).
- Install the driver fresh – Windows will try to find a driver. Let it. If it fails, download the latest driver from your printer manufacturer's website (HP, Canon, Epson, Brother) and run the installer. Do not use the generic Microsoft driver unless you have no choice—it strips features and sometimes causes the same problem.
What to check if it still fails
Three things left to check.
- IP address conflict – If your printer is on Wi-Fi, make sure it has a static IP. Print a network configuration page from the printer's menu. Open a command prompt on your PC and type
ping [printer IP]. If you get replies but printing still fails, the printer might have the wrong subnet mask or gateway. Set it manually to match your router. - USB cable – For a wired printer, try a different USB cable. I've seen cables that pass power but drop data. Use a cable shorter than 3 meters (10 feet) for reliable USB 2.0 communication.
- Windows update issue – Some cumulative updates break printer drivers. Check Settings > Windows Update > Update history. If the problem started after a specific update, uninstall it (look for Uninstall updates at the top of that page). Reboot and test.
That covers the real reasons your printer shows connected but won't print. Most people fix it in step 3. The rest need a clean driver. The IP conflict is rare but nasty when it happens. Start with the spooler—it's fast and harmless to try.
Was this solution helpful?