Fix ERROR_SPOOL_FILE_NOT_FOUND 0X00000BBA in Under 30 Seconds
That spool file error means Windows can't find a print job file. Usually a stuck print queue or corrupted spooler. Here's how to fix it fast.
The 30-Second Fix: Clear the Stuck Print Queue
Nine times out of ten, this error shows up when you've got a print job stuck in the queue. Windows can't find the temporary file it created, so it throws 0X00000BBA. The quickest way out is to purge the queue manually.
- Open Services: Hit Win + R, type
services.msc, press Enter. - Stop the Spooler: Find Print Spooler in the list. Right-click it and select Stop. Do not close Services yet.
- Delete the Spool Files: Open File Explorer and go to
C:\Windows\System32\spool\PRINTERS. Delete everything in that folder. You'll see.SHDand.SPLfiles — those are the spool files. Trash them all. - Restart the Spooler: Go back to Services, right-click Print Spooler again, and hit Start.
That's it. Try printing again. If the error's gone, you're done. This works on Windows 10, 11, and even Server 2019. I've seen it fix the issue instantly on hundreds of machines.
5-Minute Fix: Check the Spooler Service and Dependencies
If the queue's clear but the error comes back, the spooler service itself might have stopped or got misconfigured. Here's what to check.
Go back to Services. Double-click Print Spooler. Make sure the Startup type is set to Automatic. Then click Start if it's not running. Hit Apply and OK.
Now look at dependencies. The spooler relies on HTTP Service and Remote Procedure Call (RPC). If either of those is off, the spooler won't start. In Services, find Remote Procedure Call (RPC) — it should be running and set to Automatic. Same for HTTP Service if it exists on your system. On Windows 10, it's usually automatic.
While you're there, check if the spooler's logon account is correct. Right-click Print Spooler > Properties > Log On tab. It should be Local System account. If someone changed it to a user account, that'll break things. Set it back.
One more thing: Open Event Viewer (eventvwr.msc) and look under Windows Logs > System for any Print Spooler errors. You'll often see Event ID 7031 or 7034 — those tell you the service crashed. The details might point to a specific driver. We'll deal with that next.
15+ Minute Fix: Reinstall or Update the Printer Driver
If the queue's clean and the service is running but you still get 0X00000BBA, the culprit is almost always a corrupt or incompatible printer driver. You'll see this after a Windows update or when mixing drivers from different printer models.
First, remove the printer. Go to Settings > Bluetooth & devices > Printers & scanners. Click on your printer, then Remove device. Confirm.
Now remove the driver. In the same settings page, scroll down and click Print server properties (a bit hidden, but it's there). Go to the Drivers tab. Find your printer's driver in the list. Select it, click Remove, and choose Remove driver and driver package. This nukes everything, including the inf files. If you're on a network printer, you might need admin rights for this.
Restart the computer — don't skip this. After reboot, Windows will try to auto-install the printer. Let it. Or, download the latest driver from the manufacturer's site. For HP, go to HP Support; for Brother, their support page; for Canon, same deal. Don't use the generic Windows driver unless you're stuck. It often lacks features and can cause spooler issues.
Install the driver fresh. Add the printer back. Test with a simple Notepad print. If the error still shows, run the built-in troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Printer. It's not a silver bullet, but it catches obvious misconfigurations.
Last resort: check for corrupt system files. Open Command Prompt as admin and run sfc /scannow. Let it finish. Then run DISM /Online /Cleanup-Image /RestoreHealth. This can fix spooler components that got corrupted. I've seen this fix a stubborn spooler after a failed Windows update.
If you're still stuck after all that, consider a full printer driver cleanup tool like Print Management Console (printmanagement.msc) or a third-party tool like DriverStore Explorer to remove leftover driver packages. Sometimes old driver files linger and cause conflicts.
That's the full rundown. Start with the queue, check the service, then kill the driver. One of these will get you printing again.
Was this solution helpful?