So you are trying to run a PowerShell and keep getting:
Suggestion [3,General]: The command <script file> was not found, but does exist in the current location. Windows PowerShell doesn't load commands from the current location by default. If you trust this command, instead type ".\<script>.ps1". See "get-help about_Command_Precedence" for more details.
This generic error is pretty much what you will see for anything, even if the file does not exist. One of my clients was trying to run Invoke-AlertFixup in SharePoint and kept getting this error even when correctly opening it as:
The fix is quite simple - simply enter:
$env:PATH = $env:PATH + "."
then enter the .\<script>.ps1 - Viola!