Fix ERROR_META_EXPANSION_TOO_LONG (0x000000D0)

You'll see error code 0x000000D0 (ERROR_META_EXPANSION_TOO_LONG) when Windows tries to expand an environment variable—like %PATH% or %USERPROFILE%—and the result exceeds 32,767 characters (32K). This usually hits during command prompt launches, batch file execution, or when a program reads the system environment. Common triggers: a developer with too many tool paths in PATH (Node, Python, Git, VS Code, etc.), or a registry value that recursively references itself through %VAR% patterns.

Why Windows throws this

What's actually happening here is that Windows' internal string buffer for environment variable expansion is capped at 32,767 characters. When the expansion engine processes a variable like %PATH%, it replaces %VAR% references inside it with their values. If any of those referenced variables themselves contain %VAR% references, the engine iterates until no more substitutions are possible. If the final string exceeds 32K, it bails with 0x000000D0.

The most frequent culprit is the PATH environment variable. Modern development tools—Node.js, Python, Git, Rust, WSL, Docker, MinGW, Cygwin—each append their own directories. Over years of installs and uninstalls, orphaned entries pile up. One wrong %PATH% append in a batch file that itself contains %PATH% can create a feedback loop that doubles the length each time it expands.

The fix: trim or redirect the variable

You have two paths here. The direct fix is to shorten the offending variable. The faster workaround is to avoid expanding it at all by using delayed expansion or a temporary variable.

Step 1: Identify the offender

Open an elevated Command Prompt (Run as Administrator). Run this to see each environment variable's length:

set | findstr /r "^[A-Z]" | sort

Look for lines longer than 30,000 characters. PATH is the usual suspect, but PSModulePath or INCLUDE (common with Visual Studio) can also trip this.

Step 2: Check the registry for recursive references

Open regedit and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

Also check:

HKEY_CURRENT_USER\Environment

Look for any value that contains something like %PATH% inside itself. That's a recursive bomb. A bad line like C:\OldTool;%PATH% in a user environment variable will expand to the entire system PATH plus itself, doubling the length. Remove it.

Step 3: Shorten PATH (the real fix)

Back up your PATH first. In a command prompt:

reg export "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" C:\env_backup.reg

Now open System Properties → Environment Variables. Under System variables, select Path and click Edit.

Remove any entries that:

Point to uninstalled software (e.g., an old Java SDK, outdated Git)
Are duplicate directories (e.g., C:\Windows\system32 appearing twice)
Use relative paths like .; or ..\bin
Are long paths you can consolidate—for example, replace C:\Python312\Scripts and C:\Python312\ with a single C:\Python312\Scripts if Python's installer already adds it.

If you use many tools, consolidate them into a single directory and add that one entry. For instance, create C:\Scripts and put shortcuts or symlinks there.

Step 4: Use delayed expansion in batch files (if you can't shorten it)

If the error only happens inside a batch file, you can bypass it by using delayed expansion—this prevents the %VAR% from expanding during the parsing phase:

setlocal enabledelayedexpansion
set "MYVAR=!PATH!"
echo !MYVAR!

The reason this works is that delayed expansion happens after the normal expansion phase, so the 32K limit on the initial parse is avoided. But this only masks the problem—the underlying variable is still too long for most system APIs.

Step 5: Reset PATH from a minimal base

If the PATH is totally trashed, reset it to Windows defaults. In an admin command prompt:

setx PATH "%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\" /M

Then add back your essential tool paths one by one. Reboot after.

Still failing? Check these three things

User vs system PATH — the error can come from either scope. Check both in registry (steps above). Sometimes the user PATH is fine but the system PATH is bloated, or vice versa.
Non-PATH variables — the error isn't exclusive to PATH. PSModulePath in PowerShell can grow huge. TEMP or TMP can hit the limit if they contain %USERPROFILE% nested inside a long username. Check set output for any variable over 30K.
Third-party software — antivirus or MDM software sometimes injects their own %VAR% references into environment variables. Temporarily disable or check logs for any policy that appends to PATH.

The root cause is always an expansion result that's too long. Fix the variable's content, not the error handler. Once you shorten it, the error disappears permanently.