How To Setup Environment Variables In Windows
Tancredo Dori
PowerShell can access and manage environment variables in any of the supportedoperating system platforms. The PowerShell environment provider lets you get,add, change, clear, and delete environment variables in the current console.
Environment variables, unlike other types of variables in PowerShell, arealways stored as strings. Also unlike other variables, they're inherited bychild processes, such as local background jobs and the sessions in which modulemembers run. This makes environment variables well suited to storing valuesthat are needed in both parent and child processes.
The Process scope contains the environment variables available in the currentprocess, or PowerShell session. This list of variables is inherited from theparent process and is constructed from the variables in the Machine andUser scopes.
When you change environment variables in PowerShell, the change affects onlythe current session. This behavior resembles the behavior of the set commandin the Windows Command Shell and the setenv command in UNIX-basedenvironments. To change values in the Machine or User scopes, you must use themethods of the System.Environment class.
PowerShell's Environment provider gives you an interface for interactingwith environment variables in a format that resembles a file system drive. Itlets you get, add, change, clear, and delete environment variables and valuesin PowerShell.
You can also copy the environment variable with Copy-Item, set the value ofan environment variable with Set-Item, list environment variables withGet-Item, and delete the environment variable with Remove-Item.
On Windows, you can specify a scope for the SetEnvironmentVariable() methodas the third parameter to set the environment variable in that scope. Themachine and user scopes both persist outside of the current process, allowingyou to save a new or changed environment variable.
In the System Control Panel, you can add or edit existing environment variablesin the User and System (Machine) scopes. Windows writes these values tothe Registry so that they persist across sessions and system restarts.
When running PowerShell as the default (login) shell, you can defineenvironment variables in the global initialization files supported by theoperating system. For example on Linux, you can add environment variables tothe /etc/environment file or create a script that sets environment variablesand put it in the /etc/profile.d folder. On macOS, you can add environmentvariables to the /etc/profile file.
PowerShell features can use environment variables to store user preferences.These variables work like preference variables, but they're inherited by childsessions of the sessions in which they're created. For more information aboutpreference variables, see about_Preference_Variables.
The $env:PSModulePath environment variable contains a list of folderlocations that are searched to find modules and resources. On Windows, thelist of folder locations is separated by the semi-colon (;) character. Onnon-Windows platforms, the colon (:) separates the folder locations in theenvironment variable.
System-wide locations: These folders contain modules that ship withPowerShell. The modules are store in the $PSHOME\Modules location. Also,This is the location where the Windows management modules are installed.
User-installed modules: These are modules installed by the user.Install-Module has a Scope parameter that allows you to specifywhether the module is installed for the current user or for all users. Formore information, see Install-Module.
PowerShell provides control over the file that's used to cache data aboutmodules and their cmdlets. The cache is read at startup while searching for acommand and is written on a background thread sometime after a module isimported.
The default filename for the cache is ModuleAnalysisCache. When you havemultiple instances of PowerShell installed, the filename includes ahexadecimal suffix so that there is a unique filename per installation.
To change the default location of the cache, set the environment variablebefore starting PowerShell. The value should name a full path (includingfilename) that PowerShell has permission to create and write files.
When writing out the module analysis cache, PowerShell checks for modulesthat no longer exist to avoid an unnecessarily large cache. Sometimes thesechecks aren't desirable, in which case you can turn them off by setting thisenvironment variable value to 1.
Setting this environment variable takes effect for subsequent cleanup eventsin the current process. To ensure that cleanup is disabled at startup, youmust set the environment variable before starting PowerShell. See theprevious sections for information about creating persistent environmentvariables.
The $env:PATH environment variable contains a list of folder locations thatthe operating system searches for executable files. On Windows, the list offolder locations is separated by the semi-colon (;) character. Onnon-Windows platforms, the colon (:) separates the folder locations in theenvironment variable.
The $env:PATHEXT variable contains a list of file extensions that Windowsconsiders to be executable files. When a script file with one of the listedextensions is executed from PowerShell, the script runs in the currentconsole or terminal session. If the file extension isn't listed, the scriptruns in a new console session.
To ensure that scripts for another scripting language run in the currentconsole session, add the file extension used by the scripting language. Forexample, to run Python scripts in the current console, add the .pyextension to the environment variable. For Windows to support the .pyextension as an executable file you must register the file extension usingthe ftype and assoc commands of the CMD command shell. PowerShell has nodirect method to register the file handler. For more information, see thedocumentation for the ftype command.
Beginning in PowerShell 7.2, the following environment variables can be used tocontrol the Virtual Terminal features like ANSI escape sequences that colorizeoutput. Support for ANSI escape sequences can be turned off using the TERMor NO_COLOR environment variables.
Remember to replace PATH with the name of the environment variable you want to check. For instance, in the following screenshot, we used the echo %OS% to print the value of the environment variable.
The Windows Registry is the central database in Windows, storing configurations for the OS, software, and hardware. You can easily unset or delete environment variables in Windows by editing the relevant entry in the Registry.
Setting, unsetting, or modifying environment variables with the right approach can effectively tailor your system to specific needs. It involves various methods, from using the GUI to editing the Registry. Whether through a user-friendly interface or more advanced settings, always exercise caution to ensure system stability.
RedSwitches offers the best dedicated server pricing and delivers instant dedicated servers, usually on the same day the order gets approved. Whether you need a dedicated server, a traffic-friendly 10Gbps dedicated server, or a powerful bare metal server, we are your trusted hosting partner.
Setting environment variables allows you to customize system behavior, define path variables for executable files, and configure specific application settings, providing flexibility and control over your Windows environment.
It is possible to set environment variables for the system and the current user simultaneously. System-wide variables impact all users on the Windows computer, whereas user-specific variables only apply to the logged-in user.
You can edit other environment variables by highlighting the variable in the System variables section and clicking Edit. If you need to create a new environment variable, click New, and enter the variable name and value.
Realize that as you install programs, the path is updated with the paths for the newly installed programs. So, if you have erased your path after installing other programs, those programs may be affected.
(Note: Other answers don't specifically address Windows 10 - at least not yet - and they leave off important steps - like how to open the control panel - that changed since previous versions of Windows.)
If by "system environment variables" you refer specifically to system-wide environment variables, then other answers have already covered this. However, if you want to edit both system-wide and user-specific environment variables then most (if not all) of these answers are inapplicable in general case.
If your user has administrator rights, you will be able to edit both sections of that dialog: user-specific environment variables (upper section) and system-wide environment variables (lower section). If you don't have administrator rights, you will only be able to edit the upper section: your own user-specific environment variables.
c80f0f1006