Windows printer and print spooler troubleshooting for MSPs

1. Scope it before touching anything

One printer or all of them? One person or everyone? That answer decides whether the fault is a printer, a queue, a driver, or the print server.

Get-Service Spooler
Get-Printer | Select-Object Name, PrinterStatus, PortName, DriverName
Get-PrintJob -PrinterName 'Front Office'

A stopped spooler affects every printer on that machine. A single printer in an error state with a healthy spooler points at the port, the driver or the device.

2. Can the machine reach the printer?

Most network printers listen on a raw port, usually 9100. Test it.

Test-NetConnection 192.0.2.50 -Port 9100

If that fails, nothing on the Windows side will help: the printer is off, on another network, or its address changed. Check Get-PrinterPort for the address the printer is configured with and compare it with the one on the device.

3. Recovering a stuck queue

A job that will not clear can block everything behind it. The standard recovery is to stop the spooler, clear the spool folder and start it again.

This deletes every queued job for every user on that machine. Warn the user, and get approval before running it. It is the single step in this guide that quietly loses someone's documents.

Stop-Service Spooler -Force
Remove-Item "$env:SystemRoot\System32\spool\PRINTERS\*" -Force
Start-Service Spooler

The -Force on the stop also stops services that depend on the spooler, such as the fax service. They do not all come back on their own, so check that anything which should be running is.

4. The spooler keeps crashing

If it stops again within minutes, something it loads is faulting - almost always a third-party driver or port monitor. The Application log names the module.

Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='Application Error'; StartTime=(Get-Date).AddDays(-2)} |
  Where-Object { $_.Message -match 'spoolsv' } |
  Select-Object TimeCreated, Message -First 5

Remove the printers that use the suspect driver, then the driver, then reinstall a current one from the manufacturer. Reinstalling the same driver over itself rarely helps.

5. Errors that are about permissions, not the spooler

Connecting to a printer shared from a print server can fail with codes such as 0x0000011b, 0x00000709 or 0x00000bcb. These became common after Microsoft tightened how Windows authenticates RPC print connections and restricted driver installation from shared printers, and they are fixed on the server or by policy, not by restarting the client's spooler. Check Microsoft's current guidance for the exact update and the policy that applies to your environment before changing anything.

The print service logs (Microsoft-Windows-PrintService/Admin, and /Operational once enabled) record what failed. The Operational log is off by default; turning it on is a change, so note that you did.

6. Verify with a real page

Get-CimInstance Win32_Printer -Filter "Name='Front Office'" | Invoke-CimMethod -MethodName PrintTestPage

Then confirm the queue is empty and that the user can print from the application they use. A test page printing while their application still fails is a driver or default-settings problem, and worth saying so.

When to stop and escalate: a driver the vendor must supply, a fault on the print server, or a permissions policy change that affects more than one machine. RemediateDesk follows the same order and treats clearing a queue as a change that needs approval; its Windows examples show what it gathers.

Step-by-step in RemediateDesk

A queue recovery is a change, so it waits on an approval card before it runs. Read how approvals work for the choices on that card, and the chat page for where it appears.