Often see some software installation instructions that say, modify the environment variables for Windows, and then restart the computer. This begs the question, do you really want to restart after modifying the environment variable?
In fact, as long as the understanding of the principle of environmental variables can make the right judgment. Environment variables are system variables that are valid for any program that runs. The simplest method of confirmation is the Cmd.exe program. Click Start, run, enter CMD, enter in the command-line window that starts, and set
you'll see a whole bunch of different environment variables appearing on the screen. Modifying environment variables is done through the Environment Variables dialog box, System, control Panel, and so on.
The understanding here is that when a program starts, the environment variable is copied to the environment where the program is located, and it is not changed by programs other than that program during the execution of the program. that is, suppose we start a cmd program and then modify the environment variable settings through the Control Panel, but the environment variables owned by the CMD that have been started are not changed. If we start the CMD program after modifying the environment variable, the program will have the new environment variable.
So the conclusion is obvious: after modifying an environment variable, if the application is affected, the modification of the environment variable will be reflected in the program without restarting the computer if it is simply restarted, but if the system service is affected, A reboot is required to reflect the modification of the environment variable to the system service (because there is no way to restart the system Service Manager without restarting the computer).
Configuring environment variables under windows and requiring no restart issues