Printers & Peripherals

"I can't print" is the single most frequent ticket in IT support. It is also one of the easiest to score interview points on, because the answer is a clean process.

The process, not the guess

✖Do not start by reinstalling the printer

Interviewers are testing whether you isolate variables. A good answer names the order of checks. A bad answer starts with reinstall.

1. Ask one clarifying question — "Does anything print, or just this document / this PC?" This splits a printer fault from an application fault.
2. Check the physical layer — paper loaded, no jam lights, correct toner, printer powered, cable seated.
3. Check the queue — PrintManagement or the Windows queue. Errors there usually mean the printer itself is the problem.
4. Check the driver — is it a v3 or v4 driver? Correct model? Bit level?
5. Check the network path — Test-NetConnection <printer-ip> -Port 9100 (JetDirect) or 631 (IPP).
6. Check the client side — default printer, "use printer offline" ticked, the print spooler service.
7. Only then reinstall the driver or reset the queue.

# The queue, with error codes
Get-PrintJob -PrinterName "HP-Lobby" | Select-Object ID, DocumentName, JobStatus

# Is the spooler even running?
Get-Service Spooler

# Is the printer reachable and what does it report?
Get-Printer | Select-Object Name, PortName, PrinterStatus, DriverName
Get-PrinterPort | Select-Object Name, PrinterHostAddress, PortNumber

PortNumber	Protocol
9100	Raw JetDirect / TCP — the classic one to test
631	IPP
515	LPD
161	SNMP

The error codes that actually mean something

Code / message	Meaning	Fix
0x00000470	The print spooler could not reach the printer	Network or the printer is off
0x0000010b	Invalid printer name	Re-add with the correct IP/FQDN
Stuck "Deleting"	Spooler stopped	Restart the spooler service
"Paper jam" persists	Sensor, not paper	Open the tray, check the sensor flag
Blank pages	Toner, drum, or a driver rendering issue	Print a test page from the printer itself
Garbled text	Wrong driver or bit depth	Install the correct model driver

★Separate app from printer

If a test page prints from Notepad but not from Excel, the printer and network are fine and you have an application problem — a bad print range, a stuck print dialog, or an Excel template issue. Restarting the spooler will not fix it.

Print server

Get-PrintServer | Select-Object Name
Get-Printer -Server print01.corp.local
Add-Printer -ConnectionName "\\print01.corp.local\HP-Lobby" `
  -PrinterHostAddress "192.168.10.50"

Concept	Detail
Shared printer	A printer object on a print server, shared to users
Deployed printer	A client-side object that points at the share and installs drivers
Group Policy deployment	"Deploy printers" in Computer Configuration
Logon script mapping	Legacy; Group Policy is preferred
3rd-party drivers	Universal (v4) vs model-specific (v3)

ℹv3 vs v4 drivers

v4 drivers are isolated from the spooler and are far more stable. v3 drivers run inside it, so a bad v3 driver can hang printing for everyone on that server. That is a real reason to prefer universal drivers.

Scanners

Get-PnpDevice | Where-Object {$_.FriendlyName -like "*scan*"}

Most scanners are "WIA" devices:

# Check the WIA service
Get-Service WIA

# Test acquisition
wiacmd /?

USB peripherals and docking stations

Get-PnpDevice -PresentOnly | Where-Object {$_.Status -ne 'OK'}
Get-PnpDevice -Class USB | Select-Object FriendlyName, Status

Fault	Check
Device not detected	Different port, especially a USB-C port that is data-only
Recognised but no driver	Get-PnpDevice for an unknown device
Headset mic not working	Wrong default input device in Windows sound settings
Docking station drops monitors	DisplayLink driver, or bandwidth limits on a single cable
Intermittent USB	Hub power, not the device. Move to a port on the machine.

⚠USB-C is not automatically DisplayPort

Many USB-C ports are charge-only or USB 2.0 data only. If a dock's monitors drop when you plug in a second device, you are hitting the port's bandwidth limit, not the dock.

Interview scenario

'I can't print' — how do you answer?

"First I'd clarify scope: does anything print, and does it print from other machines? If nothing prints anywhere, the problem is the printer or its network. If it prints from another PC, the problem is this PC's driver or queue.

I'd check the physical state first — paper, toner, error lights — then the queue in PrintManagement for a specific error, then verify I can reach the printer on port 9100 with Test-NetConnection, then confirm the spooler service is running and that the client isn't set to 'use printer offline'. Only after isolating those would I reinstall the driver or clear the queue."

Next

Troubleshooting Methodology.