TRIGGERcmd not starting at boot

Program is displayed correctly in Task Manager but it simply refuses to start at boot, rendering it useless completely.

Adding a registry key to start at launch correctly creates a duplicate boot entry in Task Manager but fails to solve the problem.

Is this known? Any help?

Russ

@TheConfax, when you login, TRIGGERcmd should startup, and you should see it as a tray icon in the lower-right near your clock when you click the up arrow.

If you right-click that tray icon, you can also install the background service which starts up when your computer boots (even before you login). That background service runs your background commands.

You mentioned you see TRIGGERcmd in Task Manager. That could be the normal foreground agent or the background service if you installed it. Have you checked for the tray icon?

Hi @Russ

Sorry for the late reply. No, the program is not displaying any tray icon, that is the point.

I said that the TRIGGERcmd entry is correctly present in task manager for startup, but the program is not starting up at boot and no tray icon is shown. If you have any advice or need some information from me, I am available for troubleshooting.

Thank you.

Russ

@TheConfax, that is strange. Did the prompt for the token even come up right after you installed the agent?

You could try a couple of things:

Kill the one you see in task manager, and re-run TRIGGERcmd Agent, to see if it shows up.
Delete your c:\Users\theco\.TRIGGERcmdData folder, then kill and re-run the agent. At that point it should prompt you for your token. If you already have the computer in your account, you'll want to delete that before entering the token so it doesn't create a duplicate.

@Russ sorry again for the late reply but I'm not getting mail notifications from the forum

I can try to delete the data maybe, but just to get things straight, the program is working fine, I'm using it with Siri Shortcuts, it just won't ever start at boot by itself! The screenshot is from the "startup" sectionin task manager, when I run it manually the process comes up and the tray icon comes up and all works fine, so is a startup only problem.

I told you all that because solution 1 seemed like i had the process and not the tray icon, and that is not the case, everything is fine, that is the startup section of Task Manager.

Should I delete the folder?

Russ

@TheConfax, no, don't delete the .TRIGGERcmdData folder. It probably won't help this problem. Now I understand it's just a startup problem.

I don't know why the normal startup process isn't working, but I think this work-around will work:

Copy the TRIGGERcmd Agent shortcut to the Startup folder.
From: %appdata%\Microsoft\Windows\Start Menu\Programs\TRIGGERcmd
To: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp

To get to the From folder, search for TRIGGERcmd, right-click it, and click Open file location.

I tested this on my computer and it worked for me.

@Russ said in TRIGGERcmd not starting at boot:

%appdata%\Microsoft\Windows\Start Menu\Programs\TRIGGERcmd

Hi, @Russ

That is precisely what is not working, my startup folder looks like this:

As you can see there are other programs that are starting fine at boot, but triggerCMD is never starting!

I tried inserting the link in both startup folders (common and user), and as a registry key to launch at startup too, and none of this is working...

Russ

@TheConfax, man that is odd. I've never seen this before. It works fine if you run it manually right?

I don't get it. You could try uninstalling and re-installing it. That won't delete your data.

I don't have a lot of confidence it will fix it, but it's worth a try.

@Russ yeah I know that's odd, that is why I posted here on the forums, I was hoping that it was a known issue...

I'll try reinstalling then! Thank you anyway!

hdegenaro

Hello. I'm also having the same problem. I've done the same tests and it didn't work. In my case, I'm in Brazil and I use Windows 10 Professional x64. It is worth mentioning that when I create the shortcut and place it in the start folder, the shortcut only works if I click on it. Does not work at startup. I like the program is very useful, I even paid for the license to enjoy another PC. I will be very happy if you find out why this is happening. Thanks.

@hdegenaro Yes, the problem never solved for me too, you can put a simple .bat script in the startup folder pointing to the folder where TriggerCMD is installed to workaround, with the bat script launches every time.

If you don't want to see a CMD window at every boot, you can convert it into an exe and make it a background software.

Hope this helps you, this problem must be solved though.

hdegenaro

@TheConfax Thanks for answering. I will do this and I will return to speak if it worked.

hdegenaro

@TheConfax Hello, my friend ... I would like to say that it worked for me too. Thanks for the tip!

hdegenaro

@Russ There is a way to fix this problem in your program so that it starts with Windows? The installation of the "background service" does not work either. Isn't this a bug? Sorry for the questions.

Ivan Kuler

@Russ ... Same issue here. Seems to have a incompatibility with a app from MS at the Store (Phone).

Russ

@Ivan-Kuler and @hdegenaro, I think it is a bug, but it's difficult for me to fix because the bug doesn't happen for me. For me, on all of my computers, it always starts up automatically when I log in. If I could see the bug myself, I could probably fix it.

Ivan Kuler

@Russ for me no worries at all... but happen in 2 of my computer already.
The workaround to use a batch (in my case a Ahk script compiled in Exe file works..

Meanwhile, I’m seeking to figure out is is a incompatible with a process running... the App Your Phone from MS Store.

Keep you aware..

Br,

Russ

Thanks @Ivan-Kuler.

@Russ I just wanted to check in again to say that I'm noticing that the .bat workaround is not working for me every time lately... have you tried to dig into this? I can provide you troubleshooting info if you need it.

Russ

@TheConfax, honestly I forgot about it, but I'd like to solve it if I can.

I wonder if the problem is specific to certain non-english versions of Windows 10. Are you running an Italian version of Windows 10?

I'm confident I can solve it if I can reproduce the problem. I'd like to create a virtual machine running Windows 10 with the Italian version (if that's what you're running). I tried installing an additional language on my Windows, but that didn't show me the problem.

Right now I'm downloading an Italian version of Windows 10 ISO using the media creation tool I downloaded from here:
https://www.microsoft.com/it-it/software-download/windows10