Fix 0X0000090D NERR_TooMuchData Truncated Admin Data

Quick Answer

Adjust the NetServerEnum buffer size in the registry or narrow your enumeration query by filtering on a specific domain or server role.

What This Error Actually Means

You're running a remote administration command — like net view, net user /domain, or a Server Manager query — against a Windows machine that holds a lot of data. The problem is Windows has a hard 64 KB limit on the reply size for certain legacy RPC calls (NetServerEnum, NetUserEnum, NetShareEnum). If the server has more than about 200-300 users, shares, or servers, the call returns 0X0000090D instead of the full list. The data gets truncated silently.

I've seen this a lot on domain controllers hosting thousands of user accounts, or file servers with 400+ shares. The worst part? Older tools like net.exe and some MMC snap-ins just show you a partial list and maybe a cryptic error. You might not even notice until you try to manage a user that's cut off.

Fix Steps

1. Identify the call that's failing. Look at the exact command or tool. If it's net view, it's likely NetServerEnum. If it's net user /domain, it's NetUserEnum. This matters because the registry fix is per-API.
2. Open Registry Editor as Administrator (right-click Start -> Run -> regedit).
3. Navigate to the correct key based on the failing API:
   • For user/share enumeration: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
   • For server enumeration (net view): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
4. Create a new DWORD value (32-bit) named MaxBufferSize. If it already exists, double-click it.
5. Set the value to 65536 (decimal) — that's 64 KB, the default. But you want more, so set it to 262144 (256 KB) or 524288 (512 KB). I've used 256 KB on a DC with 5000 users and it worked fine.
6. Click OK, close Regedit.
7. Restart the service:
   • For LanmanServer: run net stop LanmanServer && net start LanmanServer as admin.
   • For LanmanWorkstation: run net stop LanmanWorkstation && net start LanmanWorkstation. This will disconnect any network drives temporarily.
8. Test the command again. If you see the full list without the error, you're set.

Alternative Fixes

Filter your query. If you can't change the registry (locked down environment), break the query into smaller chunks. For net view, specify a domain: net view /domain:yourdomain. For user enumeration, use PowerShell with a filter:

Get-ADUser -Filter * -Properties * | Select-Object -First 300

Use PowerShell directly. The old net commands are limited. Switch to Get-ADUser, Get-SmbShare, or Get-SmbServerConfiguration. These use newer APIs that support pagination (like 1000 records at a time) and don't hit the 64 KB wall.

If the registry fix doesn't help: Check if the remote server has a firewall rule blocking large RPC packets. Some third-party firewalls (like McAfee or Symantec Endpoint Protection) have a setting called "RPC maximum packet size" that defaults to 64 KB. You'll need to raise it on both sides — client and server.

Prevention Tip

Stop using the old net.exe commands for large environments. They're from the NT 4.0 era and weren't designed for today's directory sizes. If you must keep using MMC or legacy scripts, set the MaxBufferSize on every machine that runs remote admin tools — especially your admin workstations. Also, keep an eye on event ID 3200 (Source: NETLOGON) on your DCs; it logs when this error occurs.