Windows 10: Why would Powershell or cmd not recognize any commands, I am also not able to reset my...

I have felt ive been hacked for some time now but dont know what to look for to prove it. I also have suspicion/question...are there files a hacker can upload to my laptop that would restrict me from completing such tasks??

:)

 

Most windows executable commands not recognized by CMD and PowerShell.

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 this overall terminal issue:

• IntelliJ IDEA cannot launch its in-IDE terminal. In particular it cannot find PowerShell.
  
• I cannot run any windows executables from WSL2 environment.
  
• Oracle virtual box running UBUNTU LTE16.04 has issues syncing shared folders.
  

 

Can't run command in PowerShell but OK in Cmd

I tried the suggested command and it does work manually in Power Shell. But Task Scheduler chokes on it.





If i say "Yes" it breaks up the command string to "%C:\program" with the rest of the command as an argument.

 

Not all command lines of CMD are working in Powershell

In build 14971.1000 Microsoft has changed Command prompt with Powershell in the right-click context Startmenu, see screenshot below.

Batch files (.bat or .cmd) will also not run properly in Powershell because not all command lines of HELP are working in the Powershell. How do we run batch (.bat) files with command lines that aren't supported in it.

Consider you have a file "test.bat" on the root of the D: dirve. You can't run in it Powershell by entering "test.bat" on the D: drive. The term will not be recognized. You have to write "D:\test.bat" to run it in Powershell. That is strange behaviour. In
the old CMD you didn't had to add "D:\" path in the line to run it in the opened directory.

I know CMD can still be executed in the Startmenu of build 14971.1000, but it looks they are changing this behaviour. It is now hidden from the contextmenu by default.

For those who prefer to use Command Prompt, you can opt out of the WIN + X change by opening Settings > Personalization > Taskbar, and turning “Replace Command Prompt with Windows PowerShell in the menu when I right-click the Start button or press Windows
key+X” to “Off”.