Fix 0X0000084A: Peer service max user limit reached
This error means Windows Peer service hit its 10-user limit. The fix is either upping the limit or killing stale connections. Here's how.
Quick answer for advanced users
Open Regedit, go to HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters, create or set Users (DWORD) to a higher value like 20 or 50, then restart the Server service or reboot.
What's actually going on
This error pops up when Windows Peer Networking Service – the thing that lets you share files and printers without a dedicated server – hits its built-in cap of 10 simultaneous user connections. Microsoft stuck that limit in decades ago to push folks toward proper server OS licenses. I've seen this most often in small offices running Windows 10 Pro or Windows 11 Pro, where someone's sharing a QuickBooks database or a shared folder for project files. One client had a team of 12 all trying to access the same shared drive, and boom – error 0X0000084A on user number 11. The error text says 'two simultaneous users' but that's a misleading translation from the old LAN Manager days – the real limit is 10.
Fix it in numbered steps
- Check current connection count. Open Command Prompt as admin and run
net session. You'll see how many active connections you've got. If it's 10 or close to it, that's your issue. - Bump the registry limit. Hit Win+R, type
regedit, press Enter. Navigate toHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters. Right-click in the right pane, choose New > DWORD (32-bit). Name itUsers. Double-click it, set the value to something like 20 or 50 (decimal). This overrides the 10-user cap. - Apply the change. Open Command Prompt as admin, run
net stop serverthennet start server. Or just reboot – either works. - Verify it's working. Try connecting from the machine that was getting the error. Should go through now.
If that doesn't do it – alternative fixes
Sometimes the registry tweak doesn't kick in because of lingering session handles. Here's the nuclear option:
- Kill stale connections. Run
net session /deletein Command Prompt as admin. This boots everyone off. Reconnect from the client machine – the registry change should now apply cleanly. - Check for third-party software limits. Some VPNs or remote desktop tools mess with the Peer service. I had a client whose LogMeIn session counted as a 'user' connection, eating up a slot. Disconnect that and test.
- Upgrade to Windows Server. If you consistently need more than 10 simultaneous connections, Windows 10/11 isn't your tool. Get a Windows Server license – it handles hundreds without this nonsense.
Prevent it from coming back
The registry fix works, but it's a band-aid. If you're regularly over 10 users, your network's outgrown peer-to-peer sharing. Plan for a proper server. Also, train users to log off shared folders when they're done – I've seen people leave folders open overnight, and those connections don't drop until the machine reboots. Set a scheduled task to run net session /delete nightly if you want to be proactive.
Had a client last month whose entire print queue died because of this error on a shared printer – the fix above got them printing again in five minutes, but I still had to talk them into buying a dedicated print server.
If you're still stuck, check Event Viewer under System logs for Event ID 2019 – that'll confirm the exact connection count when the error hit.
Was this solution helpful?