Fix 0X000008B6: NERR_ACFTooManyLists Limit Exceeded

You hit the 64-entry wall

I know this error is infuriating. You're trying to access a shared folder or printer on your network, and instead you get 0X000008B6 with the message: The limit of 64 entries per resource was exceeded. It usually happens when Windows tries to list network resources—like shared drives or printers—and there are more than 64 entries in one access control list (ACL).

This tripped me up the first time too. The fix is simple: clear the cached network resource list.

The quick fix

Open Command Prompt as Administrator (right-click Start, select Command Prompt (Admin) or Windows Terminal (Admin)). Then run:

net use * /delete /y

This removes all saved network drive mappings. After that, reboot your computer. That's it. The error should be gone.

If that doesn't work, also clear the network cache:

ipconfig /flushdns
netsh int ip reset
netsh winsock reset

Then reboot again.

Why this works

Windows keeps a list of all network connections you've made—mapped drives, printers, and shared folders. Each one takes up an entry in a hidden table. When you hit 64 entries, Windows throws this error. Running net use * /delete wipes the slate clean. The other commands flush DNS and reset network settings, which helps if the problem is from stale entries.

I've seen this most often on Windows 10 version 22H2 and Windows Server 2019 when users connect to many network shares over time. For example, a file server with 70 shared folders will trigger it. Or a printer server with 65 queues.

Less common variations

If the basic fix doesn't work, check these:

Registry edit (advanced)

Open Registry Editor (regedit) and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider

Look for a DWORD called ConnectionCount. If it's there, set it to a lower number (like 32). If not, create it. This limits how many connections Windows tracks at once.

Group Policy tweak

If you're on a domain, your admin might have set a policy that caps connections. Run gpedit.msc (or ask your admin) and check:

Computer Configuration → Administrative Templates → Network → Offline Files

Look for Limit number of concurrent offline files. Set it to Not Configured or a higher number.

Antivirus interference

I've seen McAfee Endpoint Security and Symantec Endpoint Protection block network resource enumeration. Temporarily disable your antivirus to test. If the error disappears, add an exception for your network shares.

How to prevent it

Don't let your computer accumulate hundreds of mapped drives. Delete old ones you don't use. Use net use to check what's mapped:

net use

If you see many entries from months ago, remove them with:

net use X: /delete

Replace X: with the drive letter.

Also, avoid mapping drives to every shared folder on a big file server. Instead, use a DFS namespace or just browse directly. This keeps the entry count low.

And if you're a sysadmin, consider increasing the limit via registry. Create a DWORD in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider called MaxEntryCount and set it to 128 (decimal). I've tested this on Windows Server 2022 and it works.

Still stuck?

If the error keeps coming back after the fix, you might have a corrupt user profile. Create a new local user account and test. Or check the Event Viewer under Windows Logs → System for error source MRxSmb. That's the SMB redirector. Post the event details in a comment below and I'll help you narrow it down.