Command not usable through runret() or command prompt

Things you’d like to miss in the future...
Forum rules
:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:

:info: Please include the following information:
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).

:info: We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.

:info: When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".

:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:
Post Reply
o7blue
Posts: 116
Joined: 22 Dec 2020 07:10

Command not usable through runret() or command prompt

Post by o7blue »

I recently installed jq (that is, I downloaded the jq binary from https://github.com/jqlang/jq/releases, and put it in C:\Windows\System32\jq.exe)

Now when I open up powershell (start right click menu) or the command prompt (running cmd in eplorer) jq runs ok.

But trying to do the same through the command prompt spawned via XY, or runret() results in the command not being found:

'jq' is not recognized as an internal or external command, operable program or batch file.

When I echo %PATH% C:\Windows\system32 is the first entry, I'm not sure why jq isn't found?

highend
Posts: 14991
Joined: 06 Feb 2011 00:33
Location: Win Server 2022 @100%

Re: Command not usable through runret() or command prompt

Post by highend »

Read the help file about "WOW64 redirection"...
One of my scripts helped you out? Please donate via Paypal

o7blue
Posts: 116
Joined: 22 Dec 2020 07:10

Re: Command not usable through runret() or command prompt

Post by o7blue »

Thank you highend, wasn't aware of this.
Moving my binary to C:\Windows\SysWOW64 solves this.

Post Reply