Most windows executable commands not recognized by CMD and PowerShell.

[herbal_rage]

Out of nowhere commands which involve executables like explorer.exe, msedge.exe, mspaint.exe, where, etc. are not working in command prompt or PowerShell. The output of the command prompt seem to be quite simple: ```C:\Users\grass>where 'where' is not recognized as an internal or external command, operable program or batch file. C:\Users\grass>explorer 'explorer' is not recognized as an internal or external command, operable program or batch file.```I'm still able to call applications in the path, like: idea, code, adb, gcc, etc.Some things also stopped working, and it looks relevant to

Continue reading...