Rem Get all user environment variables as currently stored in Windows Rem registry and set them in local environment with exception of system PATH.įor /F "skip=2 tokens=1,2*" %%A in ('%SystemRoot%\System32\reg.exe query "HKLM\System\CurrentControlSet\Control\Session Manager\Environment" 2^>nul') do ( Rem Get all system environment variables as currently stored in Windows Rem do not already exist with unwanted values. Rem the PATH environment variables currently stored in Windows registry Rem Make sure the environment variables used to build local PATH from Rem Set current directory to user's profile directory. Setlocal EnableExtensions DisableDelayedExpansion This can be done by extending post_install.bat with following commented code: off For that reason it is necessary to update local environment variables with the system and user environment variables (in this order) before executing npm batch file. So whatever the Node.js installation process modified in Windows registry on the persistent stored system and user environment variables or on local environment variables of MSIEXEC process is not visible for the Windows command process executing the batch file post_install.bat.īut npm batch file executed by post_install.bat depends on environment variables stored in Windows registry during Node.js installation process.
Next is started by IExpress installation process a command process with command line cmd /c post_install.bat which gets by Windows a fresh copy of environment variables as currently set for IExpress installation process to work with. But those modifications on persistent stored environment variables for entire machine and current user are not automatically taken over to local environment variables list of already running IExpress installation process.
The IExpress installation process runs msiexec /i node.msi which installs Node.js and most likely adds or modifies system or user environment variables in Windows registry. So on starting IExpress installation process this installation process inherits the environment variables from its parent process which is usually Windows Explorer, but can be also a www browser or any other application. It also explains that no process can modify the environment variables of an already running process and each new process inherits the current list of environment variables of its parent process. The answer on What is the reason for '.' is not recognized as an internal or external command, operable program or batch file? explains where system and user environment variables are stored in Windows registry and how updates are made on them.
0 kommentar(er)
