0x000006be

Printer Spooler Keeps Stopping: Real Fix for Error 0x000006be

EP
Erropedia Team
📅 August 8, 2026 📅 Updated Aug 8, 2026 👁 1 views Hardware – Printers Intermediate
The print spooler crashes with 0x000006be usually due to corrupted spool files or a bad driver. Here's the fix that actually works.

Quick answer

Stop the spooler service, delete everything in C:\Windows\System32\spool\PRINTERS, restart the service. If that doesn't stick, uninstall the printer driver and reinstall with the manufacturer's latest version, not the Windows built-in one.

What's actually happening here is the spooler service (spoolsv.exe) is crashing before it can write or read a print job. The error 0x000006be is a Windows error that maps to ERROR_DELETE_PENDING — a file or object is marked for deletion but still in use. In the context of printing, that almost always means a stuck print job file in the spool folder that the spooler can't process, or a printer driver that's holding onto a file handle that shouldn't be there. When the spooler hits that corrupted state, it dies and Windows restarts it, but if the problem persists, it keeps dying. You'll see the popup "Spooler SubSystem App has stopped working" or just "Printer Spooler service terminated unexpectedly."

I've seen this on Windows 10 and 11, mostly after an update, or after a printer is unplugged mid-print, or when a network printer goes offline while jobs are queued. The fix below clears the junk and replaces the driver that caused it in the first place.

Fix steps (in order)

  1. Clear the spool folder. Open Services (Win+R, type services.msc), find Print Spooler, right-click and Stop. Then open File Explorer and delete everything inside C:\Windows\System32\spool\PRINTERS. If you get an access denied, you didn't stop the service properly.
  2. Restart the spooler. Back in Services, right-click Print Spooler and Start. Try printing something. If it works, you're done — it was just a corrupted job file. If it crashes again, move on.
  3. Uninstall the printer driver. Go to Settings > Devices > Printers & scanners, select your printer, Remove device. Then open Print Management (Win+R, type printmanagement.msc). Under Print Servers > Drivers, right-click any driver for that printer and Remove. Check both "Remove driver package" boxes if it asks.
  4. Reinstall the driver. Download the latest driver from the manufacturer's site. Do not use Windows Update's version — I've seen that one cause this exact error because it's generic and missing the port monitor bits. Install, restart your PC, then re-add the printer.

If that fails

The main steps work for most people, but sometimes the corruption runs deeper. Here's what to try next.

Run the spooler as a different account

By default, the spooler runs as LocalSystem. If that account's profile is corrupted, the spooler can crash on startup. Change it to NetworkService temporarily: in Services, right-click Print Spooler > Properties > Log On tab, select This account, type NT AUTHORITY\NetworkService, leave the password blank, restart the service. This is a diagnostic step, not a permanent fix — if it stabilizes the spooler, you've confirmed the profile issue, but you should really create a new admin account or do a system restore.

Repair system files

Corrupted system files can also trigger this. Open an elevated Command Prompt and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth. This takes a while, but I've seen it fix spooler crashes that nothing else touched. The reason it works is that the spooler relies on several DLLs, and if one of them got hosed by an update, the whole thing falls apart.

Check for third-party software

I once spent hours on this, only to find that a "printer optimizer" utility (from the printer's own CD) was injecting into the spooler process. Uninstall any printer-related utilities that came with the device — you don't need them. The driver alone is enough.

Prevention

This error is almost always caused by a bad driver or a corrupted spool file. To avoid it:

  • Never unplug a printer while it's printing. Let the job finish or cancel it from the queue first.
  • If a print job gets stuck, clear the queue before restarting the spooler. Right-click the printer > See what's printing, cancel all documents, then restart the spooler.
  • Update the driver from the manufacturer's site, not Windows Update. Set a reminder to check every few months if you print often.
  • If you use a network printer, make sure it's on a static IP. I've seen the spooler crash when the printer's IP changes and the driver can't find the port.

The spooler is a fragile piece of infrastructure. Once you've fixed it once, you'll know exactly what to do the next time — because there will be a next time, trust me.

Related Errors in Hardware – Printers
Printer Sharing Stopped After Windows Update – Fix Steps Stuck 'Deleting' Print Queue—Fix It in 2 Minutes SMART BAD SMART Status BAD: Backup and Replace Hard Drive Guide 0XC01C001C 0XC01C001C: HP Printer Context Already Linked Fix
printer spooler error 0x000006be spooler keeps stopping fix print spooler crash clear spooler cache printer driver corruption Windows 10 spooler error 0x000006be fix spoolsv.exe crash reset print spooler printer not printing

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.