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

    Is Trigger and dead?

    Scheduled Pinned Locked Moved General Discussion
    2 Posts 2 Posters 644 Views 1 Watching
    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.
    • H Offline
      hellomiakoda
      last edited by

      It has been a very very long time since TriggerCMD actually ran on my computer. It's still installed on my computer, it's just times out at boot ever since a particular update. Is TriggerCMD ever going to be updated again, or is this cool thing just gone and dead?
      I used to use this all the time, but... once day, my OS was updated too far for it, and it's never worked again.

      RussR 1 Reply Last reply Reply Quote 0
      • RussR Offline
        Russ @hellomiakoda
        last edited by Russ

        @hellomiakoda, how can you tell it's timing out? Is that what it says in your %userprofile%\.TRIGGERcmdData\debug.log file?

        Can you confirm you're running Windows 10 and the latest version of the TRIGGERcmd agent?

        TRIGGERcmd is working fine for me, and a lot of other people. I've updated my Windows 10 PC to the latest updates. I'm also using the latest version of the TRIGGERcmd Windows agent.

        These are a couple things you could try:

        1. You could try removing and re-installing the agent.
        2. Some antivirus software breaks the TRIGGERcmd agent. You could try disabling it temporarily to see if that makes it work.
        3. You could reset your data with these steps:
          a. Rename your %userprofile%\.TRIGGERcmdData folder
          b. Go to this page https://www.triggercmd.com/user/computer/list and delete your computer.
          c. Right-click your TRIGGERcmd agent tray icon and click Quit
          d. Re-run the TRIGGERcmd Agent and log it in.
          e. Copy your commands.json file from your backed up .TRIGGERcmdData folder to your new .TRIGGERcmdData folder to restore your commands.

        Russell VanderMey

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • First post
          Last post