Environment Variables in
Windows 10 & 11

What Are Environment Variables in Windows?

Environment variables are named key-value pairs stored by the operating system that hold configuration information used by programs, scripts, and the shell itself. Think of them as a global settings registry that any running process can read — without hardcoding paths or values directly into code.

For example, the well-known PATH variable tells Windows where to look when you type a command into Command Prompt. Instead of typing C:\Windows\System32\notepad.exe every time, you just type notepad — because C:\Windows\System32 is already listed in PATH.

Environment variables have been a core part of Windows since NT 3.1, and their behavior is essentially identical across Windows 10 and Windows 11. The GUI dialogs look slightly different due to the Windows 11 design refresh, but the underlying registry locations, inheritance rules, and command-line tools work exactly the same way.

Why Environment Variables Matter

Developers, system administrators, and power users rely on environment variables for a wide range of tasks. They allow you to store sensitive data like API keys outside of source code, configure runtime behavior of applications without recompiling, create portable scripts that work on any machine, and define installation paths for tools like Python, Java, Node.js, and Git.

Types and Scope of Environment Variables

Windows recognizes four distinct scopes for environment variables. Understanding scope is critical, because a variable defined at one level may override, be overridden by, or simply be invisible to another level.

Precedence and PATH Merging

For most variables, User variables take precedence over System variables when both exist with the same name. The one important exception is PATH: Windows concatenates the System PATH and User PATH together (System first, then User), so both contribute to the final value seen by any running process.

How to View and Open Environment Variables in Windows 10 and Windows 11 (GUI)

There are several ways to open the Environment Variables dialog. Here are the most reliable methods, all of which work on both Windows 10 and Windows 11:

Method A — Via System Properties

1. Press Win + R, type sysdm.cpl, and press Enter.
2. In the System Properties window, click the Advanced tab.
3. Click the Environment Variables… button at the bottom.
4. The dialog shows two sections: User variables (top) and System variables (bottom).

Method B — Via Settings Search (Windows 11)

1. Press Win + S to open Search.
2. Type environment variables.
3. Click "Edit the system environment variables" or "Edit environment variables for your account" from the results.

Method C — Direct Run Command

1. Press Win + R to open the Run dialog.
2. Type rundll32 sysdm.cpl,EditEnvironmentVariables and press Enter.
3. This opens the Environment Variables dialog directly — no intermediate steps.

How to List Environment Variables Using CMD and PowerShell

The command line gives you fast, scriptable access to environment variable values without opening any GUI dialogs.

Command Prompt (cmd.exe)

CMD — list all variablesset

CMD — print a single variableecho %VARIABLE_NAME%
echo %PATH%
echo %USERNAME%

CMD — filter variables by prefixset APP_

Typing set with no arguments dumps every environment variable available in the current process. Typing set PREFIX (no equals sign) lists every variable whose name starts with that prefix — useful for quickly checking all JAVA_ or PYTHON related variables.

PowerShell

PowerShell — list all variablesGet-ChildItem Env:

PowerShell — read a single variable$env:PATH
$env:USERNAME
$env:APPDATA

PowerShell — filter and formatGet-ChildItem Env: | Where-Object { $_.Name -like "APP_*" }
Get-ChildItem Env: | Sort-Object Name | Format-Table -AutoSize

PowerShell — read persistent User variable from registry[System.Environment]::GetEnvironmentVariable("VARIABLE_NAME", "User")
[System.Environment]::GetEnvironmentVariable("VARIABLE_NAME", "Machine")

How to Create, Edit, and Delete Environment Variables in Windows

Creating a New Variable (GUI)

1. Open the Environment Variables dialog (see Section 03).
2. Under User variables or System variables, click New…
3. Enter the Variable name (e.g., MY_APP_ROOT) and the Variable value (e.g., C:\MyApp).
4. Click OK in all open dialogs to save.

Editing an Existing Variable (GUI)

1. Select the variable you want to change from the list.
2. Click Edit…
3. Modify the value as needed and click OK.

Creating or Updating a Variable via CMD (Current Session Only)

CMD — set a variable for the current sessionset MY_VARIABLE=HelloWorld
set APP_ENV=production

CMD — delete a variable from the current sessionset MY_VARIABLE=

Persisting a Variable via CMD (setx)

CMD — create a persistent User variablesetx MY_VARIABLE "HelloWorld"

CMD — create a persistent System variable (requires Admin)setx MY_VARIABLE "HelloWorld" /M

Managing the PATH Environment Variable in Windows 10 and Windows 11

The PATH variable is by far the most important and most frequently modified environment variable. It is a semicolon-delimited list of directories that Windows searches, in order, when you run an executable without specifying its full path.

Windows 10 and 11 include a dedicated PATH editor that displays each entry on its own line, making it far easier to manage than manually editing the raw semicolon-separated string.

Opening the PATH Editor (Windows 10 / 11)

1. Open Environment Variables (see Section 03).
2. Select Path in either the User or System section.
3. Click Edit… — Windows opens a dedicated multi-line editor instead of a single text field.
4. Use the New, Edit, Delete, Move Up, and Move Down buttons to manage entries.
5. Click OK to save all dialogs.

Adding a Directory to PATH via PowerShell (Persistent)

PowerShell — append to User PATH permanently$current = [System.Environment]::GetEnvironmentVariable("Path", "User")
$newEntry = "C:\MyTool\bin"
[System.Environment]::SetEnvironmentVariable("Path", "$current;$newEntry", "User")

PowerShell — append to System PATH (run as Administrator)$current = [System.Environment]::GetEnvironmentVariable("Path", "Machine")
$newEntry = "C:\MyTool\bin"
[System.Environment]::SetEnvironmentVariable("Path", "$current;$newEntry", "Machine")

Advanced Environment Variable Management with PowerShell

PowerShell's [System.Environment] .NET class and the Env: provider give you full, scriptable control over all scopes of environment variables.

Setting Persistent Variables

PowerShell — set a persistent User variable[System.Environment]::SetEnvironmentVariable("API_KEY", "abc123xyz", "User")

PowerShell — set a persistent System variable (Admin required)[System.Environment]::SetEnvironmentVariable("DB_HOST", "prod-db-01", "Machine")

Deleting Variables

PowerShell — delete a User variable[System.Environment]::SetEnvironmentVariable("API_KEY", $null, "User")

Setting a Temporary Process-Level Variable

PowerShell — set variable for current session only$env:MY_TEMP_VAR = "temporary_value"
Remove-Item Env:MY_TEMP_VAR

Bulk Export and Import

PowerShell — export all User variables to a fileGet-ChildItem Env: | Export-Csv -Path "$HOME\env_backup.csv" -NoTypeInformation

PowerShell — import variables from a .env file (common pattern)Get-Content ".env" | ForEach-Object {
    if ($_ -match "^([^#=]+)=(.*)$") {
        [System.Environment]::SetEnvironmentVariable($matches[1].Trim(), $matches[2].Trim(), "User")
    }
}

Important Built-in Environment Variables in Windows

Windows ships with a rich set of pre-defined environment variables. Knowing them saves time and makes scripts portable across different machines and users.

You can use any of these variables in File Explorer's address bar, the Run dialog (Win+R), batch scripts, and PowerShell by wrapping them in percent signs (%VARIABLE%) or the $env:VARIABLE syntax.

Troubleshooting Environment Variable Issues in Windows 10 / 11

Method Comparison

Common Problems and Solutions

Changes aren't taking effect in open applications. Environment variable changes are only read when a process starts. You must close and reopen the application, terminal, or IDE. Signing out and back in ensures all processes get the updated values.

Command not found after adding to PATH. First verify the path was added correctly with echo %PATH% in a new CMD window. Check for typos, missing backslashes, or extra spaces. Ensure you edited the correct scope (User vs. System).

PATH appears truncated — entries are missing. This is caused by the 1,024-character limit of the old setx command or legacy registry tools. Use the GUI PATH editor or the PowerShell [System.Environment] method, which supports paths up to 32,767 characters (the Windows registry limit).

System variables not visible to the current user. Make sure you're looking in both the User and System sections of the Environment Variables dialog, or use set in CMD, which shows the merged result. If a System variable still doesn't appear, check Group Policy — it can override or hide variables.

An application ignores the environment variable. Some applications cache environment variables at startup and don't re-read them while running. Restart the application. Some also require the variable to be set before the service that launches them starts — in that case, a system reboot may be necessary.

Frequently Asked Questions About Windows Environment Variables