Fix Printer Spooler Crash After Windows Update

When You See This Error

You try to print a document – maybe a PDF or a Word file – and nothing happens. The print queue shows the job stuck with a status like "Deleting – Printing" or simply errors out. Then you get a popup: "Spooler SubSystem App has stopped working" or the Event Viewer logs a 7031 or 7034 error for the Print Spooler service. This usually happens right after a Windows 10 22H2 or Windows 11 23H2 cumulative update, especially on machines with HP, Canon, or Brother network printers.

Root Cause

The spooler crashes because of a corrupt printer driver – specifically one that didn't survive the update cleanly. Windows updates sometimes reset permissions on the %windir%\system32\spool\PRINTERS folder or leave orphaned registry entries under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers. When the spooler tries to load a driver with bad data, it chokes and stops. Don't bother reinstalling the printer from scratch – the registry rot stays unless you clean it manually.

How to Fix It

This fix works for Windows 10 (1809+) and Windows 11. Do these steps in order. If you skip a step, you'll be back here in 10 minutes.

Stop the spooler service. Open Command Prompt as Administrator. Run:
```
net stop spooler
```
The spooler will stop. If it doesn't, run sc query spooler to check its state – it might already be crashed.
Delete everything in the spool folder. Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS. Delete all files inside. Don't delete the folder itself – just the contents. This clears stuck print jobs. Use del /F /Q C:\Windows\System32\spool\PRINTERS\*.* from an admin prompt if Explorer refuses.
Remove corrupt drivers from the registry. Run regedit as Administrator. Go to:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers\Version-3
```
(For 32-bit systems it's Windows NT x86). Look for subkeys named after your printer brand, like "HP Universal Printing PCL 6" or "Canon MF244dw". Right-click and delete them. Be careful – only delete the printer-specific keys, not the entire Drivers folder.
Restart the spooler service. Back in the admin Command Prompt, run:
```
net start spooler
```
Check that it's running with sc query spooler | find "STATE". You should see RUNNING.
Reinstall the printer driver fresh. Download the latest driver from your printer manufacturer's site – not the one Windows Update offers, which is often stripped down. Install it as Administrator (right-click, Run as Administrator). Add the printer again via Settings > Bluetooth & devices > Printers & scanners > Add device.
Print a test page. Once the printer is back, right-click it in Settings and choose Print a test page. If it works, you're done. If not, see the next section.

What to Check If It Still Fails

If the spooler crashes again after a reboot, check these:

Third-party antivirus – McAfee and Norton sometimes quarantine spooler files. Disable real-time protection temporarily and test.
Event Viewer logs – Look under Windows Logs > System for spooler errors. The faulting module path (like C:\Windows\System32\spool\DRIVERS\x64\3\hpcpp10.dll) tells you which driver is the problem. Delete that specific file and the corresponding registry key, then reinstall.
Corrupt spooler folder permissions – The PRINTERS folder should have SYSTEM and Administrators with Full Control. Use icacls C:\Windows\System32\spool\PRINTERS /grant SYSTEM:F Administrators:F to fix it.
Hardware conflict – If it's a USB printer, try a different USB port or cable. For network printers, reset the printer's network settings and confirm its IP hasn't changed.

This fix kills the problem 9 times out of 10. The other 1 time, it's a sign the printer itself has a dying mainboard – but that's rare. Start with the steps above.