1

This is a very annoying thing, to run any .exe that is inside the current directory in Powershell, I am required to use a .\ ahead.

For example, if I have the program fastboot.exe inside the current folder I can not simply type fastboot, as it does inside cmd. I'm forced to type:

.\fastboot

If I just type fastboot (without .\ I get some error like:

The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

+ fastboot + ~~~~~~~~ + CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException

How to avoid this?

  • Could you be a little more specific? I just checked mine and that's not the case. I'm running PS version 5.1. I typed "cd C:\users\xxx\desktop" and then typed "start xxx.xxx" and it opened without a leading ".\" - Could you provide a snippet of your code? The .\ might be needed for another reason. – Andrew Nov 6 '18 at 1:54
  • to run any command...are you sure this is required for all/any commands? Not just PowerShell scripts? – Twisty Impersonator Nov 6 '18 at 1:56
  • I corrected the post, it would not be "command", but ".exe". – Rogério Dec Nov 6 '18 at 2:08
  • can you provide the response when you try to use the command like you expect? – manbearpig Nov 6 '18 at 2:18
  • I put the error in the post – Rogério Dec Nov 6 '18 at 2:37
1

Powershell does not load commands from the current location by default.

Suggestion [3,General]: The command xxx.exe was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type ".\xxx.exe". See "get-help about_Command_Precedence" for more details.

So you are left with two options

  • Lower the security barrier by adding the current directory to you path

     $env:path ="$($env:path);."
    
  • Get into the habbit of always prefixing the command with .\

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.