How to fix Error 231 on Windows 11

by

Windows 11 Troubleshooting: Error 231 – “All Pipe Instances Are Busy”

Why This Error Happens

Error 231 occurs when a client application attempts to connect to a named pipe (a form of inter-process communication, often used for network printing, RPC, or service-to-service communication), but the server has reached its maximum configured limit of simultaneous pipe instances. This typically happens due to a resource leak where connections aren’t properly closed, an overloaded print spooler, or a misconfigured service that limits the number of concurrent connections it can accept. In many cases, this is triggered by network printer connections or third-party backup/remote software creating too many concurrent handles.

Step-by-Step Resolution Guide

  1. Restart the Print Spooler Service (most common cause for this error):
  • Press Win + R, type services.msc, and press Enter.
  • Locate Print Spooler in the list, right-click it, and select Restart.
  • If the issue recurs frequently, right-click Print Spooler → Properties → set Startup type to Automatic (Delayed Start).
  1. Clear the Print Spooler Queue and Cache:
  • Stop the Print Spooler service via services.msc.
  • Navigate to C:\Windows\System32\spool\PRINTERS and delete all files inside this folder.
  • Restart the Print Spooler service.
  1. Check for Resource Leaks via Task Manager:
  • Open Task Manager (Ctrl + Shift + Esc) and check for any application repeatedly spawning processes (e.g., backup agents, RPC-dependent apps, or SQL Server client tools).
  • End any suspicious or unresponsive processes that may be holding pipe handles open without releasing them.
  1. Increase Named Pipe Instance Limit (for custom applications/services):
  • If the error originates from a custom service or SQL Server, check the application’s configuration file or registry settings for MaxInstances.
  • For SQL Server, verify the \\.\pipe\sql\query configuration isn’t capped too low in SQL Server Configuration Manager under SQL Server Network Configuration.
  1. Run System File Checker to Rule Out Corruption:
  • Open Command Prompt as Administrator.
  • Run: sfc /scannow
  • Follow with: DISM /Online /Cleanup-Image /RestoreHealth
  • Restart your PC once complete.

Alternative or Verification Steps

  • Verify the fix: Attempt the original action (e.g., printing, connecting to the network share, or running the affected application) that previously triggered Error 231. If successful without delay or error, the pipe instance issue is resolved.
  • Alternative: If the error persists and involves a specific third-party application, check for and install the latest updates/patches for that software, as vendors often release fixes for known pipe-handling bugs.