The environment command breaks your entire path variables.
Valiice opened this issue · comments
"the environment command"? please be more specific, we can't help you with absolutely no details or explanation
Sorry, I didn't get a single email about this.
What happened was: I used the setx path command and it deleted all my PATH value's. I have no clue why it deleted all of them.
I ran into this issue and had to do a system restore to bring back the path envar.
During the installation instructions of FFMPEG on windows, the command reads:
"After moving the ffmpeg folder into your C: drive, open Command Prompt with administrator and run this: setx /m PATH "C:\ffmpeg\bin;%PATH%" "
This replaces the envars entirely if it's ran in powershell, as %PATH% doesn't print the Path envar.
Whilst the commands do say "Command Prompt", the default terminal on windows is moving towards powershell, so it's not inconceivable that someone else could accidentally run it in powershell.
If You've accidentally done this, You can either run a command to get the old envars if you have another terminal window open, (either by running echo %path% if it is command prompt, or echo $Env:path if it's powershell) to get a list of the old envars.
Failing that, you will need to use a system restore point by going to "Advanced system settings", navigating to the "System Protection" tab and using System Restore.
Yea, I had used the Windows Terminal app which on default uses Powershell.
I basically manually filled the PATH env back up. This was quite annoying since it was quite a bit as well.
Thank you for the command to get the old envars back though.
Argh, shame you had to manually fill it all back, at least if someone else stumbles across this they are potentially spared the pain now.