Custom monitors for print spooler stability
Overview
Print spooler crashes still plague LOB apps—detect before users chain-call.
Signals
Spooler service not running, queue depth > threshold, recurring driver isolation events.
Auto-remediation (careful)
Restart spooler once; if repeats in 24h escalate—avoid infinite restart loops masking malware.
Root causes
Bad driver, corrupted jobs, PrintNightmare mitigations conflicting with vendor requirement.
Docs
Known good driver versions pinned per printer model in client appendix.
Related Articles
EDR deployment checklist for new workstations
## Overview Use this runbook when onboarding a new Windows workstation or re-imaging a device that...
Handling Defender for Business false positives
## Overview False positives waste analyst time and train users to ignore alerts. This article stand...
Application allowlisting with Windows Defender ASR rules
## Overview Attack Surface Reduction (ASR) rules reduce exploit surface by constraining Office macr...