After installing Weback, run Webpack-v error: ' Webpack ' is not internal or external command

Recently, after the back-end colleague installs the Webpack, the Discovery command cannot run up.

Cause: The colleague installed Webpack when the global storage path and cache path to D disk, not in the default directory of C drive.

I think it may be because the system received the Webpack command will go to the C-disk to find Webpack file Parsing command, but there is no file in the C disk, and did not tell the system that the Webpack installation files changed position, the system does not know, did not find, will not run up.

WORKAROUND: Set the PATH environment variable to tell the system to install the file on the D drive.

Note: At the time of the test, the cmd command window is always the same, even if the environment variable is set, the command window is the previous system default C drive. You need to turn it off again to re-read the configuration and find the D drive in the environment variable.

After installing Weback, run Webpack-v error: ' Webpack ' is not internal or external command