Command Prompt/PowerShell/Terminal doesn't give any output when running almost any .exe file like adb.exe

Anonymous
2024-01-18T07:43:55+00:00

I have a new laptop with Windows 11 Pro installed on it.

I have noticed that I cannot run almost any .exe file within the Command Prompt, Terminal nor PowerShell to execute.

It doesn't give me any output at all.

See the screenshot:

my PATH variables looks ok:

I have tried everything to get any output, but nothing is working...

System is running Win11 23H2

Windows for home | Windows 11 | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

8 answers

Sort by: Most helpful
  1. Anonymous
    2024-01-26T08:04:36+00:00

    Strange. It sounds like you've rebooted already. Maybe check the options for Cmd, specifically the buffer size. See:

    https://superuser.com/questions/1640320/cannot-see-output-of-command-prompt-anymore-windows-10

    Normally with 23H2, your Cmd window would be a Terminal window. Even if you directly run Cmd.exe, it should open Terminal. In your case, you've got the old-school Cmd window. You can get to that window directly by running conhost.exe but you ran c:\windows\system32\cmd.exe. That should have opened like this:

    Image

    It might help to go to Settings, Apps, Installed Apps, Terminal, Advanced options. You can try Repair, Reset, or Uninstall and then reinstall.

    You can manually change that within the system settings to still get the command prompt.

    However, like the title already said, I get the same results even when using Terminal and PowerShell.

    Using the advance options didn't make a difference for me. Problem is still existing.

    I've already seen that post about the buffer size, but everything was already set up properly, so it's not a buffer problem either...

    This problem drives me really nuts...

    0 comments No comments
  2. Anonymous
    2024-02-06T02:22:58+00:00

    This problem is still existing and too bad that it seems like no one knows how to solve this problem...

    0 comments No comments
  3. Anonymous
    2024-02-06T20:50:38+00:00

    I just found the solution!
    It was my Eset Antivirus that was the culprit.

    Everything started to work again after turning off the Deep Behavioral Inspection (you can find it inside HIPS settings)

    (Note: I haven't tried out to add it as an exception. It might work as well if you add it there)

    0 comments No comments