• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
TRIGGERcmd
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Triggercmd doesn't install windows 64 bits

Windows
3
3
362
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I
    Igor Marinho
    last edited by Igor Marinho Mar 30, 2024, 1:55 PM Mar 30, 2024, 1:32 PM

    minha alexa parou de reconhecer os comandos do trigger, fui reinstalar e isso aconteceu, alguém pode me ajudar?

    já deletei a pasta de arquivos local .triggercmd e também desabilitei o antivirus... o erro persiste

    7b62e781-6f58-42aa-ad1a-c7f5d797b323-image.png ac786ef9-1455-4114-9dfd-c1a842bfb363-image.png

    X R 2 Replies Last reply Mar 30, 2024, 2:09 PM Reply Quote 0
    • X
      Xander @Igor Marinho
      last edited by Mar 30, 2024, 2:09 PM

      "2021-08-26 19:54:08 Program: About to install to: C:\Users\User\AppData\Local\Discord"
      "2821-08 1-26 19:54:21) Apply 21 ApplyReleasesImpl: Updating shortcut C:\Users\User\Desktop\Discord.Ink"

      @Igor-Marinho Looks like you're installing Discord, not TriggerCMD.

      1 Reply Last reply Reply Quote 0
      • R
        Russ @Igor Marinho
        last edited by Mar 30, 2024, 6:08 PM

        @Igor-Marinho, Alexa talks to the TRIGGERcmd servers, and the TRIGGERcmd servers talk to the agents. Next time, please test the agent first by running your commands from the triggercmd.com website. If that works, there's no need to troubleshoot the agent and you can move on to troubleshooting the Alexa integration. Also if you do have an agent problem, instead of uninstalling/re-installing it, you should try restarting it.

        We can troubleshoot Alexa after you re-install the TRIGGERcmd agent and test it from the triggercmd.com website.

        Please try deleting your C:\Users\(your user)\AppData\Local\triggercmdagent directory, then re-install the TRIGGERcmd agent. Hopefully that will work around the installation error.

        Russell VanderMey

        1 Reply Last reply Reply Quote 0
        2 out of 3
        • First post
          2/3
          Last post