@Xander, thank you for reporting this. Would you please try rebooting and trying the install again?

I tried the upgrade on 2 Windows 11 PC's and 1 Windows 10 PC so far and it worked for me. It took about 20-30 seconds to get started after I clicked the update option in the tray menu, but I soon got this install progress indicator:

6e1e5c6c-d264-416c-9f6b-a1bd49d5e296-image.png

... and now I have the new 1.0.47 version:

969b65b0-da50-40e4-a767-cfcfaad86621-image.png

What version shows in Apps > Installed apps ? This is what I see:

2373143f-4d9e-41d9-af92-bacaa2079a46-image.png

I wonder if you have the new version or the old one, or neither.

I'll keep testing the install on other computers. If I see an issue I'll pull this version and put 1.0.46 back.

About it showing Discord in the install log - the agent uses the Squirrel installer and I've seen it mention other applications during the install. I don't know why - it's sort of a black box to me, but I can tell you that's normal and you can ignore it. I suspect Discord also uses the Squirrel installer. I know Slack does (for example).

@trinib, I just released version 1.0.47 for Windows that will show the icon with a "Waiting for internet" message until the Internet is connected, then it will show the full tray icon menu.

Would you mind testing it? I tested it and it seems to work well.

@kellanist, great. That makes sense.

@Tiago-Ivanov-Lavinas, great. Not sure what happened the first time, but renaming that folder is like a fresh agent install.

@Adam-S It worked. Thanks.

@Russ
Perfect! Thanks for your help!

I've found out a bit more about why the taskkill command does not always work. If there is more than one instance of the browser open, only the one that Windows perceives to be active shows up in the task list. So if the browser App is minimised or you switch focus to another browser window, it 'dissappears' from the task list and the taskkill command fails.

Unfortunately I haven't found a workaround yet!

@vitormbn , if you run the same command from a CMD window does it work? Error code 1 means it's running the command but it's failing. Ideally it will fail in the same way so you can see the error. One possible reason for the failure might be you don't have admin access on your machine.

@Russ Done. Will keep you in the loop.
Thank you!

@Tony-Seaback

I replied to you here, but basically I broke the background service in version 1.0.45. I just need to upgrade the node version and update the agent. I'll do that today. Stay tuned.

https://www.triggercmd.com/forum/topic/3227/background-agent-commands-not-syncing-or-service-not-starting-please-assist-please-thank-you

EDIT: Please upgrade to version 1.0.46. It should fix the windows background service. Sorry about the bug.

@Tony-Seaback, I replied to you here, but basically I broke the background service. I just need to upgrade the node version and update the agent. I'll do that today. Stay tuned.

https://www.triggercmd.com/forum/topic/3227/background-agent-commands-not-syncing-or-service-not-starting-please-assist-please-thank-you

EDIT: Please upgrade to version 1.0.46. It should fix the windows background service. Sorry about the bug.

@Tony-Seaback, I see the problem. I broke the background service in this latest version 1.0.45. I'll produce a new version today and get back to you.

EDIT: Please upgrade to version 1.0.46. It should fix the windows background service. Sorry about the bug.

@atroguer
Yes if you setup a autohotkey and use the spy to get the x and y mouse coordinates u can

In TriggerCMD gui
“C:(path to autohotkey)” -play “C:(path to autohotkey script)”

Use ChatGPT, to help you make the autohotkey script

On desktop make a txt document
Copy and paste AHK script from CHATGPT to document
Save as
MyScript.ahk
File Type. ALL

Awesome @Santiago. Thanks for letting me know. Sorry about the trouble.

@Abel-Boby, do you see a list of voice commands on this page?

You should have one voice command for each of your triggercmd commands that has a voice word, but only if the computer is your default computer or it has a voice word assigned to it. You can set your default computer on your profile page.

In other words, these are the requirements for creating virtual devices in Google Home for your commands:

Each command must have a voice word. Each computer must have a voice word, or it must be your default computer.

@steef-van-der-Poel If you want to run a .jar executable, you need to run it using java. This is best done with a batch script like the following file:

Batch Script (launch.bat) cd C:\Users\steef\Desktop\minecraftServer java -Xmx1024M -Xms1024M -jar minecraft_server.1.21.4.jar > log.txt 2>&1

Your TriggerCMD command would have to be executing the .bat file

Something like this would work, the command comes from Minecraft's site:
https://www.minecraft.net/en-us/download/server

a66cf93e-d25e-4307-8d9a-ba761eec8e5c-image.png

@Hugoboss, sorry, I missed your original post so I'm glad you followed up.

For the 2 examples that won't run in the triggercmd agent, you said they won't run now, but they ran fine yesterday. Did you upgrade the agent between when they ran and when they didn't?

Do they run fine if you run them manually from a cmd prompt?

Please try putting this one in a .bat script like this, and run the .bat script as your command instead:

cd /d "C:\Users\username\AppData\Local\Programs\UiPath\Studio" UiRobot.exe execute --process "Discord.Join.Server"

Please test the .bat script manually too.

Also could you share the contents of this script, and the output when you run it manually?

"C:\Applications\UiPath\Robot\Starta Spel\Starta Spel\Start Game.bat"

@Matheus-de-Souza, it's showing "Command ran with error code 1" because your command is failing. Commands return error code 0 when they succeed.

To troubleshoot, it would help to get the output of your command. You should be able to see the error if you run it manually from a cmd prompt.

To open a cmd prompt, you can hold the Windows key and press R, then type cmd and press enter.
9a53f208-d7ed-45ee-b14b-dec1f499230d-image.png

If the command runs fine in the cmd prompt but it fails when you run it with the TRIGGERcmd agent, you should copy/paste your command into a .bat file and redirect the command's output to a log file, and change your triggercmd command to run the .bat file. That way you can look in the log file to see the error.

For example, you could create a script.bat file with these contents:

yourcommand > c:\logs\script.log 2>&1

This part is to make stderr output go into your log, not just stdout: 2>&1

Notice I put the log file in a c:\logs directory. You'll need to create that directory first. Windows won't let you write to a file in c:\ by default.

@Russ

THANKS! Looks like that will work for me (but I bet you knew that 🙂 )!