Support Center

Windows command results in error "Not recognized as the name of cmdlet, function, script file, or operable program"



When attempting to run a Windows executable from the Command tab, the following error is reported back within the command log:

c:\windows\system32\application : The term 'c:\windows\system32\application' 
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 
+ c:\windows\system32\application.exe -flag
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
+ CategoryInfo : ObjectNotFound: 
String) [], CommandNotFoundException 
+ FullyQualifiedErrorId : CommandNotFoundException 



The commands function instantiates a 32-bit command process, so any command with 64-bit dependencies may not be recognized or run properly. There are numerous reasons, but in many cases it may be triggered by .net Classes, Snapins, Modules, or even COM Objects that are 64-bit dependent.


Call the sysnative virtual folder to launch a 64-bit process.  See Executing 64-bit Windows operations within JumpCloud Commands for examples. 

Last Updated: Nov 10, 2016 03:32PM MST

Related Articles
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found