Printers generate more tickets per device than anything else in the office. Most of them are the same three problems wearing different clothes: a stuck spooler, a bad driver, or the PC talking to the wrong address.
This is the order we work through them. Start at the PC, move to the driver and port, then to the print server or the printer itself. Do not reinstall the printer as step one. It hides the cause and it will be back.
Find where the job is stuck
Open Settings > Bluetooth & devices > Printers & scanners, pick the printer and open the print queue. Three things tell you a lot. If the job sits at Spooling or Printing with an Error status, the spooler on the PC is the problem. If the queue is empty and nothing came out, the job went somewhere else: check the default printer, because Windows will happily send to a PDF printer or a printer at the old office.
If the printer shows Offline, Windows could not reach it the last time it tried. That points at the port or the network, not the spooler. Turn off the Use Printer Offline option in the queue's Printer menu, then test again.
Restart the spooler and clear the queue
A job that is corrupt or was cancelled halfway through can block everything behind it, and the Cancel button in the queue does not always work. The reliable fix is to stop the spooler service, delete the spool files on disk, and start it again. Run this from an elevated command prompt. It clears the queue for every printer on that PC, so warn the user.
net stop spooler
del /Q /F %systemroot%\System32\spool\PRINTERS\*
net start spoolerDriver and port problems
Open the printer's Properties and look at the Ports tab. A WSD port is auto-discovered and breaks when the printer's address changes or the discovery service hiccups. A Standard TCP/IP port pointing at a fixed IP or a DNS name is far more reliable. If the printer got a new address from DHCP, that is your cause: reserve the address on the DHCP server and fix the port.
On the Advanced tab note the driver name. Type 4 (class) drivers are simple but lose features like finishing options. Vendor Type 3 drivers do more but are the ones that crash the spooler, usually visible in the System log as a spooler crash every time a specific user prints. Since the PrintNightmare changes, installing a driver on a client needs admin rights unless Point and Print is configured through Group Policy, so a "driver is unavailable" message often just means the user cannot install it.
- Ping the printer's address from the PC. No reply means network or printer, not Windows.
- Open the printer's web page in a browser. If that loads, the printer is up and the problem is between Windows and it.
- Print a test page from Properties > General. If the test page works but the app does not, the problem is the application or the document.
Print server and network issues
When printers are shared from a print server, one server problem becomes fifty tickets at once. On the server, check the queue for the printer, restart the spooler there, and look at the event logs under Applications and Services Logs > Microsoft-Windows-PrintService. The Admin log records failed jobs and driver failures; the Operational log, if enabled, records every job.
Also check the basics on the client: can it resolve and reach the server by name, and is the user's connection to the shared printer still authenticated? A stale credential or a Kerberos problem shows as Access denied when adding or printing to the shared printer. On segmented networks, make sure the printer VLAN allows TCP 9100 (raw), 631 (IPP) and 515 (LPD) from the client VLAN, and that SNMP is not blocked if the port monitor is set to use it, because a blocked SNMP query makes a working printer show Offline.
Get-Printer -ComputerName printsrv01 | Select-Object Name, DriverName, PortName, PrinterStatusReduce printer tickets for good
A few standards remove most of the recurring pain. Give every printer a DHCP reservation or a static address and a DNS name. Use one driver per model across the fleet, and prefer a universal driver where the vendor has a good one. Name printers by location, not by model number, so users pick the right one. Deploy printers by Group Policy Preferences or Intune based on the user's site rather than letting people add whatever they find.
If you are fully in Microsoft 365, Universal Print takes the print server and driver installs off the table entirely. It is not free and it needs a connector or compatible printers, but it ends the spooler tickets. If you want help deciding whether that fits your fleet, RackLedge can look at your printers and say plainly whether it is worth it.
Frequently asked questions
The printer prints a test page but not from one application. Why?
The application is either using a different default printer, printing to a paper size the tray does not have, or sending a document the driver cannot render. Print to PDF first to confirm the document is fine, then check the app's own print settings.
Why does the printer show Offline when it is clearly on?
Windows marks a printer Offline when the port cannot reach it or an SNMP status query fails. Check the port address, untick SNMP Status Enabled on the port's Configure Port dialog, and confirm the printer did not change IP address.
Takeaway
Most printer tickets are a stuck spooler, a bad driver or a printer that moved address. Work from the PC outward, clear the spooler properly, fix the port rather than reinstalling, and check the print server logs when many people are affected at once. Then set standards for addresses, drivers and naming so the same ticket stops coming back.