Since I installed Windows 7, Startup Organizer 2.9 doesn't start-up although it is configured to do so. Is W7 preventing it ?
Check box "Start with Windows" is on.
It seems as though the programs that SO starts up do not run elevated - which is a good thing in most cases. But if I run (right click - run) from withing SO, programs do start elevated because SO is running elevated. My guess is that during boot, ctrl.exe somehow manages the startup programs and even though SO is started elevated, the programs it executes on boot (via ctrl.exe?) do not start elevated.
Maybe a future update will simplify this?
Would it work correctly now?
Maybe it starts then exits? How else could you explain ctrl being invoked???
I don't mind starting it via Task Scheduler. That avoids me having to answer the "do you want to allow" prompt when it's started.
So having it not run - or stay running - on startup is not an issue for me. Ctrl.exe is important and it somehow starts and runs all my controlled items as normal - not admin. Further discussion of that in my other post.
Installed SO, verified it was set to...
run in system tray
minimize on start
X button minimizes the main window
Rebooted. SO is not in task manager nor in the system tray. But msconfig shows an 'enabled' entry for it. How is this possible?
SO. I moved SO to controlled start-up. When I booted and logged in I got the permissions dialog for SO, answered yes, and it loaded!
Weird. So the workaround is to place in in controlled start-up. BUT, I will not do this because I don't want to deal with the permissions prompt. Windows 7 Task Scheduler is still the easiest way to run SO as admin on start-up with no prompts.
Does Startup Organizer invoke CTRL.EXE? I'm thinking is must. If true, then SO must be running on start-up, at least just enough to invoke CTRL before exiting. I even turned off run at start-up and the controlled start-up items still get processed. I associated a sound with controlled start-up items and I can hear that sound even with SO Load at Start-up NOT checked. I'm thinking now that SO must run twice. Once as normal to invoke CTRL, then again as admin to begin monitoring the system. But as I stated above, this second launch doesn't take place unless SO is in the controlled start-up section. Last but not least, when it is started after being placed in the controlled start-up section - it runs as admin. That's contrary to CTRL's behavior. All of the programs started by CTRL run as a normal user. But not in this particular case. Of course that's not a problem because you want SO to run as admin. I just can't explain why it does when CTRL apparently launched it!
SO.exe always starts as admin - no matter how it gets started. This is because it contains "manifest" that tells the system that it should be run as admin.
So the only weirdness remaining is why SO will not start when msconfig indicates that is will be run. Apparently on your system is DOES start?
Still, not an issue for me because Task Scheduler is the best way (currently) to start it - without any prompts to grant permission.
I'm not going to spend any more time on this particular issue though because I use Task Scheduler to start it elevated which avoids the permissions prompt.