@Russ There has to be a way. Many systems, like VNC for example, use this feature.

@Carlos-Junior, you could create a script with two commands in it like this:

taskkill /f /fi "USERNAME eq %USERNAME%" /fi "WINDOWTITLE ne" shutdown /s /f /t 0

Then your command would run that script with a command like this:

c:\scripts\close_all_shutdown.bat

If you don't want to create a script, you can generally run multiple commands with one command line by separating the commands with && like this:

taskkill /f /fi "USERNAME eq %USERNAME%" /fi "WINDOWTITLE ne" && shutdown /s /f /t 0

@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.

@Diego-Ulises-Pérez-Ruiz, maybe you need to specify the full path to nircmd.exe in your command, like c:\tools\nircmd.exe ...

Also, by manually, I assume you mean when you run it manually from the command line it works. What if you run it manually via TRIGGERcmd using the green Trigger button on the website, or from the green Play arrow in the GUI Editor ? We should make sure those work before attempting Alexa.

Thanks @Xander. I'm glad that worked.

@Russ
Perfect! Thanks for your help!

@Russ
the restart and status check worked!

I used apt for the removal and node update.

Thanks again for your help!

@Oliver-R Thanks a lot

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.