@Renan-J, please make sure your second computer has a "Voice Name" because if it doesn't, it won't work with the Alexa skills.

Only your default computer works with the Alexa skills without a Voice Name. Your first computer is the default computer by default.

@Gabriel-Martins you could try the new version I just released, but I don't have confidence it will solve that error.

Do you have admin access on your Windows PC? What Antivirus do you use?

@D0llyy, yes there are many tools for many OS's that can send the magic packet to wake up another computer.

Windows: https://www.nirsoft.net/utils/wake_on_lan.html
Mac: https://formulae.brew.sh/formula/wakeonlan
Ubuntu: sudo apt-get install wakeonlan

@Mariana-Castro, if you didn't save your c:\Users\(your user)\.TRIGGERcmdData\commands.json from your previous Windows load, you've lost your commands.. You should delete your computer from your TRIGGERcmd account so you can recreate it from your new Windows load.

For security reasons, TRIGGERcmd does not store the actual commands in the cloud - they only exist on your computer in your commands.json file.

@Luigi-Marco-Silvestrini, I think I fixed it but I'm not 100 percent sure because the error showed up so rarely. Please upgrade to the latest version (1.0.36), and please tell me if you ever see the error again.

Thanks @Javier-Juarez, I'll look into Binance. I tried adding Stripe but they cancelled me after a couple weeks because a customer claimed they didn't subscribe.

@Mauro, there's no built-in way to open the GUI Editor using a command, but if you want I could build it into the next version of the agent.

I remember you did it this way, so I assume you're looking for a simpler/cleaner method.
https://www.triggercmd.com/forum/topic/2716/macro-to-open-triggercmd-gui?_=1718324644863

@Luise-Fernandes, I'm not sure, but please try deleting this folder, then re-run the "TRIGGERcmd Agent" app.

c:\Users\luise\.TRIGGERcmdData

@Ben-Klinger Awesome. Thanks.

@James-Clark, great! Thanks for confirming you're all set.

@Joao-victor-0 That's not TriggerCMD causing the problem, it's another device connected to your PC that's causing it to power back on. If you run the command outside of TCMD, it will do the same thing.

Try unplugging your USB devices and see which one is reawakening your PC.