Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| USB printer never appears | Test cable, direct port, printer power and USB detection |
| Wireless printer is not found | Put PC and printer on the same usable network |
| Printer appears offline | Check its address, connection, queue and default selection |
| Printer vanished after a driver change | Remove stale package and install the current supported one |
Diagnose printer not detected before replacing drivers
Determine whether Windows cannot discover the printer, installs it offline, or lists it with an error. These require different fixes across discovery, queue, port, and driver layers.
Check printer power, cable/network link, and whether the printer itself reports Ready. For USB printers, test another direct port; for network printers, verify the PC can reach the printer's address.
Use the symptom evidence to select the correct layer. “USB printer never appears” points toward test cable, direct port, printer power and usb detection, while “Wireless printer is not found” suggests put pc and printer on the same usable network. Also note what changed immediately before the failure: a Windows update, driver package, new dock, BIOS update, sleep or hibernation cycle, physical impact, liquid exposure or installation of device-management software.
Use Windows Update or the printer manufacturer's exact package for that model. Avoid universal drivers until the device is at least detected and basic printing is understood.
Restart Windows and the printer, clear temporary offline states, disconnect duplicate USB/network paths, and retry discovery before reinstalling the print stack.
The remaining symptoms also narrow the search: “Printer appears offline” means you should check its address, connection, queue and default selection, while “Printer vanished after a driver change” means you should remove stale package and install the current supported one. After each repair, verify the original function rather than accepting a successful installer message. A package can finish correctly while Windows still loads another driver or the hardware remains unavailable.
Prove the printer connection first
Print a network or status page from the printer when available. For Wi-Fi or Ethernet, confirm that the PC and printer can reach the same local network and that guest-network isolation is not blocking discovery. For USB, use a known-good data cable and connect directly.
Open Settings > Bluetooth & devices > Printers & scanners and choose Add device. If automatic discovery fails, use the manual option with the printer's hostname, IP address or documented port method. Avoid adding several duplicate queues during testing.
1Clear temporary Windows faults
- Run the Printer troubleshooter in Get Help.
- Restart the printer and PC.
- Restart Print Spooler in Services if discovery or queues remain stuck.
2Reinstall one clean queue
- Remove the failed printer from Printers & scanners.
- Install Windows and optional printer updates.
- Use the latest package from the printer manufacturer.
Repair network, USB and spooler layers separately
A network printer with a changed DHCP address may leave Windows pointing to its old address. Compare the printer's current network page with the configured port. Reserve an address in the router or use the manufacturer's documented discovery method when the environment supports it.
If no printer can add or every queue fails, the Print Spooler or Windows printing components deserve attention. If only one model fails, focus on that queue, port and driver. Repeatedly clearing the spool folder is unnecessary when the real issue is network reachability.
Handle old and multifunction printer packages
Older installation discs often contain outdated software. Prefer Windows Update or the manufacturer's current download. A basic class driver may print but omit scanning, ink tools, finishing or duplex features; install the supported full package only when those functions are needed.
Test printing and scanning separately because multifunction devices can expose different network services and drivers. A printer that prints but will not scan is not truly undetected; repair the scanner component, app permissions or vendor utility instead.
Verify the repair before making more changes
Restart Windows—not only the affected app—and confirm that the printer remains online and completes a Windows test page plus any required scan test. Check Device Manager again: the device should remain present without a warning icon, and Device status should say it is working properly.
Print a Windows test page, restart the PC and printer, then print again. Confirm the printer remains installed and online.
Technical order checked against Microsoft's current printer detection guidance. Device-specific menus and driver availability vary by manufacturer.
Frequently asked questions
Why can my phone find the printer but Windows cannot?
The PC may be on another network, discovery may be blocked or Windows may need the correct queue and driver.
Should I restart the Print Spooler?
Yes for stuck discovery or queues, but it will not fix a disconnected USB cable or unreachable network printer.
Why does a basic driver print but not scan?
Printing and scanning can use separate components. Install the supported full package or scanner app.