Print Spooler Won't Stay Running on Windows Server? Check the PrintNightmare GPO First

On a Windows Server (2019/2022/2025), the Print Spooler won’t start, or it starts and stops again on its own — so you can’t install printers or share them.

A security policy can deliberately disable the spooler on a server, but a corrupt job, driver failure or dependency problem can also prevent startup or cause a crash. Check the recorded error, service configuration and effective policy before clearing queues or changing security settings.

Fix 1: Find the GPO that disabled it

A spooler that stops soon after starting can have a policy, driver, queue, dependency or other service failure. Check the service error and Event Viewer before choosing a repair. A security baseline may deliberately disable it; confirm the reason with the policy owner:

1. Run gpresult /h gpreport.html (admin) and open the report, or use RSOP.
2. Look under Computer Configuration → Windows Settings → Security Settings → System Services → Print Spooler — if a policy sets it to Disabled, that’s your cause.
3. Also check Administrative Templates → Printers for “Allow Print Spooler to accept client connections” and related PrintNightmare-era settings.
4. Ask the policy owner why the service was disabled. Do not move the server to another OU to bypass its security policy. If printing is required, first confirm the security prerequisites below; the administrator can then approve a targeted policy change and refresh it with gpupdate /force.

Before re-enabling a service disabled for PrintNightmare: install current security updates on the server and clients, keep printer-driver installation restricted to administrators, and review Point and Print policy for warning/elevation prompts. PrintNightmare is CVE-2021-34527. CVE-2021-1678 RPC hardening addresses a different vulnerability and does not replace these protections. Servers that do not need printing can keep the spooler disabled.

Fix 2: Clear the queue and remove bad drivers

If the logs identify a stuck queue or driver failure, use a targeted repair. Do not remove every driver just because no disabling policy was found:

1. services.msc → Stop Print Spooler.
2. After confirming no needed jobs must be retained, delete only the queued job files inside C:\Windows\System32\spool\PRINTERS. This cancels pending jobs; do not delete the parent spool folder or driver folders.
3. In Print Management (printmanagement.msc), remove duplicate/old drivers for the problem printer.
4. Start the spooler and set Recovery → Restart the Service on failure.

Fix 3: Antivirus locking spool files

If logs identify antivirus interference, collect the error and consult the antivirus vendor. Avoid excluding the whole C:\Windows\System32\spool tree: it contains more than pending jobs, and exclusions reduce protection. Any necessary exception should follow current vendor guidance and have a narrow, reviewed scope.

Fix 4: Confirm dependencies and rebuild

• Ensure Remote Procedure Call (RPC) (RpcSs) is running — the spooler depends on it.
• If the service binary itself is corrupt, sfc /scannow + DISM /Online /Cleanup-Image /RestoreHealth, then restart.

FAQ

Why does it stop the instant I start it? Check the service error and Event Viewer System/Application and PrintService logs. Policy, queue/driver failures and other service problems are possible; the timing alone does not identify the cause. Use the recorded event details to choose the next step.

Is disabling the spooler a valid security step? Yes — on servers that don’t print, disabling it is a legitimate PrintNightmare mitigation. If printing is required, review current patching and secure Point and Print/driver-installation policy before an administrator approves enabling it. RPC hardening alone is insufficient.

This is a desktop, not a server. Use the consumer order in Print Spooler not running.

Sources: Microsoft Support — PrintNightmare protection and Point and Print, Microsoft Support — CVE-2021-1678 RPC changes, Microsoft Learn — Print Spooler service is not running (Windows Server)