Printer Spooler Crash: Fix 0X00000476 Too Many Links

Yeah, that 0X00000476 error is a classic. It pops up when you try to print and nothing happens — or the spooler just crashes. The culprit here is almost always the spooler folder hitting the NTFS hard link limit. Don't bother reinstalling drivers yet. That rarely helps.

Fix It: Clear the Spooler Folder

You need to stop the spooler, nuke the queued jobs, and restart it. Here's the exact sequence:

1. Open Command Prompt as Administrator. Type net stop spooler and hit Enter. The service stops immediately.
2. Now open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS. Delete everything in that folder. Yes, everything. Those are orphaned .SHD and .SPL files — they're the links causing the error.
3. Back in Command Prompt, type net start spooler and press Enter.
4. Try printing again. It'll work.

This works because NTFS has a hard limit of 1023 hard links per file in some configurations — especially on older Windows 10 builds or systems with large volumes of stalled print jobs. The spooler creates a link for each pending job. Once you hit that ceiling, it throws 0X00000476. Clearing the folder resets the count.

Less Common Variations

Sometimes the error isn't in the PRINTERS folder itself. Check these spots too:

• System Temp folder (%TEMP%) — leftover printer spooler temp files can build up. Run Disk Cleanup to clear them.
• Driver cache — corrupted printer drivers can create ghost links. Open Print Management (printmanagement.msc), right-click your printer, and select Remove Printer Driver. Reinstall clean.
• Network shares — if you're printing to a network printer, the server might have the same issue. Run the same fix there.

If you're still stuck after clearing the folder, check the Event Viewer for System logs around the time of the crash. Filter by source PrintService. If you see event ID 808, that confirms the spooler ran out of memory. That's a different fix — increase the spooler's memory limit in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Spooler
Value: SpoolerMemoryLimit
Type: DWORD
Data: 0 (or higher in bytes, default is 0 = unlimited)

Set it to 0 for unlimited unless you're on a really tight system. That usually stops the memory-related crashes.

Prevention

This error happens because people let print jobs pile up. Set a scheduled task to clear the PRINTERS folder weekly. Use this PowerShell script:

Get-ChildItem "C:\Windows\System32\spool\PRINTERS" -Recurse | Remove-Item -Force

Run it daily if you manage a busy print server. Also, update your printer drivers every six months — old drivers can leak jobs and create those orphaned links faster.

One more thing: if you're on a domain, check Group Policy for Printer retention settings. Some policies keep completed jobs for auditing. That's a direct cause of this error. Disable that unless you need the logs.