Cumulus Support

Just moved my Cumulus PC to Windows 10.

Cannot for the life of me get it to load the programs on Startup. Tried the old W7 method of putting the shortcuts in the StartUp folder but it would appear that W10 will not start programs nneding Admin rights on StartUp as it is a security risk.

So switched to Task Scheduler and that doesn't work either, despite the masses on Google saying it would !!

Anybody achieved this and if so how?

What were the problems with Task Scheduler?
I have it starting lots of programs with elevated privileges.

I have my CumulusMX start up as a windows service in Windows 10 - works well for me.

See viewtopic.php?f=27&t=15780&p=128028&hil ... ce#p128028

Got this to work thank you. But the weirdest thing neither program is showing up on the desktop but they are running in the Task Manager???????????

If it is running as a service you will not be able to see the console interface.

OK Mark, thanks I will check that.

Mark it is not running as a Service as it doesn't appear in Services.

Task Manager has it in a Group called "Background Processes". The only way to stop it since I have no Application window is to tell Task manager to End Task, but I am guessing that will not be a clean close?

Mine on W8 starts via task scheduler; running at elevated privledges & at logon plus multiple triggers.
I've also created a shortcut on the desktop to launch it from there in the same manner as opposed to a normal shortcut.

This means it always runs in a Window titled "C:\CumulusMX\CumulusMX.exe"

That means that when it comes to closing MX, I am able to run an AutoHotKey script that puts the focus on the above Window & sends it the Ctrl-C keystroke so it shut down correctly.

The AutoHotKey Script is discussed in this thread.

Cheers.

water01 wrote: ↑Thu 27 Feb 2020 5:36 pm
Task Manager has it in a Group called "Background Processes". The only way to stop it since I have no Application window is to tell Task manager to End Task, but I am guessing that will not be a clean close?

And you used the option "Run only when user is logged on"? If you use "Run if user is logged on or not" then it will run in the background.

Theory here, as I run on Linux, but I think I'd run cmd.exe with Cumulus as a program, that way if it crashes the window will not close and you can read the messages.
Something like: cmd.exe /K c:\cumulus\CumulusMX.exe

Thanks Mark, solved it.

I had it as "Run if user is logged on or not" as when I switched it to "Run only when user is logged on" it would not start automatically.

So I found out how to make Windows 10 autamatically log into a user without a password, then switched it "Run only when user is logged on" but it still didn't work.

So I tried something you said earlier about delaying it to wait for Windows 10 logging in (only 1 minute) and it works !!

They have made the Start Up bloody difficult to use in Windows 10!!