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.

Why the consumer advice doesn’t apply here: the usual fix (clear spool\PRINTERS, reset print-processor keys) targets a corrupt queue. On a server, the spooler is very often disabled deliberately by a Group Policy — a common PrintNightmare mitigation set it to Disabled, so it restarts then immediately stops again, and cache-clearing never resolves it. Check policy first.

Fix 1: Find the GPO that disabled it

The spooler stopping right after you start it = something is forcing it off:

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. Edit the GPO (or move the server to an OU without it) to set Print Spooler Automatic, then gpupdate /force.

If this is a print server that must serve clients, the supported hardening is to keep the spooler running but lock down the RPC interface — see CVE-2021-1678 printer RPC hardening — rather than disabling the service outright.

Fix 2: Clear the queue and remove bad drivers

If no policy is forcing it off, then it’s the same crash causes as on a client:

1. services.msc → Stop Print Spooler.
2. Delete everything in C:\Windows\System32\spool\PRINTERS.
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

Server AV that scans spool\PRINTERS can lock files and crash the spooler. Add the C:\Windows\System32\spool path to the AV’s exclusions, then restart the service.

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? Either a GPO set it to Disabled (Fix 1) or a corrupt job/driver crashes it on launch (Fix 2). On servers, suspect the GPO first.

Is disabling the spooler a valid security step? Yes — on servers that don’t print, disabling it is a legitimate PrintNightmare mitigation. If you need printing, keep it running and harden the RPC interface instead.

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

Sources: Microsoft Learn — Print Spooler service is not running (Windows Server)