Windows Server 2022 — Print Spooler Service Crashes in Loop on Multi-Function Driver Update — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Quick Checks
3. Deep Diagnosis
4. Primary Fix
5. Verification
6. Prevention & Hardening

Symptom & Impact

The Print Spooler service terminates repeatedly after a vendor driver update, stopping all print queues. Departments relying on label or invoice printing experience immediate operational disruption. Spooler restarts temporarily recover then fail again.

Quick Checks

Confirm crash signatures, recently installed print drivers, and queue backlog patterns.

Get-Service Spooler
Get-PrinterDriver
Get-WinEvent -LogName Application -MaxEvents 80 | Where-Object {$_.ProviderName -match 'PrintService|Application Error'}

Deep Diagnosis

Identify faulting DLLs and isolate problematic third-party processors or language monitors.

Get-WinEvent -LogName 'Microsoft-Windows-PrintService/Admin' -MaxEvents 120
reg query 'HKLMSYSTEMCurrentControlSetControlPrintMonitors'
Get-ChildItem C:WindowsSystem32spooldriversx643

Primary Fix

Remove unstable drivers, clear stuck jobs, and re-add queues with Type 4 or vendor-certified package versions.

Stop-Service Spooler -Force
Remove-Item C:WindowsSystem32spoolPRINTERS* -Force
Remove-PrinterDriver -Name 'Vendor Universal PS'
Start-Service Spooler

Verification

Spooler should remain running while test pages print successfully across affected queues.

Get-Service Spooler
Get-Printer | Select Name,PrinterStatus
Start-Process -FilePath rundll32.exe -ArgumentList 'printui.dll,PrintUIEntry /k /n \print01Finance'

Prevention & Hardening

Stage driver rollouts and block unsigned or unapproved packages using print server governance policy.

Get-PrinterDriver | Select Name,MajorVersion,Manufacturer
Set-ItemProperty 'HKLM:SoftwarePoliciesMicrosoftWindows NTPrintersPointAndPrint' -Name RestrictDriverInstallationToAdministrators -Value 1