Настройка переменных среды Windows может помочь сократить время, необходимое для набора команд в командной строке или, если вы часто пишете скрипты для собственных задач, сделать их более читаемыми. В большинстве случаев обычные пользователи добавляют записи в системную переменную среды PATH, хотя бывают и другие задачи.
В этой пошаговой инструкции базовая информация о том, как открыть переменные среды Windows 11 и Windows 10, создать или отредактировать их.
Что такое переменные среды
Переменные среды в Windows — записи о расположении системных папок, свойствах системы и другие, которые доступны для любой программы или скрипта.
Одна из наиболее часто используемых переменных среды — PATH, указывающая на папки, в которых выполняется поиск файлов, вызываемых в командной строке, терминале Windows, файле bat или из других источников. В качестве примера её назначения:
- Если вы откроете командную строку (или диалоговое окно «Выполнить»), введёте regedit и нажмете Enter — вы сможете запустить редактор реестра, не указывая полный путь к файлу regedit.exe, поскольку путь C:\Windows добавлен в переменную среды Path.
- Если же тем же образом в командной строке написать имя программы, путь к которой не добавлен в Path (chrome.exe, adb.exe, pip и другие), вы получите сообщение «Не является внутренней или внешней командой, исполняемой программой или пакетным файлом».
Если предположить, что вы часто используете команды adb.exe (например, для установки приложений Android в Windows 11), pip install (для установки пакетов Python) или любые другие то для того, чтобы не писать каждый раз полный путь к этим файлам, имеет смысл добавить эти пути в переменные среды.
Также вы можете добавлять и иные переменные среды (не обязательно содержащие пути), а в дальнейшем получать и использовать их значения в сценариях BAT (командной строки) или PowerShell. Пример получения и отображения значения системной переменной PATH для обоих случаев:
echo %PATH% echo $Env:PATH
Получить список всех переменных среды в командной строке и PowerShell соответственно можно следующими командами:
set ls env:
Редактирование переменных среды Windows 11/10
Прежде чем приступать, учтите: изменение системных переменных среды по умолчанию может привести к проблемам в работе системы, не удаляйте уже имеющиеся переменные среды. Возможно, имеет смысл создать точку восстановления системы, если вы не уверены в своих действиях.
- Чтобы открыть переменные среды Windows вы можете использовать поиск в панели задач (начните вводить «Переменных» и откройте пункт «Изменение системных переменных среды») или нажать клавиши Win+R на клавиатуре, ввести sysdm.cpl и нажать Enter.
- На вкладке «Дополнительно» нажмите кнопку «Переменные среды…»
- В разделе «Переменные среды пользователя» (если требуется изменение только для текущего пользователя) или «Системные переменные» выберите переменную, которую нужно изменить и нажмите «Изменить» (обычно требуется именно это), либо, если необходимо создать новую переменную — нажмите кнопку «Создать». В моем примере — добавляем свои пути в системную переменную Path (выбираем эту переменную и нажимаем «Изменить»).
- Для добавления нового значения (пути) в системную переменную в следующем окне можно нажать кнопку «Создать», либо просто дважды кликнуть по первой пустой строке, затем — ввести нужный путь к папке, содержащей нужные нам исполняемые файлы.
- Также вы можете использовать кнопку «Изменить текст», в этом случае окно изменения системной переменной откроется в ином виде: имя переменной, а ниже — её значение. В случае указания путей значение будет представлять собой все пути, хранящиеся в переменной, разделенные знаком «точка с запятой».
- При создании новой переменной среды окно будет тем же, что и в 5-м шаге: необходимо будет указать имя системной переменной в верхнем поле, а её значение — в нижнем.
После создания или изменения переменной среды и сохранения сделанных настроек, переменная или обновленные значения сразу становятся доступны для текущего пользователя или в системе в целом в зависимости от того, какие именно переменные редактировались или создавались. Также есть методы добавления переменных среды в командной строке или PowerShell, подробнее в статье: Как добавить путь в переменную среды PATH
- Environment variables are global system variables that are available to all users and programs running on the system. They store system-wide and user-specific values.
- You can view and manage environment variables from Settings > System > About > Advanced system settings > Environment Variables.
- To view all environment variables in Command Prompt, run “set“, or run “Get-ChildItem Env: | Sort Name” in PowerShell.
Most operating systems have environment variables, including Windows, MacOS, and Linux. Just like in a programming language, environment variables can be called upon to use their values that can store a number, a location, or any other value defined.
The environment variables were introduced with Windows 95, and have since gone through many iterations with every Windows release. These can be used to access certain directories quickly, rather than enter the complete paths.
Environment variables can be edited and manipulated, or you can even add new ones. In this article, we discuss the many different Windows environment variables, what they do, and all that you need to know about them.
This guide applies to all versions of Windows, including Windows XP, Windows Vista, Windows 7, Windows 8, Windows 10, and Windows 11.
Table of Contents
What are Environment Variables
Environment variables are variables that can be used across your system. Just like in programming, variables contain a value that can be changed or called when needed. Environment variables are the same but can be used across the entire scope.
You can use environment variables in Windows to store frequently used locations, so you don’t have to type them out each time, or temporarily change the way a program behaves. Environment variables are normally used in scripts or programs/apps.
For example, you can create an environment variable called TEMP that points to a different folder than the default TEMP folder Windows uses. Then, when a program needs to store temporary files, it will use the TEMP folder you specified instead of the default one.
Tip: If you are using Linux or MacOS, the environment variables can be set in the .bashrc or .profile files.
There are 3 types/scopes of environment variables in the hierarchy:
- Machine
- User
- Process
At the top, you have machine or system environment variables. These can be used across the entire system, and used for global variables, meaning changing the system variables will affect all users of the computer. Then there are user environment variables. This is defined individually for each user account and is limited to that account only and only affects the user currently logged in.
Then you have the process variables which are only limited to the processes and cannot be edited or created. The end-user does not see or have anything to do with the process variables.
Furthermore, each of these scopes has different types of variables, which are as follows:
- PATH: This variable stores a list of directories where your OS searches for executable programs. It’s crucial to run commands and launch applications from the command prompt and Run dialog.
- JAVA_HOME: This variable points to the installation directory of your Java Development Kit (JDK), a necessity for Java development and running Java applications.
- CLASSPATH: This variable tells your Java Virtual Machine (JVM) where to find user-defined classes and libraries, ensuring your Java code can access the necessary resources.
Please note that environment variables in Windows are not case-sensitive and are only written in upper case to distinguish between the variable name and the value.
Additionally, if there is an environment variable of the same name in more than one scope, then the variable in the lower scope will supersede the value of the one higher in the hierarchy.
For example, the common environment variable “TEMP” is available in all scopes with the following values:
- Machine: C:\Windows\Temp
- User: C:\Users\[Username]\AppData\Local\Temp
- Process: C:\Users\[Username]\AppData\Local\Temp
Hence, using the “Temp” variable will call for the value set for the process scope. If there is no variable by the name “Temp” in this scope, then it will use the value for the user scope, and so on.
You can use these variables to access a path quickly. For example, typing in “%HOMEPATH%” in the Run Command box will open the user’s home directory.
You can also edit this variable to include a sub-directory of the path, like opening the user account’s desktop by typing in “%HOMEPATH%\Desktop%”.
What are Environment Variable Scopes
As we mentioned earlier, there are 3 scopes for environment variables: Machine/System, user, and process. These scopes define the limitations of the variables and where they can be used.
Below you’ll find a more detailed explanation of the different types of environment variable scopes.
System/Machine
The environment variables defined inside this scope can be used by anyone on the system. These types of variables are associated with the running instance of Windows. Any user account can read these, set, change, or delete them, provided they have administrative rights.
User
The environment variables defined within this scope are only user-specific and might be different for each user account. This is associated with the current user. User variables overwrite machine-scoped variables with the same name.
Process
Environment variables in this scope are a combination of machine and user scopes in addition to some dynamically created variables by the Windows OS.
Now that you know what environment variables are and how they work, let us see which variables are available in a Windows OS.
Here is a list of the process variables which are available in this scope:
- ALLUSERSPROFILE
- APPDATA
- COMPUTERNAME
- HOMEDRIVE
- HOMEPATH
- LOCALAPPDATA
- LOGONSERVER
- PROMPT
- PUBLIC
- SESSION
- SystemDrive
- SystemRoot
- USERDNSDOMAIN
- USERDOMAIN
- USERDOMAIN_ROAMINGPROFILE
- USERNAME
- USERPROFILE
Complete list of Windows Environment Variables
Below is a complete list of the environment variables that you will find inside the Windows operating system by default:
| Variable Name | Value |
|---|---|
| %ALLUSERSPROFILE% | C:\ProgramData |
| %APPDATA% | C:\Users\{username}\AppData\Roaming |
| %COMMONPROGRAMFILES% | C:\Program Files\Common Files |
| %COMMONPROGRAMFILES(x86)% | C:\Program Files (x86)\Common Files |
| %CommonProgramW6432% | C:\Program Files\Common Files |
| %COMSPEC% | C:\Windows\System32\cmd.exe |
| %HOMEDRIVE% | C:\ |
| %HOMEPATH% | C:\Users\{username} |
| %LOCALAPPDATA% | C:\Users\{username}\AppData\Local |
| %LOGONSERVER% | \\{domain_logon_server} |
| %PATH% | C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem |
| %PathExt% | .com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc |
| %PROGRAMDATA% | C:\ProgramData |
| %PROGRAMFILES% | C:\Program Files |
| %ProgramW6432% | C:\Program Files |
| %PROGRAMFILES(X86)% | C:\Program Files (x86) |
| %PROMPT% | $P$G |
| %SystemDrive% | C: |
| %SystemRoot% | C:\Windows |
| %TEMP% | C:\Users\{username}\AppData\Local\Temp |
| %TMP% | C:\Users\{username}\AppData\Local\Temp |
| %USERDOMAIN% | Userdomain associated with the current user. |
| %USERDOMAIN_ROAMINGPROFILE% | Userdomain associated with roaming profile. |
| %USERNAME% | {username} |
| %USERPROFILE% | C:\Users\{username} |
| %WINDIR% | C:\Windows |
| %PUBLIC% | C:\Users\Public |
| %PSModulePath% | %SystemRoot%\system32\WindowsPowerShell\v1.0\Modules\ |
| %OneDrive% | C:\Users\{username}\OneDrive |
| %DriverData% | C:\Windows\System32\Drivers\DriverData |
| %CD% | Outputs current directory path. (Command Prompt.) |
| %CMDCMDLINE% | Outputs command line used to launch current Command Prompt session. (Command Prompt.) |
| %CMDEXTVERSION% | Outputs the number of current command processor extensions. (Command Prompt.) |
| %COMPUTERNAME% | Outputs the system name. |
| %DATE% | Outputs current date. (Command Prompt.) |
| %TIME% | Outputs time. (Command Prompt.) |
| %ERRORLEVEL% | Outputs the number of defining exit status of the previous command. (Command Prompt.) |
| %PROCESSOR_IDENTIFIER% | Outputs processor identifier. |
| %PROCESSOR_LEVEL% | Outputs processor level. |
| %PROCESSOR_REVISION% | Outputs processor revision. |
| %NUMBER_OF_PROCESSORS% | Outputs the number of physical and virtual cores. |
| %RANDOM% | Outputs random numbers from 0 through 32767. |
| %OS% | Windows_NT |
Where are Environment Variables Stored
The environment variables are stored in 2 places in the Windows Registry; one for the system and one for individual users.
The system environment variables are stored at the following location:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
The user environment variables are stored at the following location:
Computer\HKEY_CURRENT_USER\Environment
You can also export the “Environment” key using its context menu to import the environment variables on another Windows computer, or vice versa.
Now that you know where they are stored, you may have a look at them. However, it is strongly recommended that you do not add or change environment variables using the Windows Registry. This is because any running processes will not see variable changes in the registry. Processes only see the registry variables and values that are present when the process was started unless Windows notifies them that there has been a change.
If you want to add or make changes to the environment variables, keep reading this post.
How to View/Access Windows Environment Variables
You can view and access Windows environment variables in multiple ways. Pick the method you like best from below.
View Environment Variables from Settings App
Follow these steps to access the environment variables using the Settings app:
-
Navigate to the following:
Settings app >> System >> About
-
Now click Device Specifications to expand it.
Expand Device Specifications -
Now click Advanced system settings under Related links.
Open Advanced system settings -
From the pop-up System Properties window, switch to the Advanced tab, and then click Environment Variables.
Open Environment Variables -
The Environment Variables window will now open. Here, you can see the user variables at the top and the system/machine variables at the bottom.
Environment Variables window
View Environment Variables from Command Line
If you want to access the environment variables using the Command Line, here is how:
-
Run the following cmdlet in either the Command Prompt, Windows PowerShell, or the Run Command box to open the System Properties applet.
sysdm.cplOpen System Properties applet -
From the pop-up System Properties window, switch to the Advanced tab, and then click Environment Variables.
Open Environment Variables -
The Environment Variables window will now open. Here, you can see the user variables at the top and the system/machine variables at the bottom.
Environment Variables window
List Environment Variables in PowerShell
Alternative to the methods discussed above, you can also list the environment variables in PowerShell using a simple cmdlet.
Run the following command in an elevated PowerShell instance and it will display all of the environment variables on your computer:
Get-ChildItem Env: | Sort Name
List Environment Variables in Command Prompt
You can also view the list of environment variables in the Command Prompt with the following basic command:
setThis command will list down all environment variables on your computer.
View Value for Environment Variable using Command Prompt
If you access the environment variable using any of the given methods above, then you can see their values as well. Another method to view the value of an environment variable is through the Command Prompt.
Simply type in “echo” followed by the environment variable name in the “%” sign in an elevated Command Prompt and you will then see its value(s), as in this image:
How to Create and Set/Edit Environment Variables in Windows
From System Properties
You may need to create a new environment variable or modify an existing one in the Windows OS to be used for programming purposes or to use Java. Whatever the reason, follow these steps to create a new environment variable using the GUI:
-
Access the Environment Variables window using one of the given methods above. In this window, click New either under user variables or system variables, depending on which scope you want to create the variable in.
Create a new variable -
In the popup window, set a name for the variable and then enter its value. Once done, click OK.
Enter details for variable -
Back in the Environment Variable window, click OK again to save the changes.
The variable will now be created, and you can now use it in your code, or access the folder by concatenating a “%” sign on the front and back of it.
From Command Prompt
You can also create a new environment variable using the Command Prompt, and define its value(s). You can create both a temporary variable that only lasts until the instance is closed or the system is rebooted, or a permanent variable that will always remain unless explicitly deleted.
Once you create the variable, you can access it immediately. There’s no need to restart the computer for the changes to take effect.
Note: These methods create a user environment variable and not a system variable.
Temporary Environment Variable
Use the following cmdlet in an elevated Command Prompt to create a temporary variable while replacing [VariableName] with a custom name for the variable, and [Value] with the value that you want to define for the variable, which can be a string or a number.
Set [VariableName]=[Value]
Permanent Environment Variable
If you want to create a permanent environment variable, then use this cmdlet instead:
Setx [VariableName] "[Value]"
Using third-party software
You can also manage environment variables using third-party tools and utilities. Here are a few that can be used with great convenience.
Rapid Environment Editor
Rapid Environment Editor (REE) provides a very user-friendly way of editing environment variables. It lists the system variables in the left pane and the user variables in the right pane, while the bottom pane will give details about the selected variable.
The best thing about REE is that it will also highlight a variable if its value has some errors. You can also back up the environment variable configuration from the file menu. Rapid Environment Editor comes with an installable program, as well as a portable one. If you are using the portable REE in Windows 7 or Windows 8, you will need to run the executable in the administrative mode so that it can make changes to the system configuration.
PathMan
PathMan is a very simple portable program, which will only edit the PATH environment variable. Since PATH is a variable that needs to be edited frequently, PathMan can help edit the Path environment variable directly from the USB drive.
Eveditor
Eveditor comes with an elegant and very user-friendly graphical user interface that resembles the look and feel of Windows Explorer. You can choose from a user variable or system variable from the pane on the left. The selection will be displayed on the right-hand pane. The details of the selected environment variable will be displayed in the bottom pane.
You can edit the selected variable, and upon clicking the “Set” button, the variable will be saved. Please note that you will need to run Eveditor with administrative privileges to save the environment variables successfully.
How to Delete an Environment Variable in Windows
If you no longer need an environment variable, you can simply delete it.
One concern while deleting a variable is whether it is safe. The answer is both yes and no. Nothing happens when an environment variable is deleted, except that the apps, program, and other elements no longer know where to look for an item when it is called upon. Other than that, it has no impact on the system’s performance.
That said, we still think that you should be extremely careful when deleting a variable. If you still wish to continue to remove an environment variable, follow these steps:
Note: You should create a system restore point before proceeding so that your system can be reverted to previous settings in case things do not go as planned.
-
Access the Environment Variables window using one of the given methods above.
-
In the Environment Variables window, click on the variable that you want to remove and click Delete under the same section.
Delete environment variable -
Now click OK to save the changes.
The variable will now be removed from your PC.
Alternatively, you can use the Command Prompt to unset an environment variable. Simply use the set command discussed above to empty the string. Here is an example:
set [VariableName]=Leaving the command blank after “=” will set the string to empty. The environment variable will exist but will be of no use.
How to Edit an Environment Variable in Windows
You can also edit an environment variable. Its name can be changed as well as its value. However, it is recommended that you do not edit the default Windows environment variables, or else the apps and programs using those variables might no longer work.
That said, the “PATH” variable stores several paths to directories for executable files. You can safely add more directory paths to this variable without causing an issue.
Follow these steps to edit an environment variable in Windows:
-
Access the Environment Variables window using one of the given methods above.
-
Here, click on the variable that you want to edit and then click Edit under the same section.
Edit an environment variable -
From the Edit popup, make the changes you want to the name or the value of the variable, and then click OK.
Edit variable details -
Back on the Environment Variables window, click OK to save the changes.
What is the PATH Environment Variable
Earlier in this post, we mentioned the PATH environment variable. The PATH variable is perhaps the most-used variable out of the lot.
The PATH variable stores multiple entries (or values). Those values specify the directories in which the executable programs are located on the system so that they can be started without knowing and typing the whole path to the file on the command line.
How to Manage Environment Variables using PowerShell Env
The PowerShell has a virtual drive known as the “PS Drive.” It is a data store location that you can access like a file system drive in Windows PowerShell. Using this drive, we can manage different aspects of the environment variables. A PS drive allows you to treat environment variables as if they are a file system through the Env: drive.
Below you’ll find the guidelines to perform different variables-related tasks using the Env: drive.
To begin, you must first switch to the ENv: drive. To do that, type in the following in the PowerShell window.
cd Env:
To get the complete list of environment variables and their values, use the following cmdlet:
Get-Item -Path Env:
You can also create new environment variables from the Env: drive by using this cmdlet. Replace [VarableName] with a name for the variable, and [Value] with the value you want to set for the variable.
NewItem -Path Env:\[VariableName] -Value [Value]
To set the value of an existing variable, use this cmdlet:
Set-Item -Path Env:[VariableName] -Value "[Value]"
To delete an environment variable from the Env: drive, use this cmdlet:
Remove-Item -Path Env:\[VariableName]
Frequently Asked Questions (FAQs)
Is it safe to delete an environment variable?
The answer is both yes and no. Although deleting a default OS environment variable will have no performance repercussions, any apps or programs using that variable will no longer be able to look for the executables in the specified directories, or you won’t be able to use the shortcuts anywhere in the system to run an executable.
What does the PATH environment variable do?
The PATH environment variable can store multiple path values for different executable files. When an executable file is called, like “CMD,” the PATH variable tells it where to look for the cmd.exe file.
System and User Environment Variables have always been a complex topic of discussion for day-to-day Windows OS users. What do they do? A tutorial on the internet said to add a PATH variable, but what is it? Where do I find these variables? All of these questions will be answered shortly in this post. We’ve tried to give you a high-level overview of what System and User Environment Variables are and how you can utilize them.
In this post, we will discuss Environment Variables, System and User Environment Variables and how to add and modify them. Then, we will move on to Dynamic System Variables and see how to use them in the command prompt.
What is an Environment Variable In Windows OS
Environment Variable is formed up of two separate words, ‘Environment’ and ‘Variable’. Let’s discuss ‘variable’ first. It means that the entity can store a value and vary from computer to computer. Windows provides an ‘Environment’ for applications to execute and perform operations, and that is what makes the first word. Combining both, Environment Variables are those dynamic objects that store the values provided by the environment. Now, the environment provides values that help other programs in obtaining some crucial information about the system. There is an environment variable called ‘windir’ that corresponds to the directory where Windows is installed. To see this in action, open up an explorer window and type in ‘%windir%’ in the address bar. The Windows installation folder will open up.
Very similarly, you can make reference to the Windows directory using ‘windir’ variable in other programs and scripts. There are numerous other variables that can be accessed, ‘TEMP’ or ‘TMP’ is the variable that points to the directory where all temporary files are stored. The most popular ‘Path’ variable is the one that points to the directories containing executable files. So that you can run a program from the Command Prompt in any other directory. We’ve explained Path later on in this post. All these variables come in handy when you are developing something or using the shell a lot.
Very similar to how the Registry works on Windows, we have System and User Environment Variables. The system variables are system-wide accepted and do not vary from user to user. Whereas User Environments are configured differently from user to user. You can add your variables under the user so that other users are not affected by them.
Just for your information, since we are discussing the topic in depth. System Variables are evaluated before User Variables. So if there are some user variables with the same name as system variables, then user variables will be considered. The Path variable is generated in a different way. The effective Path will be the User Path variable appended to the System Path variable. So, the order of entries will be system entries followed by user entries.
Read: How to use Environment Variable Editor in PowerToys?
How to add & modify Environment Variables
A small warning before we go deeper. Create a system restore point, and try not to tamper with the existing settings configured for your system. Until you are very sure about your actions. To open the ‘Environment Variables’ Window, follow these steps:
- Right-click ‘This PC’ icon and select ‘Properties’.
- Now in this window, select ‘Advanced System Settings’ from the left part.
- Hit the last button saying ‘Environment Variables’ to open our destined window.
Once you’ve opened this up, you will be able to view User and System variables separately. The variable name is in the first column and its value in the second. The corresponding buttons below the table let you ‘Add’, ‘Edit’ and ‘Delete’ these variables.
Read: Environment Variables not working in Windows 11
Using the Path variable
Path is the most used environment variable. As I mentioned, it points to directories that contain executable files. Once you’ve correctly set up your Path variable, you can use these executables from anywhere in the system. Let’s try to understand this with an example. Open up the environment variables window and look for ‘Path’ in system variables.
Click on ‘Edit’ and then click on ‘New’ without playing around with other controls right now. Now click browse and select a folder that has your desired executable file. Click ‘Ok’ and save everything. I added ‘Visual Studio Code’ executable to the path.
Now to run your application, open up Command Prompt and type in the name of the executable file that was in the folder. You can provide additional arguments if the program supports it. The program will run from the command prompt without actually being in the directory from where you executed the command. That is the beauty of the Path variable.
Read: How to add or edit a PATH Environment Variable in Windows.
List of all Environment Variables
Open the command prompt and type ‘SET’ and hit Enter. The entire list of variables with their current values will be displayed, and you can refer to it to make changes to your computer.
Read: How to see Names and Values of Environment Variables in Windows
Dynamic Environment Variables
Unlike conventional variables, dynamic environment variables are provided by the CMD and not by the system. You cannot change the values of these variables and they expand to various discrete values whenever queried. We usually use these variables for batch processing and these are not stored in the environment. Even the ‘SET’ command will not reveal these variables. Some of the dynamic environment variables are listed below.
Read: How to add Environment Variables to Context Menu.
List of environment variables in Windows 11/10
%APPDATA% – C:\Users\<username>\AppData\Roaming
%ALLUSERSPROFILE% – C:\ProgramData
%CD% – Typing in this command will give you the current directory you are working in.
%COMMONPROGRAMFILES% – C:\Program Files\Common Files
%COMMONPROGRAMFILES(x86)% – C:\Program Files (x86)\Common Files
%COMMONPRGRAMW6432% – C:\Program Files\Common Files
%CMDEXTVERSION% – This variable expands to the version of the command-line extensions.
%COMSPEC% – C:\Windows\System32\cmd.exe
%DATE%: – This variable will give you the current date according to date format preferences.
%ERRORLEVEL% – Determines the error level set by last executing command.
%HOMEDRIVE% – C:\
%HOMEPATH% -C:\Users\<username>
%LOCALAPPDATA% – C:\Users\<username>\AppData\Local
%LOGONSERVER% – \\<domain_logon_server>
%PATH% – C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem
%PATHEXT% – .com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc
%PROGRAMDATA% – C:\ProgramData
%PROGRAMFILES% – C:\Program Files
%PROGRAMW6432% – C:\Program Files
%PROGRAMFILES(X86)% – C:\Program Files (x86)
%PROMPT% – $P$G
%SYSTEMDRIVE% – C:
%SYSTEMROOT% – C:\Windows
%TIME% – Similarly, it gives you current time according to the time format preferences.
%TMP% – C:\Users\<username>\AppData\Local\Temp
%TEMP% – C:\Users\<username>\AppData\Local\Temp
%USERNAME% – <username>
%USERPROFILE% – C:\Users\<username>
%USERDOMAIN% – Userdomain associated with current user.
%USERDOMAIN_ROAMINGPROFILE% – Userdomain associated with roaming profile.
%WINDIR% – C:\Windows
%PUBLIC% – C:\Users\Public
%PSMODULEPATH% – %SystemRoot%\system32\WindowsPowerShell\v1.0\Modules\
%ONEDRIVE% – C:\Users\<username>\OneDrive
%DRVERDATA% – C:\Windows\System32\Drivers\DriverData
%CMDCMDLINE% – Outputs command line used to launch the current Command Prompt session. (Command Prompt.)
%COMPUTERNAME% -Outputs the system name.
%PROCESSOR_REVISION% – Outputs processor revision.
%PROCESSOR_IDENTIFIER% – Outputs processor identifier.
%PROCESSOR_LEVEL% – Outputs processor level.
%RANDOM% – This variable prints a random number from 0 through 32767
%NUMBER_OF_PROCESSORS% – Outputs the number of physical and virtual cores.
%OS% – Windows_NT
This was pretty much about System and User Environment Variables on Windows. Windows does come with a lot more variables – don’t forget to check them using the ‘SET’ command.
TIP: Rapid Environment Editor is a powerful Environment Variables Editor for Windows.
This tutorial will show you a complete list of default environment variables that can be used to reference standard directories and parameters in Windows 10 and Windows 11.
Environment variables are a set of dynamic named values that can affect the way running processes will behave on a computer. The variables can be used both in scripts and on the command line. Environment variables makes it easy when certain standard directories and parameters need to be referenced but where the actual locations or names can vary from computer to computer.
The variable (ex: «%UserProfile%» for command and «$Env:UserProfile» for PowerShell) is used as a type of shortcut of the value (ex: «C:\Users\<username>»).
There are two types of environment variables: user environment variables (set only for current user) and system environment variables (set for all users).
User environment variables are stored in the registry key below:
HKEY_CURRENT_USER\Environment
System environment variables are stored in the registry key below:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
You can open a command prompt, type set, and press Enter to display all current environment variables on your PC.
You can open PowerShell, type Get-ChildItem Env:, and press Enter to display all current environment variables on your PC.
|
Command |
PowerShell |
Values |
|---|---|---|
| %ALLUSERSPROFILE% | $Env:ALLUSERSPROFILE | C:\ProgramData |
| %APPDATA% | $Env:APPDATA | C:\Users\(user-name)\AppData\Roaming |
| %CD% | $Env:CD | Current directory full path |
| %CMDCMDLINE% | Returns exact command line used to start current cmd.exe session. | |
| %CMDEXTVERSION% | Number of current command processor extensions. | |
| %CommonProgramFiles% | $Env:CommonProgramFiles | C:\Program Files\Common Files |
| %CommonProgramFiles(x86)% | $Env:CommonProgramFiles(x86) | C:\Program Files (x86)\Common Files |
| %CommonProgramW6432% | $Env:CommonProgramW6432 | C:\Program Files\Common Files |
| %COMPUTERNAME% | $Env:COMPUTERNAME | The computer name of the current local system. |
| %ComSpec% | $Env:ComSpec | C:\Windows\System32\cmd.exe |
| %DATE% | Current date in format determined by Date command | |
| %DriverData% | $Env:DriverData | C:\Windows\System32\Drivers\DriverData |
| %ERRORLEVEL% | Number defining exit status of previous command or program | |
| %HOMEDRIVE% | $Env:HOMEDRIVE | C: |
| %HOMEPATH% | $Env:HOMEPATH | \Users\(user-name) |
| %LOCALAPPDATA% | $Env:LOCALAPPDATA | C:\Users\(user-name)\AppData\Local |
| %LOGONSERVER% | $Env:LOGONSERVER | \\MicrosoftAccount |
| %NUMBER_OF_PROCESSORS% | $Env:NUMBER_OF_PROCESSORS | 12 |
| %OneDrive% | $Env:OneDrive | Current OneDrive folder location |
| %OS% | $Env:OS | Windows_NT |
| %Path% | $Env:path | C:\WINDOWS C:\WINDOWS\system32 C:\WINDOWS\System32\Wbem C:\WINDOWS\System32\WindowsPowerShell\v1.0 |
| %PATHEXT% | $Env:pATHEXT | COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC |
| %PROCESSOR_ARCHITECTURE% | $Env:pROCESSOR_ARCHITECTURE | AMD64 |
| %PROCESSOR_IDENTIFIER% | $Env:pROCESSOR_IDENTIFIER | Intel64 Family 6 Model 158 Stepping 10, GenuineIntel |
| %PROCESSOR_LEVEL% | $Env:pROCESSOR_LEVEL | 6 |
| %PROCESSOR_REVISION% | $Env:pROCESSOR_REVISION | 9e0a |
| %ProgramData% | $Env:programData | C:\ProgramData |
| %ProgramFiles% | $Env:programFiles | C:\Program Files |
| %ProgramFiles(x86)% | $Env:programFiles(x86) | C:\Program Files (x86) |
| %ProgramW6432% | $Env:programW6432 | C:\Program Files |
| %PROMPT% | Code for current command prompt format. Code is usually $P$G | |
| %PSModulePath% | $Env:pSModulePath | C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ |
| %PUBLIC% | $Env:pUBLIC | C:\Users\Public |
| %RANDOM% | Get random number between 0 and 32767 | |
| %SESSIONNAME% | $Env:SESSIONNAME | When logging on directly to machine, returns «Console».
When client connects via terminal server session, is combination of |
| %SystemDrive% | $Env:SystemDrive | C: |
| %SystemRoot% | $Env:SystemRoot | C:\Windows |
| %TEMP% | $Env:TEMP | C:\Users\(user-name)\AppData\Local\Temp |
| %TIME% | Current time in format determined by Time command | |
| %TMP% | $Env:TMP | C:\Users\(user-name)\AppData\Local\Temp |
| %USERDOMAIN% | $Env:USERDOMAIN | Network domain name associated with the current user. |
| %USERDOMAIN_ROAMINGPROFILE% | $Env:USERDOMAIN_ROAMINGPROFILE | Network domain name associated with the current roaming profile. |
| %USERNAME% | $Env:USERNAME | (user-name) |
| %USERPROFILE% | $Env:USERPROFILE | C:\Users\(user-name) |
| %WINDIR% | $Env:WINDIR | C:\Windows |
That’s it,
Shawn Brink
Related Tutorials
- Create New Environment Variables in Windows 11
- Delete Environment Variables in Windows 11
- Create Shortcuts to Open Control Panel Items in Windows 11
- Create Shortcuts to Open Pages in Settings in Windows 11
- List of Windows 11 CLSID Key (GUID) Shortcuts
- List of Windows 11 Shell Commands for Shell Folder Shortcuts
- Complete List of Rundll32 Commands in Windows 11
Last edited:
GWD
Active member
-
-
#2
Hi Brink,
If I am missing several of these Environmental Variables from your list above, is there any advantage to manually adding them?
Also, should I be on the lookup for obsolete Environmental Variables that should be deleted?
Thanks,
GWD
-
- OS
- Windows 11 Pro for Workstations
- Computer type
- PC/Desktop
- Manufacturer/Model
- Alienware
- CPU
- Intel(R) Core (TM) i7-9700 CPU @ 3.00 GHz
- Memory
- 32 GB
- Graphics Card(s)
- NVIDIA GeForce RTX 2060
Try3
Well-known member
-
-
#3
How did you list them?
Which ones are missing?
Denis
-
- OS
- Windows 11 Home x64 Version 23H2 Build 22631.3447
-
-
#4
Hi Brink,
If I am missing several of these Environmental Variables from your list above, is there any advantage to manually adding them?
Also, should I be on the lookup for obsolete Environmental Variables that should be deleted?
Thanks,
GWD
Hello GWD, and welcome.
You can check using one of the commands at the top to see which variables you currently have.
Which ones are you missing?
-
- OS
- Windows 11 Pro for Workstations
- Computer type
- PC/Desktop
- Manufacturer/Model
- Custom self build
- CPU
- Intel i7-8700K 5 GHz
- Motherboard
- ASUS ROG Maximus XI Formula Z390
- Memory
- 64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
- Graphics Card(s)
- ASUS ROG-STRIX-GTX1080TI-O11G-GAMING (11GB GDDR5X)
- Sound Card
- Integrated Digital Audio (S/PDIF)
- Monitor(s) Displays
- 2 x Samsung Odyssey G75 27″
- Screen Resolution
- 2560×1440
- Hard Drives
- 1TB Samsung 990 PRO M.2,
4TB Samsung 990 PRO M.2,
8TB WD MyCloudEX2Ultra NAS
- PSU
- Seasonic Prime Titanium 850W
- Case
- Thermaltake Core P3 wall mounted
- Cooling
- Corsair Hydro H115i
- Keyboard
- Logitech wireless K800
- Mouse
- Logitech MX Master 3
- Internet Speed
- 1 Gbps Download and 35 Mbps Upload
- Browser
- Google Chrome
- Antivirus
- Microsoft Defender and Malwarebytes Premium
- Other Info
- Logitech Z625 speaker system,
Logitech BRIO 4K Pro webcam,
HP Color LaserJet Pro MFP M477fdn,
CyberPower CP1500PFCLCD
Galaxy S23 Plus phone
-
- Operating System
- Windows 11 Pro
- Computer type
- Laptop
- Manufacturer/Model
- Surface Laptop 7 Copilot+ PC
- CPU
- Snapdragon X Elite (12 core) 3.42 GHz
- Memory
- 16 GB LPDDR5x-7467 MHz
- Monitor(s) Displays
- 15″ HDR
- Screen Resolution
- 2496 x 1664
- Hard Drives
- 1 TB SSD
- Internet Speed
- Wi-Fi 7 and Bluetooth 5.4
- Browser
- Chrome and Edge
- Antivirus
- Windows Defender
-
-
#5
I have a cmd file in which %USERPROFILE% works in win10 32bit but not in win11 64bit but fixed it with using %HOMEPATH% I didn’t think it should make a difference.
-
- OS
- Windows 11 PRO, 22H2
- CPU
- Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz 3.10 GHz
- Motherboard
- ASUS PRIME B460M-A
- Memory
- 16.0 GB
- Monitor(s) Displays
- 2 X Acer B243HL
- Hard Drives
- Samsung SSD 970 EVO Plus 500GB + 2 SATA X 1TB
-
-
#6
Is there no Environment Variable for?: C:\Users\Default\AppData
-
- OS
- Windows 11 Pro
- Computer type
- PC/Desktop
- Manufacturer/Model
- Stigg’s Build
- CPU
- Intel Core i9-10900X
- Motherboard
- GIGABYTE X299X DESIGNARE 10G
- Memory
- Corsair 64 GB (4 x 16 GB) CMW64GX4M4C3000C15 Vengeance RGB Pro 3000Mhz DDR4
- Graphics Card(s)
- GIGABYTE GeForce GTX 1660 Super Mini ITX 6 GB OC
- Sound Card
- Realtek ALC1220
- Monitor(s) Displays
- Samsung 27″ FHD LED FreeSync Gaming Monitor (LS27F350FHEXXY)
- Screen Resolution
- 1920 x 1080
- Hard Drives
- Samsung 970 Pro Series 1TB M.2 2280 NVMe SSD
Western Digital Red Pro WD8003FFBX-68B9AN0 8 TB, 7200 RPM, SATA-III
Western Digital Red Pro WD8003FFBX-68B9AN0 8 TB, 7200 RPM, SATA-III
- PSU
- Corsair HX1200 1200W 80 Plus Platinum
- Case
- Fractal Design Define 7 Black Solid Case
- Cooling
- Noctua NH-D15 Chromax Black
- Keyboard
- Razer Ornata V2
- Mouse
- Razer DeathAdder Essential
- Internet Speed
- FTTN 100Mbps / 40Mbps
- Browser
- Mozilla Firefox
- Antivirus
- N/A
- Other Info
- Logitech BRIO 4k Ultra HD USB-C Webcam
-
- Operating System
- Windows 10 Pro
- Computer type
- Laptop
- Manufacturer/Model
- ASUS ROG Zephyrus M GM501GS
- CPU
- Core i7-8750H
- Motherboard
- Zephyrus M GM501GS
- Memory
- SK Hynix 32 GB (2 x 16 GB) HMA82GS6CJR8N-VK 16 GB DDR4-2666 DDR4 SDRAM
- Graphics card(s)
- NVIDIA GeForce GTX 1070
- Sound Card
- Realtek ALC294
- Monitor(s) Displays
- AU Optronics B156HAN07.1 [15.6″ LCD]
- Screen Resolution
- 1920 x 1080
- Hard Drives
- Samsung MZVKW512HMJP-00000 512 GB, PCI-E 3.0 x4
Samsung SSD 860 QVO 4TB 4 TB, SATA-III
- PSU
- N/A
- Case
- N/A
- Cooling
- N/A
- Mouse
- Razer DeathAdder Essential
- Keyboard
- PC/AT Enhanced PS2 Keyboard (101/102-Key)
- Internet Speed
- FTTN 100Mbps / 40Mbps
- Browser
- Mozilla Firefox
- Antivirus
- N/A
- Other Info
- USB2.0 HD UVC Webcam
Try3
Well-known member
-
-
#7
I have a cmd file in which %USERPROFILE% works in win10 32bit but not in win11 64bit but fixed it with using %HOMEPATH% I didn’t think it should make a difference.
I am also surprised.
What does %USERPROFILE% return for you in those two OSes?
Denis
-
- OS
- Windows 11 Home x64 Version 23H2 Build 22631.3447
-
-
#8
ERROR in win11 (using robocopy) but works perfectly in win10 32
%HOMEPATH% works perfectly in win11 64 & win10 32
same problem with xcopy
-
- OS
- Windows 11 PRO, 22H2
- CPU
- Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz 3.10 GHz
- Motherboard
- ASUS PRIME B460M-A
- Memory
- 16.0 GB
- Monitor(s) Displays
- 2 X Acer B243HL
- Hard Drives
- Samsung SSD 970 EVO Plus 500GB + 2 SATA X 1TB
-
-
#9
What is the environment variable for:
C:\Users\{username}\AppData\LocalLow
-
- OS
- Windows 11
Try3
Well-known member
-
-
#10
What is the environment variable for:
C:\Users\{username}\AppData\LocalLow
There isn’t one.
You’d have to use something like
%UserProfile%\AppData\LocalLow
Denis
-
- OS
- Windows 11 Home x64 Version 23H2 Build 22631.3447
-
-
#11
that’s what I thought
Thank you
-
- OS
- Windows 11
Windows Environment Variables List: Complete List on Windows 10 / 11. Microsoft first introduced file shortcuts in Windows 95. They were designed to add customization and make resources easier to access for users. Each iteration of Windows has attempted to propagate this idea. Operating systems should ultimately be easy to use while catering to the needs of their users. This is typically done through simplification, masking and linking. In a similar fashion to how a DNS provides an easily digestible name for a long IP Address. As you’ll see, Environment Variables ultimately function on the same principle (more or less). The following guide will explore what they are and list all of them for Windows 10 and 11. Without further ado…
Let’s start with Windows Environment Variables List: Complete List on Windows 10 / 11.
What are Environment Variables?
Before you dive into Environment Variables, you must understand what variables are in reference to programming languages. In computer programming, variables act as information containers. They point towards a resource or instruction. They essentially make it easier to reference information in a programming language. Instead of typing out information repeatedly, you place it in a variable and reference it instead. Again, they work similarly to domain names.
Environment Variables are variables defined outside of programs. This allows you to change them without modifying a program’s source code. Windows applications commonly use Environment Variables to determine where to either store or fetch data. For instance, an Environmental Variable may tell an application where to store temp files. Additionally Environment variables use a key and value format.
You can also use Windows search and run with Environment Variables. For instance, %APPDATA% is an example of an extremely useful Environment Variable that points towards the AppData Roaming folder. Instead of typing the entire address out (C:\Users\{username}\AppData\Roaming), you can just type the %APPDATA% shorthand.
How to Access Environment Variables
As with most things in Windows, there are several ways to access Environment Variables. The easiest is Windows’ Search:
Using Windows Search
- Open Windows Search (WinKey + S) or Start Menu (WinKey).
- Next, type Environment Variable into the search bar.
- Click on Edit the system environment variables. This will open the Systems Properties dialog.
- Make sure that the Advanced tab is selected and then click on the button labeled Environment Variable button.
Using the Control Panel
- Run the Windows Control Panel.
- Make sure you are viewing the Control Panel’s items as either small or large icons.
- Right click on System and select Open from the context menu.
- Click on Advanced system settings. Again, this action will bring up the System Properties Dialog.
- Click on the Environment Variables button.
Alternatively, you can use the search bar on the Control Panel window. Just click on it and type Environment Variables. This returns the System item along with some additional options underneath it. Click on Edit the system environment variables.
Using the Power User Menu
- Open the Power User Menu by right clicking on the Start Menu icon or pressing the Windows Key together with the X key on your keyboard.
- Next, select System from your Power User Menu.
- Scroll down through the list until you encounter the Advanced system settings.
- Finally, make sure that the Advanced tab is selected and then click on the Environment Variables button as you have done before.
In addition to the above options, you can also access the System Properties by using the This PC context menu. Just right click on This PC from Windows File Explorer or your desktop shortcut and select Properties.
So what are Windows Environment Variables List? Let’s find out.
List of Environment Variables
Here the Windows Environment Variables List section provides you with the complete list of variables for Windows. This list should be uniform across past (Windows 7/8/8.1) and present (Windows 10/11) versions of the Microsoft Windows operating system.
All User Profile
- Variable: %ALLUSERSPROFILE%
- Default Value: C:\ProgramData
- Details: Points to the location/address of the folder Windows uses to store data shared by all users on the machine.
App Data
- Variable: %APPDATA%
- Default Value: C:\Users\UserName\AppData\Roaming
- Details: Point to the location of the Roaming folder in the Application Data folder (AppData\Roaming).
Common Program Files
- Variable: %CommonProgramFiles%
- Default Value: C:\Program Files\Common Files
- Details: Points to the location of the Common Files folder in the Program Files folder.
Common Program Files(x86)
- Variable: %CommonProgramFiles(x86)%
- Default Value: C:\Program Files(x86)\Common Files
- Details: Points to the location of the Common Files folder in the Program Files (x86) folder. Typically, this folder is reserved for 32-bit programs.
Common Program W6432
- Variable: %CommonProgramW6432%
- Default Value: C:\Program Files\Common Files
- Details: Works identically to the %CommonProgramFiles%. However, it’s only supported by 64-bit versions of the Windows operating system as it’s utilized by the WOW64 emulation layer.
Computer Name
- Variable: %COMPUTERNAME%
- Default Value: ComputerName
- Details: This environmental variable points to the name of your computer name which can be found and changed under System Properties.
Command Specifier
- Variable: %COMSPEC%
- Default Value: C:\Windows\System32\cmd.exe
- Details: Points to the location of the system’s default command interpreter i.e. command prompt.
Current Directory
- Variable: %CD%
- Default Value: CurrentDirectory
- Details: Refers to the current directory that the command line is pointing to. Retrieve your current directory when referenced in the Command Prompt or PowerShell.
Command Line Session
- Variable: %CMDCMDLINE%
- Default Value: OriginCommandPrompt
- Details: Determines the command line that launched the current Command Prompt session.
Command Processor Extensions
- Variable: %CMDEXTVERSION%
- Default Value: CommandProcessorExtensions
- Details: Used in the command line to retrieve the number of current command processor extensions.
Date
- Variable: %DATE%
- Default Value: DATE
- Details: Used in Command Prompt to return the current date.
Driver Data
- Variable: %DriverData%
- Default Value: C:\Windows\System32\Drivers\DriverData
- Details: Points to the location of hardware driver data for the Windows operating system.
Error Level
- Variable: %ERRORLEVEL%
- Default Value: Exit Status
- Details: Used to retrieve the exit status of the last command.
Home Drive
- Variable: %HOMEDRIVE%
- Default Value: C:
- Details: Points to the dive letter where all the user profiles are located.
Home Path
- Variable: %HOMEPATH%
- Default Value: \Users\Username
- Details: Signifies the location of the current user’s profile directory. The drive letter is omitted from the path.
Local Application Data
- Variable: %LOCALAPPDATA%
- Default Value: C:\Users\UserName\AppData\Local
- Details: Points to the location of the local subfolder found in the AppData folder.
Logon Server
- Variable: %LOGONSERVER%
- Default Value: \\DomainLogonServer
- Details: Points to the network location of the group or domain from which your computer is connected. If you’re not connected to a domain or group, it will use the local computer’s location.
One Drive
- Variable: %OneDrive%
- Default Value: C:\Users\UserName\OneDrive
- Details: Points to the location of the OneDrive local folder.
Operating System
- Variable: %OS%
- Default Value: Operating System
- Details: Used to return and display the version of the Windows operating system.
Path
- Variable: %PATH%
- Default Value: C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem; etc.
- Details: Contains a list of paths to binary files used by various programs. You can execute the files kept in these directories directly from the command line without using the entire path e.g. Java.exe as opposed to C:\Program Files\Oracle\Java.exe. Typically, files with the extensions found in the %PATHEXT% are the only ones executable.
Path Extensions
- Variable: %PATHEXT%
- Default Value: com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc
- Details: Refers to the filetypes which can be directly executed from the command line.
Processor Identifier
- Variable: %PROCESSOR_IDENTIFIER%
- Default Value: Processor Identifier
- Details: Used in Command Prompt to return the processor identifier.
Processor Level
- Variable: %PROCESSOR_LEVEL%
- Default Value: Processor Level
- Details: Used in Command Prompt to return the processor level.
Processor Revision
- Variable: %PROCESSOR_REVISION%
- Default Value: Processor Revision
- Details: Used in Command Prompt to return the processor revision.
Number of Processors
- Variable: %NUMBER_OF_PROCESSORS%
- Default Value: Number of processors
- Details: Used in Command Prompt to return and display the number of virtual and physical cores.
Program Data
- Variable: %ProgramData%
- Default Value: %SystemDrive%\ProgramData
- Details: Points to the location of the hidden Program Data folder. This folder is used by some applications to store data.
Program Files
- Variable: %ProgramFiles%
- Default Value: %SystemDrive%\Program Files
- Details: Points to the location of the default Program Files folder on your system.
Program Files x86
- Variable: %ProgramFiles(x86)%
- Default Value: %SystemDrive%\Program Files (x86)
- Details: Points to the location of the Program Files folder that is intended for 32-bit.
Program W6432
- Variable: %ProgramW6432%
- Default Value: %SystemDrive%\Program Files
- Details: Used by the WOW32 Emulation Layer to find the default path to the Program Files folder.
Prompt
- Variable: %PROMPT%
- Default Value: $p$g
- Details: Used to change and restore the command prompt to its default setting.
PowerShell Module Path
- Variable: %PSModulePath%
- Default Value:
%SystemRoot%\system32\WindowsPowerShell\v1.0\Modules\ — (Windows 7/8/10) %ProgramFiles%\WindowsPowerShell\Modules\;C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ — (Windows 11) - Details: Points to the path where PowerShell’s modules are stored.
Public
- Variable: %PUBLIC%
- Default Value: %SystemDrive%\Users\Public
- Details: Points to the location of the Public user profile
Random
- Variable: %RANDOM%
- Default Value: Random number between 0 and 32767
- Details: Used in Command Prompt to return a number between 0 and 32767
System Drive
- Variable: %SystemDrive%
- Default Value: C:
- Details: Refers to the drive letter of the drive where your operating system is installed and running from.
System Root
- Variable: %SystemRoot%
- Default Value: %SystemDrive%\Windows
- Details: Refers to the install folder of the Windows OS.
Time
- Variable: %TIME%
- Default Value: TIME
- Details: Used in Command Prompt to return the current time.
Temp
- Variable: %TEMP% or %TMP%
- Default Value: User Processes – %USERPROFILE%\AppData\Local\Temp
System Process – %SystemRoot%\TEMP - Details: Points to the location of the temporary files folder. These files are typically transient files used by installers and other programs.
User Domain
- Variable: %USERDOMAN%
- Default Value: UserDomain
- Details: Refers to the current user’s domain or group.
User Name
- Variable: %UserName%
- Default Value: UserName
- Details: Refers to the current user’s name.
User Profile
- Variable: %USERPROFILE%
- Default Value: %SystemDrive%\Users\UserName
- Details: Points to the current user’s profile path where their data is stored.
Windows Directory
- Variable: %windir%
- Default Value: %SystemDrive%\Windows
- Details: Much like the %SystemRoot% variable, it points to the directory of the Windows operating system.
Thank you for reading Windows Environment Variables List: Complete List on Windows 10 / 11.
Windows Environment Variables List: Complete List on Windows 10 / 11 Conclusion
Above guide provides you with a comprehensive list of Environment Variables for Windows 10 and 11. Also it briefly investigates how you can see and edit some of your Windows operating system’s variables. Summarizing the Environment Variables can enhance your Windows experience by offering you new ways to customize and use it. Every administrator and power user should have a healthy understanding of Environmental Variables. Nevertheless, if you have any corrections or queries, please leave them down below. How do you utilize Windows Environment Variables?
Take a look at more Windows content here.