Interactive Troubleshooter

Published: Sep 26, 2026

Printer Not Working - Is It Network, Driver, or Spooler?

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Isolate and repair Windows printing subsystems across spooler service crashes, corrupted print driver isolates, dynamic IP assignment shifts, and physical connectivity drops. This interactive troubleshooting tree systematically identifies root causes using PowerShell commands, registry fixes, and Print Management diagnostics.

Full Diagnostic Tree & Step-by-Step Overview

What is the primary symptom or error behavior shown by your printer or Windows printing system?

Print Spooler service keeps stopping, crashing, or throwing RPC errors (e.g., 'The local print spooler service is not running').
Printer is listed as 'Offline', 'Not Connected', or fails to communicate over the network/USB.
Print jobs get stuck in the queue with 'Printing', 'Deleting', or 'Error - Sent to Printer' status.
Printer prints garbage characters, blank pages, prints extremely slowly, or fails with driver corruption errors.

What specific error or behavior occurs when the Print Spooler service fails?

Spooler service crashes repeatedly every time a print job is submitted or a printer is added.
Spooler service fails to start entirely with Error 1068 or RPC Server Unavailable.
Spooler crashes specifically due to point-and-print restrictions or Windows update security patches (e.g., KB5005565 / PrintNightmare hardening).
Spooler crashes due to corrupted third-party print monitor DLLs or third-party PDF virtual printers.

Print Spooler Service Crash Triggered by Corrupt Driver / DLL

Solution:

Root Cause: Kernel/User-Mode Memory Exception in Spooler Process (spoolsv.exe)

When spoolsv.exe crashes upon receiving a print request, a corrupted third-party printer driver DLL or invalid print processor mode is causing an unhandled memory access violation within the spooler process address space.

# Diagnostic Verification:

1. Open Event Viewer (eventvwr.msc).
2. Navigate to Windows Logs > Application.
3. Search for Event ID 1000 (Application Error) where Faulting application name is spoolsv.exe and Faulting module name points to a driver file (e.g., hpmsl150.dll, unidrv.dll, or epson12.dll).

# Step-by-Step Fix:

1. Stop the Print Spooler Service via PowerShell:

powershell
   Stop-Service -Name "Spooler" -Force

2. Purge Pending Spooler Cache Files:

powershell
   Remove-Item -Path "$env:SystemRoot\System32\spool\PRINTERS\*" -Force -Recurse

3. Isolate Corrupted Drivers in Registry:

Press Win + R, type regedit, press Enter.

Navigate to: HKLM\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3 (or Version-4).

Locate the subkey for the faulting printer driver and append .old to the key name to force Windows to bypass it.

4. Restart Spooler Service and Enable Driver Isolation:

powershell
   Start-Service -Name "Spooler"

Open Print Management (printmanagement.msc).

Under Custom Filters > All Drivers, right-click the problematic driver > Set Driver Isolation > Isolated.

# Prevention & Long-Term Monitoring:

Always configure third-party v3 drivers in Isolated mode so a driver crash does not terminate the entire spoolsv.exe service.

Spooler Fails to Start (Error 1068 / RPC Server Unavailable)

Solution:

Root Cause: Dependency Service Failure or Registry Security Permission Corruption

The Print Spooler service (spoolsv.exe) depends on the Remote Procedure Call (RPC) (RpcSs) and HTTP Service (HTTP). If a dependency service is disabled or permissions on C:\Windows\System32\spool are corrupted, the service fails with Error 1068 or Error 1058.

# Diagnostic Verification:

1. Open Command Prompt as Administrator.
2. Query Spooler configuration state:

cmd
   sc qc spooler

3. Review the DEPENDENCIES output to ensure RPCSS and HTTP services are active.

# Step-by-Step Fix:

1. Verify and Start Service Dependencies:

powershell
   Set-Service -Name "RpcSs" -StartupType Automatic
   Set-Service -Name "HTTP" -StartupType Automatic
   Start-Service -Name "RpcSs"
   Start-Service -Name "HTTP"

2. Restore File System Permissions on Spool Directory:

cmd
   icacls "C:\Windows\System32\spool\PRINTERS" /grant "NT AUTHORITY\SYSTEM":(OI)(CI)F /T
   icacls "C:\Windows\System32\spool\PRINTERS" /grant "Administrators":(OI)(CI)F /T

3. Reset Spooler Registry Permissions and Startup Type:

powershell
   Set-Service -Name "Spooler" -StartupType Automatic
   Start-Service -Name "Spooler"

# Prevention & Long-Term Monitoring:

Avoid modifying system file permissions or disabling core Windows services via aggressive third-party optimization scripts.

Point-and-Print Restriction / Security Patch Driver Block

Solution:

Root Cause: PrintNightmare Hardening (Restricted Point and Print Driver Installation)

Following security updates for vulnerabilities like PrintNightmare (CVE-2021-34527), Windows restricts non-administrative users from installing or updating print drivers via shared network printers. Attempting to connect yields errors like 0x0000011b or 0x0000007c.

# Diagnostic Verification:

Attempting to connect to a shared network printer results in error: Windows cannot connect to the printer. Operation failed with error 0x0000011b.

# Step-by-Step Fix:

1. Configure Point and Print Policy via Group Policy:

Press Win + R, type gpedit.msc, press Enter.

Navigate to: Computer Configuration > Administrative Templates > Printers.

Open Point and Print Restrictions.

Set to Enabled.

Uncheck Users can only point and print to these servers.

Set When installing drivers for a new connection = Do not show warning or elevation prompt.

2. Adjust RPC Connection Authentication Level via Registry (Client/Server):

Open PowerShell (Admin) and set RpcAuthnLevelExemption (if necessary for legacy print servers):

cmd
     reg add "HKLM\System\CurrentControlSet\Control\Print" /v RpcAuthnLevelExemption /t REG_DWORD /d 1 /f

3. Restart Print Spooler:

powershell
   Restart-Service -Name "Spooler"

# Prevention & Long-Term Monitoring:

Pre-install package-aware v4 print drivers on client machines using deployment tools like Intune or GPO to avoid requiring administrative privilege escalation during printer assignment.

Corrupted Third-Party Print Monitor DLL Crash

Solution:

Root Cause: Invalid Memory Operations in Custom Print Monitor Extensions

Print Monitors run directly inside the spoolsv.exe process to manage specialized communication ports (e.g., third-party PDF creation software, virtual fax monitors, or vendor accounting monitors). A malfunctioning monitor DLL causes global spooler crashes upon startup.

# Diagnostic Verification:

1. Open Event Viewer > System or Application log.
2. Look for Event ID 7031/7032 (Service Control Manager) reporting that the Print Spooler terminated unexpectedly.

# Step-by-Step Fix:

1. Stop Print Spooler:

powershell
   Stop-Service -Name "Spooler" -Force

2. Backup and Clean Print Monitors in Registry:

Press Win + R, type regedit, hit Enter.

Navigate to: HKLM\SYSTEM\CurrentControlSet\Control\Print\Monitors.

Core Windows monitors include: Local Port, LPR Port, Microsoft Shared Fax Monitor, Standard TCP/IP Port, USB Monitor, WSD Port.

Export and delete any third-party keys (e.g., third-party PDF generators or outdated vendor monitors).

3. Restart Print Spooler Service:

powershell
   Start-Service -Name "Spooler"

# Prevention & Long-Term Monitoring:

Use standard TCP/IP ports or WSD ports instead of installing proprietary vendor port monitor suites when configuring network printers.

How is the printer physically or logically connected to the system showing 'Offline'?

Connected via Wi-Fi/Ethernet network, but ICMP ping to printer's IP address fails or times out.
Network printer responds to ping, but Windows reports status as 'Offline' or WSD port drops connection.
Connected directly via USB, but device is listed as Unspecified or 'USB Device Not Recognized'.
Printer changed its IP address unexpectedly due to dynamic DHCP lease expiration.

Network Layer Disconnect / Subnet Routing Failure

Solution:

Root Cause: Physical Layer Failure, VLAN Isolation, or Physical Link Drop

When a network printer fails to respond to ICMP ping requests from the host PC, the printer has either lost its physical link (Wi-Fi disassociation, unplugged Ethernet cable), resides on a different unrouted VLAN, or is powered down into deep sleep mode.

# Diagnostic Verification:

1. Open Command Prompt and attempt to ping the printer's IP address:

cmd
   ping 192.168.1.200

2. If output states Destination host unreachable or Request timed out, the issue exists at Network Layer 1–3.

# Step-by-Step Fix:

1. Verify Physical Link & Print Network Configuration Page:

At the printer's physical control panel, print a Network Configuration Page or Configuration Report.

Confirm the IPv4 address, Subnet Mask, and Gateway match your local network topology.

2. Verify Port Connectivity via PowerShell:

Test raw printing port (9100) or LPR port (515):

powershell
     Test-NetConnection -ComputerName 192.168.1.200 -Port 9100

3. Power Cycle Network Infrastructure and Printer:

Turn printer off, wait 30 seconds, and turn it back on.

If connected over Wi-Fi, ensure the printer is connected to the 2.4 GHz band if it lacks 5 GHz radio support.

# Prevention & Long-Term Monitoring:

Reserve a static IP address on your network router's DHCP table for the printer's MAC address.

WSD (Web Services for Devices) Port Failure -> Convert to Standard TCP/IP

Solution:

Root Cause: WSD Dynamic Port Resolution Failure and Network State Drop

Windows automatically installs many network printers using WSD (Web Services for Devices) ports. WSD relies on multicast discovery protocols. When the printer enters power-saving sleep mode, WSD fails to re-establish the dynamic session, causing Windows to lock the printer status as 'Offline' even while pings succeed.

# Diagnostic Verification:

1. Open Control Panel > Devices and Printers.
2. Right-click printer > Printer Properties > Ports tab.
3. Check the active port type. If it starts with WSD- or displays a GUID instead of an IP address, WSD is in use.

# Step-by-Step Fix:

1. Convert WSD Port to Standard TCP/IP Port:

In Printer Properties > Ports tab, click Add Port....

Select Standard TCP/IP Port, click New Port....

Enter the printer's static IP address (e.g., 192.168.1.200) in the hostname field.

Select Raw protocol and set Port Number to 9100.

Uncheck SNMP Status Enabled if offline status persists (SNMP blocks cause false offline states when firewalls block UDP 161).

2. Disable 'Use Printer Offline' Status in Windows:

Open Print Queue > Click Printer menu > Ensure Use Printer Offline is unchecked.

# Prevention & Long-Term Monitoring:

Always select Standard TCP/IP Port instead of WSD when adding network printers manually.

USB Controller Port Disconnect or Interface Power Management Failure

Solution:

Root Cause: USB Controller Suspension or Faulty High-Speed USB Communication

Direct USB connection failures stem from bad USB cables, physical port failure, or USB Selective Suspend features powering down the controller hub during idle periods, preventing bi-directional status reporting (USBPRINT.SYS).

# Diagnostic Verification:

1. Open Device Manager (devmgmt.msc).
2. Expand Universal Serial Bus controllers and USB Printing Support.
3. Check if an entry shows a yellow exclamation mark or displays Unknown USB Device (Device Descriptor Request Failed).

# Step-by-Step Fix:

1. Disable USB Selective Suspend in Windows Power Plan:

Press Win + R, type powercfg.cpl, press Enter.

Click Change plan settings > Change advanced power settings.

Expand USB settings > USB selective suspend setting > Set to Disabled.

2. Reinstall USB Printing Support Driver:

In Device Manager, right-click USB Printing Support > Uninstall device.

Unplug the USB printer cable, wait 10 seconds, and reconnect it to a USB 2.0/3.0 port directly on the motherboard rear I/O panel.

3. Verify USB Cable Length:

Ensure USB cable length does not exceed 3 meters (10 feet) without an active USB repeater.

# Prevention & Long-Term Monitoring:

Avoid connecting printers through unpowered USB hubs or keyboard passthrough ports.

Dynamic IP Address Drift / DHCP Lease Expiration

Solution:

Root Cause: Port IP Address Mismatch caused by Dynamic DHCP Assignment

If a network printer is configured with a dynamic IP address, the router assigns a new IP address when the DHCP lease expires. The Windows driver continues sending print jobs to the old IP address, resulting in jobs timing out.

# Diagnostic Verification:

1. Print a Network Configuration Page from the printer panel to observe its current IP address (e.g., 192.168.1.150).
2. Open printmanagement.msc > Printers > Right-click printer > Properties > Ports > Configure Port....
3. Compare the Printer Name or IP Address field with the printer's actual current IP.

# Step-by-Step Fix:

1. Assign Static IP on Printer Panel or Embedded Web Server (EWS):

Type the printer's current IP into a web browser to access its Embedded Web Server.

Navigate to Network / TCP/IP Settings.

Change IP Assignment method from Auto / DHCP to Static / Manual.

Enter IP details outside your router's dynamic DHCP pool range.

2. Update Windows Print Port IP Address:

In Printer Properties > Ports > Configure Port..., update the Printer Name or IP Address field to match the new static IP address.

# Prevention & Long-Term Monitoring:

Configure DHCP MAC Reservations on network routers for all network printers to ensure IP address permanence.

What specific queue behavior or file lock condition is keeping print jobs stuck?

Jobs are stuck with status 'Deleting...' or 'Printing...' and cannot be cancelled from the GUI queue.
Print jobs spooling to disk consume gigabytes of storage space and freeze the print queue.
Print queue is blocked due to user permission conflicts or document lock state.
Print queue pauses automatically or displays 'Attention Required' status.

Clearing Locked Spool Files (.SHD / .SPL) via Terminal

Solution:

Root Cause: Windows Spooler File System Lock on Shadow (.SHD) and Spool (.SPL) Files

When a print job fails midway through transmission, Windows retains the .SPL (raw print payload) and .SHD (shadow settings file) files in C:\Windows\System32\spool\PRINTERS. The spooler holds an active file handle on these documents, preventing deletion through the standard GUI queue window.

# Diagnostic Verification:

1. Open C:\Windows\System32\spool\PRINTERS in File Explorer.
2. Observe leftover .SHD and .SPL files that persist even after clicking 'Cancel' in the Windows print queue.

# Step-by-Step Fix:

1. Open PowerShell as Administrator.
2. Execute Nuclear Spooler Reset Script:

powershell
   Stop-Service -Name "Spooler" -Force
   Get-ChildItem -Path "$env:SystemRoot\System32\Spool\PRINTERS\*" | Remove-Item -Force
   Start-Service -Name "Spooler"

3. Verify Queue Cleared:

powershell
   Get-Printer | Get-PrintJob

# Prevention & Long-Term Monitoring:

Refer to Microsoft Official Support Guide for official print queue resetting tools.

Avoid sending corrupted PDF files or raw PostScript files directly to non-PostScript printers.

EMF/RAW Spool File Bloat & Disk Space Exhaustion

Solution:

Root Cause: Vector Graphics Rendering Expansion in Spool Payload

When printing complex vector graphics or high-DPI images, the Windows GDI rendering engine translates EMF (Enhanced Metafile) records into uncompressed RAW bitmap data. A 10 MB PDF can expand into a multi-gigabyte .SPL spool file, exhausting system disk space and crashing the spooling routine.

# Diagnostic Verification:

1. Check free space on the OS boot drive (C:).
2. Inspect C:\Windows\System32\spool\PRINTERS to see if .SPL file sizes exceed several gigabytes.

# Step-by-Step Fix:

1. Enable 'Print Directly to the Printer' (Bypass Spooler Buffer):

Open Printer Properties > Advanced tab.

Select Print directly to the printer (Requires adequate onboard printer memory).

2. Change Spool Data Format to RAW / Disable Advanced Printing Features:

Under Printer Properties > Advanced tab, uncheck Enable advanced printing features.

3. Relocate Spool Directory to Secondary Drive (If C: is small):

Open printmanagement.msc > Right-click Print Servers (local machine) > Properties.

Under Advanced tab, change Spool folder path to an alternative volume (e.g., D:\Spool).

# Prevention & Long-Term Monitoring:

Ensure the primary system drive maintains at least 15% free unallocated space for print rendering buffers.

Print Queue Access Permission Conflict

Solution:

Root Cause: Insufficient User Print Management Rights across Network Shares

When printing to a shared network printer managed by a central print server, a job sent by a user without 'Manage Documents' or 'Print' permissions gets stuck when attempting to initialize administrative queue locks.

# Diagnostic Verification:

Attempting to delete or pause a stuck print job returns error: Access is denied.

# Step-by-Step Fix:

1. Adjust Printer Security Permissions:

On the print server or local PC, open Printer Properties > Security tab.

Select EVERYONE or Authenticated Users.

Ensure Print permission is set to Allow.

Allow non-administrative users to clear their own stuck documents by setting Manage Documents = Allow.

2. Purge Queue via Command Line as Administrator:

cmd
   net stop spooler
   del /Q /F /S "%systemroot%\System32\Spool\PRINTERS\*.*"
   net start spooler

# Prevention & Long-Term Monitoring:

Audit Active Directory Security Groups assigned to corporate print queues.

Printer Hardware Alert Event / Queue Paused State

Solution:

Root Cause: Uncleared Paper Jam, Low Toner Condition, or Cover Open Sensor State

Modern printer drivers monitor physical hardware sensors using SNMP or bi-directional USB communication. If a paper jam occurs or cover sensor trips, the driver shifts the Windows print queue status to Paused or Attention Required and keeps it paused even after clearing the jam.

# Diagnostic Verification:

1. Open Print Queue window.
2. Look at the title bar or status column for Paused or Printer - Attention Required.

# Step-by-Step Fix:

1. Resume Printer Queue via GUI / PowerShell:

In Print Queue window, click Printer menu > Uncheck Pause Printing.

Or via PowerShell:

powershell
     Resume-PrintJob -PrinterName "YourPrinterName"

2. Disable Bi-Directional Support (If False Sensor Alerts Persist):

Open Printer Properties > Ports tab.

Uncheck Enable bidirectional support.

Click Apply.

3. Perform Hard Hardware Reset:

Disconnect power cable from printer for 60 seconds to clear onboard sensor memory flags.

# Prevention & Long-Term Monitoring:

Keep optical paper sensors clean and use supported paper media weights.

What type of rendering corruption or driver output fault is occurring?

Printer outputs endless pages of raw code, symbols, or PostScript errors (e.g., %!PS-Adobe).
Printed documents have missing text, incorrect margins, corrupt images, or blank pages.
Driver installation fails with error 0x00000057 or 'The specified printer driver is currently in use'.
Printing is extremely slow (takes several minutes per page) when printing graphics or PDFs.

PostScript / PCL Driver Mismatch (Garbage Character Output)

Solution:

Root Cause: Page Description Language (PDL) Incompatibility

When a PostScript (PS) driver sends raw PostScript commands to a printer that only understands Printer Command Language (PCL) or host-based (GDI/XPS) languages, the printer cannot interpret the stream and prints raw code lines across hundreds of pages.

# Diagnostic Verification:

Printer outputs lines beginning with %!PS-Adobe-3.0, PCL XL error, or random ASCII symbols.

# Step-by-Step Fix:

1. Identify Printer Supported Language:

Check printer technical specifications to confirm if it supports native PostScript 3, PCL6, or PCL5.

2. Switch to Universal PCL6 / KPDL Driver:

Open printmanagement.msc > Custom Filters > Printers.

Right-click printer > Properties > Advanced tab.

Click New Driver... and install a PCL6 Universal Print Driver or vendor-specific PCL6 driver.

3. Cancel Active Spool Payload Immediately:

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

# Prevention & Long-Term Monitoring:

Use vendor PCL6 drivers by default unless explicit PostScript graphics workflows (e.g., Adobe Illustrator) are required.

Corrupted Windows Driver Package / Clean Driver Store Removal

Solution:

Root Cause: Damaged DLL Dependencies or Fragmented Driver Package in DriverStore

When print output renders missing text elements, garbled fonts, or blank pages, core rendering DLLs inside C:\Windows\System32\DriverStore\FileRepository have become corrupted or mixed across different driver versions.

# Diagnostic Verification:

Native Windows Test Page fails to print correctly, or displays missing font entries.

# Step-by-Step Fix:

1. Delete Corrupted Driver Package via Print Management:

Press Win + R, type printmanagement.msc, press Enter.

Navigate to Drivers.

Right-click the affected driver > Remove Driver Package....

Select Delete driver and driver package.

2. Force Delete Stale Driver Packages via PnPUtil (If Package in Use):

Open Command Prompt as Administrator.

List third-party print drivers:

cmd
     pnputil /enum-drivers

Force remove the corrupted driver package:

cmd
     pnputil /delete-driver oemXX.inf /uninstall /force

3. Install Fresh OEM Driver:

Download driver package directly from official manufacturer support portal (e.g., HP, Canon, Epson, Xerox, Brother).

# Prevention & Long-Term Monitoring:

Avoid using generic Windows Update optional drivers for complex multi-function printers.

Driver Installation Blocked ('Driver Currently In Use')

Solution:

Root Cause: Active Memory Lock on Driver Files by Spooler / Driver Isolation Processes

Windows prevents deleting or updating a print driver if any running service or background process retains an open file lock on files in C:\Windows\System32\spool\drivers\w32x86 or x64.

# Diagnostic Verification:

Attempting to delete a driver yields error: The specified printer driver is currently in use.

# Step-by-Step Fix:

1. Stop Dependent Services:

powershell
   Stop-Service -Name "Spooler" -Force
   Stop-Service -Name "Fax" -Force

2. Clear Driver Isolation Host Processes:

Open Task Manager (Ctrl + Shift + Esc).

End any running instances of PrintIsolationHost.exe.

3. Delete Environment Driver Registry Keys:

Open regedit > Navigate to:

HKLM\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3

Delete the key associated with the stuck driver.

4. Restart Spooler Service:

powershell
   Start-Service -Name "Spooler"

# Prevention & Long-Term Monitoring:

Always remove printer objects from Devices and Printers prior to attempting driver package removal in Print Management.

Extremely Slow Printing Throughput / High DPI Spool Bottleneck

Solution:

Root Cause: High Print Resolution Settings and Passthrough Font Substitution Failure

When document printing takes several minutes per page, the printer driver is rendering document graphics at excessive resolutions (e.g., 1200 DPI) or sending fonts as bitmap outlines rather than using printer resident fonts.

# Diagnostic Verification:

Small text documents process instantly, but PDF or web pages stall processing for 3–5 minutes per page.

# Step-by-Step Fix:

1. Adjust Print Quality & Font Settings:

Open Printer Properties > Printing Preferences.

Change Print Quality from 1200 DPI to 600 DPI.

Go to Advanced tab > Enable Substitute with Device Font.

2. Enable 'Print as Image' for PDF Documents (Adobe Reader):

Inside Adobe Acrobat / Reader, click Print > Advanced.

Check Print As Image.

3. Change Port Configuration Protocol:

In Printer Properties > Ports > Configure Port....

Switch protocol from LPR to Raw (Port 9100).

Ensure LPR Byte Counting Enabled is unchecked.

# Prevention & Long-Term Monitoring:

Use 600 DPI rendering profiles for everyday office document workflows to optimize network payload sizes.

Related Diagnostic Guides

SharePoint Online Access Denied Even as Owner

Interactive: Game Crashes - Overheating, Driver, or Corrupted Files?

Intune Device Compliance Failed: Conditional Access Fix

Entra ID Sync Error: Duplicate Proxy Address

Power Automate Flow Failed: Connector Timeout Diagnostic

Subscribe to StepDiag

Embed Guide on Your Website