TRIGGERcmd not starting at boot

Russ

@TheConfax, bad news. It worked fine for me. I installed the TRIGGERcmd agent and rebooted my Italian version of Windows 10 and it automatically started up.

@Russ To be honest is not a constant thing, without the fix it starts like 1 out of 10 attempts, with the .bat fix it starts like 19 out of 20 attempts.

Try rebooting some times, if unsuccesful in breaking it, try shutting down and powering on the virtual machine some times, both with and without fast startup enabled.

Russ

@TheConfax, I tried rebooting the VM many times and I have not seen the problem.

I did an experiment though - I disconnected the VM from the Internet, then quit and re-launched the TRIGGERcmd agent, and I found that it automatically quit because it couldn't connect to the server.

I wonder if that's what's happening to you. Is it possible your TRIGGERcmd agent is launching before your computer is connected to the Internet during boot?

@Russ Yes, it is very much possible, because my Wi-Fi card connects only after user login.
In my .bat fix i included a 30 second delay, that could explain why even that sometimes is not working.
You could try implementing a little loop at boot checking for network more than one time and it should be fixed ^^

Russ

@TheConfax, ok, yea I think I can fix this.

Thank you @Russ !
Let me know when it's done and thanks again for the very useful application!

Russ

@TheConfax, I fixed it. Please update your agent. Now it will retry every 10 seconds if there's no Internet. I tested by rebooting the VM while it was disconnected from the network, then I enabled the network a while after the agent started. It connected within 10 seconds.

@Russ Thanks for the fix! I will test it during the next days and I'll let you know if it hangs again, hopefully should be ok.

Paulo Filho

I'm from Brazil and I have the same problem, the fix doesn't work here. If anyone knows the fix about the .exe (.bat file in the background doesnt appearing the black box of CMD) help me please.

@Paulo-Filho Try uninstalling and removing the .bat fix, then reinstall the latest version and make sure it is in the automatic run folder.
It is your PC connected to the internet at launch?

@Russ For me it never broke up to now

Paulo Filho

@TheConfax Yes, its connected at launch. The .bat fix finally worked here, now how i can transform in a .exe to not show the cmd in the intro?

@Paulo-Filho You can use any exe-bat converter. But Russ updated the software, now it should work even without the bat fix

Mark Hollis

@Russ i have a startup problem on windows 10, if i set triggercmd to launch as administrator, it won't launch at window startup, you know why? thanks for help

Russ

@Mark-Hollis, how are you trying to run the agent as administrator during startup?

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

Mark Hollis

@Russ yes exactly
the link to exe is in this folder C:\Users\Carmelo\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\TRIGGERcmd

without checking run as administrator, triggercmd start correctly at boot

Russ

@Mark-Hollis, I actually included a feature to run the agent in background mode in the context of a Windows service that starts up on boot. It runs your background commands elevated.

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.

Mark Hollis

@Russ i already have uac disable, and ticked administrator to that shortcut in that folder, but this way don't start when windows 10 start