If not, please try renaming your c:\Users\(your user)\.TRIGGERcmdData folder, and then re-run the triggercmd agent. It will prompt again for the token.

I formatted my computer, and when I tried to use TriggerCMD, it didn’t start automatically. I’ve tried all the solutions mentioned here, but nothing works.

I don't use the background service (aka the TRIGGERcmdAgent windows service). I'll enable that and do more testing, but that shouldn't effect the tray icon because it's only for the foreground agent.

FYI, the background service is not necessary unless you want to be able to run command while you're logged out. Most people don't need it.

In short if no internet at startup, triggercmd does not start properly. I don't know if something else can cause a conflict at startup&no-internet with triggercmd. Really weird.

Startup with no internet - issue
After startup issue, connect to internet - still issue
Startup with internet - works
After startup issue, I force close and restart with internet - works

OS Name: Microsoft Windows 10 IoT Enterprise LTSC
OS Version: 10.0.19044 N/A Build 19044
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free

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

EDIT: I confirmed if the agent starts and can't access the Internet, it closes. It should keep trying to connect, so I'll fix this soon.

EDIT2: Actually, when I went to fix this I found that the agent does start, but it doesn't show the tray icon until the Internet connects. Fortunately that's a smaller problem, but I think it should show the icon with or without Internet. I'll work on that for next the agent version.

##### But easy work around using task scheduler.

1. Open Task Scheduler

• Start Menu → Task Scheduler

2. New Task

• Action: Create Task…
• Name: TriggerCMD Agent
• Security: Run only when user is logged on
• (Optional: check “Run with highest privileges”)

3. Trigger

• Click Triggers → New…
• Begin the task: At log on
• Settings: Specific user or Any user → OK

4. Action

Actions → New…

• Action: Start a program
• Program/script:
  C:\Users\Admin\AppData\Local\triggercmdagent\TRIGGERcmdAgent.exe
• OK

5. Condition

• Go to Conditions tab
• Check Start only if the following network connection is available
• Select Any connection
• OK

6. Finish

Click OK to save
(Enter your password if prompted)

LOVE THIS SOFTWARE . Hope it never dies . paying for full features

You install it using this "Install Background Service"

Set your commands as background commands like this:

The normal forground agent starts up when you login, and it runs commands non-elevated.

If you still want to use a shortcut with that "Run this program as an administrator" checkbox checked, you'll need to disable UAC, and you'll need to check the box on the TRIGGERcmd Agent shortcut in this folder:

C:\Users\Carmelo\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

This article shows how to quickly open that folder with shell:startup.

without checking run as administrator, triggercmd start correctly at boot

Are you using this checkbox on the shortcut? If so, how are you running that during startup?

@Russ For me it never broke up to now