Printer Spooler STATUS_TOO_MANY_LINKS 0xC0000265 Fix

When This Error Hits

You're printing a PDF or a multi-page Word doc. The print queue shows 'Printing' for a few seconds, then the spooler service crashes. Check Event Viewer — you'll see STATUS_TOO_MANY_LINKS (0xC0000265) logged against spoolsv.exe. This happens most often on servers or workstations that have been running months with lots of printer drivers installed, or after adding a network printer that uses a driver with many hard links.

Root Cause

What's actually happening here is the NTFS file system hitting its per-file hard link limit. Every file on NTFS can have at most 1023 hard links — that's the hard limit baked into the file system structure. The printer spooler uses hard links internally for managing print jobs and driver files. When a single file (usually a spool file or driver DLL) crosses that 1023-link ceiling, Windows throws 0xC0000265 and the spooler dies.

It's not a printer hardware problem. It's not a missing driver. It's the file system saying "I can't make another link to this file, I'm full." The reason this shows up during printing is that the spooler creates and destroys hard links rapidly during spooling — one bad driver that keeps creating links without deleting them will push a file past the limit.

Fix It — Step by Step

Step 1: Stop the Spooler

Open an admin Command Prompt or PowerShell and run:

net stop spooler

Or use services.msc, find the Print Spooler, right-click and Stop. The spooler won't stay running after a crash anyway, but this ensures nothing else touches the files.

Step 2: Clear the Spooler Folder

Navigate to C:\Windows\System32\spool\PRINTERS. You'll see .SPL and .SHD files — those are spooled print jobs. Delete everything in there. Do not delete the folder itself, just the contents. If Windows says files are in use, reboot into Safe Mode or use a Live USB — but on a crashed spooler, they should be free.

Step 3: Clean Up Printer Drivers

This is the real fix — removing drivers that created too many links. Go to Settings > Bluetooth & Devices > Printers & Scanners. Remove every printer you aren't actively using. Then open an admin PowerShell and run:

Get-Printer | Format-List Name, DriverName
Get-PrintDriver | Format-List Name, MajorVersion, MinorVersion

Look for drivers with multiple versions — HP, Brother, and Canon drivers are notorious for leaving old versions behind. Remove stale drivers with:

Remove-PrintDriver -Name "Driver Name Here"

Step 4: Check Hard Link Counts

To find the culprit file, you need to check link counts. Use fsutil:

fsutil hardlink list C:\Windows\System32\spool\DRIVERS\x64\3\UNIDRV.DLL

But the real trick is to find the file with the highest link count. I use a PowerShell one-liner:

Get-ChildItem -Path "C:\Windows\System32\spool\DRIVERS\x64\3\" -Recurse -File | ForEach-Object { $_.LinkCount; $_.FullName } | Out-File -FilePath "C:\linkcheck.txt"

Sort the output — any file with a link count over 1000 is your problem. Delete or rename it (after backing up).

Step 5: Restart the Spooler

net start spooler

Try printing again. If it works, the error is gone. If not, move to the next section.

If It Still Fails

Two things can still trip you up:

• Registry corruption in spooler keys. Open regedit, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler. Check if the Start value is 4 (disabled) — set it to 2 (auto). Also check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\ for orphaned printer entries. Delete those carefully.
• Antivirus locking spooler files. Some AV software (looking at you, McAfee) hooks into spooler file operations and creates hard links for scanning. Temporarily disable the AV's file system scanner and retry. If it works, add an exclusion for C:\Windows\System32\spool\ in your AV settings.

If none of that works, the spooler subsystem itself might be damaged. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. On a server, consider moving to a dedicated print server — this error is more common when a single machine hosts dozens of printer drivers.

One last thing: this error never means your printer hardware is bad. Don't waste time swapping cables or reinstalling the same driver. The fix is always on the file system side.