Yes I did and no luck.
I also tried it on the system drive, same error.
I haven't loaded everything onto the system yet but so far most things work as expected including AVSPmod. Some of the avisynth plugin took sometime to work as had to install some of the older versions of Visual C++.
Windows has all the latest updates.
Prepend the command with .\ like the suggestion tells you to. This is not unexpected behavior, and I can confirm that here: with the path specifier, avsmeter64 runs fine in PS - without it, it throws the exact same error. Do not use quotation marks.
Or better yet, actually take advantage of PS' tab autocompletion feature to make sure the command is written correctly.
To demonstrate this, navigate back a couple directories and use the fuller relative path - it works, with or without the .\, because you're specifying the directory. Stuff on the %PATH% also works exactly as cmd.exe handles it.
PS E:\> cd .\Documents\AVSMeter278\
PS E:\Documents\AVSMeter278> ls
Directory: E:\Documents\AVSMeter278
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 6/9/2018 6:07 AM doc
d----- 6/9/2018 6:07 AM source
-a---- 6/9/2018 6:07 AM 373248 AVSMeter.exe
-a---- 6/9/2018 6:07 AM 473088 AVSMeter64.exe
PS E:\Documents\AVSMeter278> avsmeter64
avsmeter64 : The term 'avsmeter64' 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.
At line:1 char:1
+ avsmeter64
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (avsmeter64:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command avsmeter64 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: ".\avsmeter64".
See "get-help about_Command_Precedence" for more details.
Doing what it says to do:
PS E:\Documents\AVSMeter278> .\avsmeter64
AVSMeter 2.7.8 (x64) - Copyright (c) 2012-2018, Groucho2004
Usage: AVSMeter script.avs [switches]
Switches:
-avsinfo [-ai] Display extended Avisynth info
-c Specify custom plugin directory
in combination with "-avsinfo"
-avsdll [-ad] Specify avisynth.dll to be used
-info [-i] Display clip info
-log [-l] Create log file
-csv Create csv file
-gpu Display GPU/VPU usage (requires GPU-Z)
-range=first,last Set frame range
-timelimit=n Set time limit (seconds)
-priority=n Set process priority (1:low, 2:normal, 3:high)
For more info on the command line switches and INI file
settings read the documentation (AVSMeter.html) included
in the distribution package.
Running from a directory above:
PS E:\Documents> AVSMeter278\AVSMeter64.exe
AVSMeter 2.7.8 (x64) - Copyright (c) 2012-2018, Groucho2004
Usage: AVSMeter script.avs [switches]
Switches:
-avsinfo [-ai] Display extended Avisynth info
-c Specify custom plugin directory
in combination with "-avsinfo"
-avsdll [-ad] Specify avisynth.dll to be used
-info [-i] Display clip info
-log [-l] Create log file
-csv Create csv file
-gpu Display GPU/VPU usage (requires GPU-Z)
-range=first,last Set frame range
-timelimit=n Set time limit (seconds)
-priority=n Set process priority (1:low, 2:normal, 3:high)
For more info on the command line switches and INI file
settings read the documentation (AVSMeter.html) included
in the distribution package.
PS E:\Documents>
Trying a program on the %PATH%:
PS E:\Documents\AVSMeter278> youtube-dl --help
Usage: youtube-dl [OPTIONS] URL [URL...]
Options:
General Options:
-h, --help Print this help text and exit
--version Print program version and exit
-U, --update Update this program to latest version. Make sure that you have sufficient
[...]
The point here is that PowerShell is not cmd.exe - cmd.exe assumes the current directory is on the %PATH%, PowerShell does not. PowerShell's behavior conforms to the way most non-Windows-centric shells behave, which is fine, since PowerShell also uses a greatly-expanded scripting language compared to cmd.exe.
'.\' (or './' on shells like bash - the ubiquitous './configure' when compiling stuff is the configure script in the current directory; when doing out-of-tree builds there's no need to use ./, because you give it the full or relative path) is a directory specifier, a piece of shorthand that explicitly says 'this file is in the current directory'*, because you can run a binary or script from a relative path just outside the directory, or from an absolute path (E:\Documents\AVSMeter278\<application name> or AVSMeter278\<application name> if you're sitting in Documents). The same way ~/ means 'your %HOME% directory'.
*'.' is what denotes the current directory, while / or \ is the path separator, depending on your OS.
So if you want to keep using PowerShell, your solution is one of:
A) Copy AVSMeter.exe to C:\Windows\SysWOW64 and AVSMeter64.exe to C:\Windows or C:\Windows\System32 (because those directories are on the %PATH%).
B) Explicitly add the AVSMeter278 directory to the %PATH%, wherever it resides.
C) Get used to having to use .\ as the directory specifier.