Environment Variables

Graphical editor for managing Windows environment variables with profile support

Overview

Environment Variables provides a modern, user-friendly interface for managing Windows environment variables. It offers advanced features like profile management, bulk editing, and easy variable creation/modification, making it much easier than the built-in Windows environment variable editor.

Changes to environment variables take effect immediately for new processes, but existing applications need to be restarted to see the changes.

Activation

1. Enable Environment Variables

   Open PowerToys Settings and enable Environment Variables

2. Launch Editor

   Open via PowerToys Settings or use the activation shortcut (if configured)

3. Select Scope

   Choose between User or System environment variables

Key Features

Graphical Variable Editor

User Variables

Manage variables for current user only

No admin privileges required

System Variables

Manage system-wide variables

Requires administrator privileges

Variable Profiles

Create and switch between variable sets

Perfect for different development environments

PATH Editor

Dedicated interface for PATH variable

Add, remove, reorder entries easily

Profile Management

Create variable profiles for different scenarios:

// Profile functionality allows switching contexts
// Example: Development, Testing, Production profiles

public class EnvironmentProfile
{
    public string Name { get; set; }
    public Dictionary<string, string> Variables { get; set; }
    public bool IsEnabled { get; set; }
}

Use cases:

• Development vs Production configurations
• Different project environments
• Testing with alternate tool versions
• Multiple SDK versions

PATH Variable Management

Enhanced PATH editing:

• Visual List: See all PATH entries in a list
• Add Entry: Click button to add new path
• Remove Entry: Delete unused paths
• Reorder: Drag entries to change priority
• Validate: Check if paths exist
• Duplicate Detection: Highlight duplicate entries

Bulk Operations

Import

Import variables from file:

# variables.env
API_KEY=your_key_here
DATABASE_URL=postgres://localhost/mydb
DEBUG_MODE=true

Load multiple variables at once

Export

Export current variables:

• Save as .env file
• Backup before changes
• Share configurations
• Version control friendly

Search

Find variables quickly:

• Filter by name
• Search in values
• Highlight matches

Variable Validation

Built-in validation features:

// PATH validation example
public bool ValidatePathEntry(string path)
{
    // Check if path exists
    if (!Directory.Exists(path) && !File.Exists(path))
    {
        return false; // Mark as invalid
    }
    
    // Check for duplicates
    if (ExistingPaths.Contains(path, StringComparer.OrdinalIgnoreCase))
    {
        return false; // Duplicate found
    }
    
    return true;
}

Visual indicators:

• ✓ Green: Valid path
• ⚠ Yellow: Warning (duplicate, spacing issues)
• ✗ Red: Invalid (path doesn’t exist)

Configuration

Settings Location

Environment variables are stored by Windows in:

• User: HKEY_CURRENT_USER\Environment
• System: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

Profile configurations stored in:

%LOCALAPPDATA%\Microsoft\PowerToys\EnvironmentVariables\

Variable Scopes

User Variables · scope

Variables specific to the current user account

• No admin rights needed
• Stored in user registry hive
• Affect only current user’s processes

System Variables · scope

Variables shared across all users

• Requires administrator privileges
• Stored in system registry
• Affect all users and system processes

Common Variables

PATH

Directories searched for executable files

Example:

C:\Program Files\Git\cmd
C:\Python312
C:\Users\YourName\AppData\Local\Programs\Python\Python312\Scripts

TEMP / TMP

Temporary file directories

Default:

TEMP=%USERPROFILE%\AppData\Local\Temp
TMP=%USERPROFILE%\AppData\Local\Temp

HOME / USERPROFILE

User home directory location

System set:

USERPROFILE=C:\Users\YourName
HOME=%USERPROFILE%

Use Cases

Development Environment Setup

1. Add Development Tools to PATH

   1. Open Environment Variables editor
   2. Navigate to PATH variable
   3. Add tool directories:
      - C:\Program Files\nodejs
      - C:\Go\bin
      - C:\Program Files\Git\cmd
   
2. Set SDK Variables

   Create variables for SDK locations:

   JAVA_HOME=C:\Program Files\Java\jdk-17
   ANDROID_HOME=C:\Android\sdk
   GOPATH=C:\Users\YourName\go
   
3. Create Development Profile

   Save configuration as “Development” profile for easy switching

Multiple Project Configurations

Project A Profile

PROJECT_ROOT=C:\Projects\ProjectA
API_ENDPOINT=https://api.projecta.dev
DATABASE_URL=postgres://localhost/projecta
NODE_ENV=development

Switch between projects by changing active profile.

CI/CD Configuration

Local Testing

Match CI environment variables locally:

CI=true
BUILD_NUMBER=local
GIT_BRANCH=feature/new-feature

Test build scripts in local environment

Secrets Management

Set API keys and tokens:

API_KEY=your_development_key
AWS_ACCESS_KEY_ID=your_key
AWS_SECRET_ACCESS_KEY=your_secret

⚠ Security Note: Use environment variables for non-production secrets only

PATH Cleanup

1. Review Current PATH

   Open PATH editor and review all entries

2. Identify Issues

   Look for:

   • Invalid paths (red indicators)
   • Duplicate entries (yellow warnings)
   • Unused applications
3. Clean Up

   • Remove invalid paths
   • Delete duplicates
   • Uninstall unused applications
   • Reorder by priority
4. Test

   Open new terminal and verify commands work

Tool Version Management

Node.js Versions

Switch between Node versions:

# Node 18 Profile
PATH=C:\Program Files\nodejs-18\;...

# Node 20 Profile
PATH=C:\Program Files\nodejs-20\;...

Python Versions

Manage multiple Python installations:

# Python 3.11
PATH=C:\Python311\;C:\Python311\Scripts;...

# Python 3.12
PATH=C:\Python312\;C:\Python312\Scripts;...

Technical Details

Architecture

Registry Integration

Direct Windows registry manipulation:

// Registry access for environment variables
using Microsoft.Win32;

public static void SetUserVariable(string name, string value)
{
    using var key = Registry.CurrentUser.OpenSubKey("Environment", true);
    key?.SetValue(name, value, RegistryValueKind.String);
    
    // Broadcast change to system
    SendMessageTimeout(
        HWND_BROADCAST,
        WM_SETTINGCHANGE,
        IntPtr.Zero,
        "Environment",
        SMTO_ABORTIFHUNG,
        5000,
        out _
    );
}

Source reference: src/modules/EnvironmentVariables/EnvironmentVariables/Helpers/NativeMethods.cs

Change Broadcasting

Changes are broadcast to all running applications:

// WM_SETTINGCHANGE notification
SendMessageTimeout(
    HWND_BROADCAST,                    // All top-level windows
    WM_SETTINGCHANGE,                  // Setting changed message
    0,                                 // wParam (unused)
    (LPARAM)"Environment",            // lParam (what changed)
    SMTO_ABORTIFHUNG,                  // Flags
    5000,                              // Timeout (5 seconds)
    NULL                               // Result (not needed)
);

Applications that listen for WM_SETTINGCHANGE will reload environment variables.

Profile Format

Profiles stored as JSON:

{
  "name": "Development",
  "enabled": true,
  "variables": [
    {
      "name": "NODE_ENV",
      "value": "development",
      "type": "User"
    },
    {
      "name": "API_ENDPOINT",
      "value": "https://localhost:3000",
      "type": "User"
    }
  ]
}

Troubleshooting

Changes not taking effect

Environment variables only affect new processes:

1. Close and reopen terminal/command prompt
2. Restart application that needs the variables
3. Log off and log back in (for some system changes)
4. Restart computer (for system-wide changes)

Verify:

# In new PowerShell window
$env:YOUR_VARIABLE_NAME

Cannot edit system variables

Requires administrator privileges:

1. Close PowerToys
2. Right-click PowerToys icon
3. Select “Run as administrator”
4. Open Environment Variables editor

Alternative: Use built-in Windows editor (requires admin)

PATH too long error

Windows has a PATH length limit (~2048 characters):

Solutions:

1. Remove unused paths
2. Use shorter directory names
3. Use symbolic links for long paths
4. Set individual tool environment variables instead of adding all to PATH

Check current length:

$env:PATH.Length

Variable not found in application

Check scope and process:

1. Verify variable exists in correct scope (User vs System)
2. Ensure application restarted after variable set
3. Check if application runs as different user
4. Verify no typos in variable name (case-insensitive but must match)

Debug:

# List all environment variables
Get-ChildItem Env:

# Check specific variable
[Environment]::GetEnvironmentVariable("VAR_NAME", "User")
[Environment]::GetEnvironmentVariable("VAR_NAME", "Machine")

See Also

• PowerToys Run - Quick environment variable access
• Command Not Found - Suggests missing PATH entries
• Windows Terminal - Modern terminal with environment support