Quick answer: Restart the Print Spooler service and clear the spooler cache: net stop spooler, delete C:\Windows\System32\spool\PRINTERS\*, then net start spooler. That fixes nine out of ten cases.
You're mid-boss fight, hit print, and instead of a nice map you get a cryptic 0x0000011B error. This isn't a game issue—it's Windows throwing a hissy fit because the print spooler, the service that manages print jobs, is either hung up or losing connection to the print server. I've seen this on Windows 10 21H2 and 11 22H2, often after a game updates its anti-cheat (looking at you, Vanguard) or when a printer driver gets half-updated. The error code itself points to a RPC (Remote Procedure Call) failure, which basically means Windows can't talk to the spooler properly. Games don't cause it, but they're often the trigger because they hog resources and push the spooler to timeout.
What Actually Causes Error 0x0000011B
Three common culprits: a corrupted spooler cache, a printer driver that's out of date or conflicts with a recent Windows update, or a third-party firewall/security app blocking RPC ports. The spooler stores print jobs as files in %SystemRoot%\System32\spool\PRINTERS. If one of those files gets corrupted (like when you force-quit a game while a print job is pending), the spooler chokes. Also, Microsoft's October 2023 patches changed some security defaults for RPC, which broke older drivers—real thing, not a conspiracy.
Fix 1: Restart the Print Spooler and Clear Cache
- Open Command Prompt as administrator (right-click Start, select Command Prompt (Admin) or Terminal (Admin)).
- Type
net stop spoolerand hit Enter. The service stops. - Now open File Explorer, go to
C:\Windows\System32\spool\PRINTERS. Delete everything inside that folder. Don't delete the folder itself. - Back in Command Prompt, type
net start spoolerand hit Enter. - Try printing again. This clears any junk that's jamming the works.
I had a client last month whose entire print queue died because a Powerpoint file from 2019 got stuck in there. This exact step saved him from reinstalling his HP driver.
Fix 2: Update or Reinstall the Printer Driver
If the spooler restart didn't do it, the driver's the usual suspect. Go to Settings > Bluetooth & devices > Printers & scanners. Click your printer, then choose 'Printer properties' (not 'Printing preferences'). Under the Driver tab, note the driver version. Then go to the manufacturer's site—HP, Canon, Epson, whatever—and grab the latest driver for your exact model and your Windows version. Don't use Windows Update's generic driver, it's usually garbage. Uninstall the old one first: right-click the printer in Devices and Printers, choose 'Remove device', then reboot and install the fresh one.
Fix 3: Check RPC Ports and Firewall Rules
This one's less common but happens with corporate networks or aggressive AV suites. Error 0x0000011B is an RPC error, and RPC uses dynamic ports (49152-65535). If your firewall is blocking those, you'll see this. For a home setup, try temporarily disabling your third-party firewall (not Windows Defender—that's not it) and test. If it works, add an allow rule for %SystemRoot%\System32\spoolsv.exe. For business networks, make sure the print server is reachable—ping it by name, not just IP, because DNS can throw a curveball.
Alternative Fixes If Those Don't Work
Sometimes the spooler cache and driver are fine, and the problem is deeper. Here's what I'd try next:
- Run the Windows Print Troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Printer. It's a band-aid, but sometimes it identifies a service dependency issue.
- Reinstall Windows Update KB5029351: That October 2023 patch caused RPC issues. Go to Settings > Windows Update > Update history > Uninstall updates, remove KB5029351, then reboot. Test printing. If it works, you can reinstall it later.
- Clean boot: Disable all non-Microsoft services via msconfig, then print. If it works, enable services one by one to find the culprit. It's tedious but effective.
Prevention: Stop It Before It Happens
The best way to avoid this? Don't print while a game is running, especially if the game uses anti-cheat that hooks into system processes. Also, make a habit of clearing the spooler cache monthly: stop the spooler, delete those files, start it back up. And keep your printer driver updated—set a reminder or use the manufacturer's update tool if they have one. Driver updates are boring, but they fix these exact RPC/timeout bugs.
If you're still stuck after all this, check if you have any 'virtual printers' like Microsoft Print to PDF or OneNote installed. Sometimes those conflict. Uninstall the ones you don't use, restart, and try again. I've seen that solve a weird variant where only certain apps failed.