ALCPU Forums

!!! Attention !!!
This guide has been outdated with the release of the latest version
Download the latest version

I noticed a lot of people are trying to make Core Temp start-up on Windows Vista x64 with UAC enabled and finding it constantly asks for permission to run. Here is how to get legally get around UAC. This is all tested with 0.99.3 on Vista x64. Vista x32 should work equally well. This may seem like a long post, but actually the instructions are very detailed - you should have no problem with Core Temp or any other app with the same issue (eg. Rocket Dock) in the future.
So on with the show.

1. Run core temp and
   disable 'Start Core Temp with windows'
   enable 'start minimized'
   enable 'enable plugins' if using the vista sidebar gadget or anything that needs CT access.
   all other options are at the discretion of the user.
   Click OK.
2. Remove the program from the Startup folder or any RUN/STARTUP registry key. - Disabling 'start CT with Windows' should actually have removed the registry key entry anyway.
3. Move Core Temp.exe to a directory that is NOT 'Programs x86' or anywhere else controlled by Windows. I created a directory in my 'Users/my login name' directory called 'startupapps' and put 'Core Temp.exe' in there. (Note: strictly speaking this is not required, but some have reported they needed to do this so I simply wrote what I tested and checked as working.)
4. Launch the Task Scheduler (Control Panel -> Administration Tools -> Task Scheduler)
5. From the Actions panel on the right, select Create Task...
6. Give the Task a description of 'CoreTemp' (or anything else you feel like if you want to be cryptic)
7. Go to the Security Options on the General tab
8. Select an user account with administrative privileges
9. Select the radio button Run only when user is logged on
10. Check the box Run with highest privileges
11. Go to the Triggers tab and click New...
12. In Begin the task, select At log on
13. In the Settings options, select All users
14. In the Advanced Settings options, check the box Enabled
15. Click OK to close the dialog
16. Go to the Actions tab and click New...
17. For Action, select Start a program
18. In the Settings options, browse for the Program/Script you want to execute on startup
19. Click OK to close the dialog
20. Go to the Settings tab
21. Check the box Run task as soon as possible after a scheduled start is missed
22. Uncheck the box Stop the task if it runs longer than
23. Click OK to save and close the task properties
24. Logout.
25. Login.
26. Wait - Core Temp will eventually load - usually instantly, but may be up to 30 seconds or so.

Core Temp will now start when you login *without* any request for permissions even when UAC is enabled.

Good post.
Stickied.

Great, but since it uses a valid Certificate why does CoreTemp still ask for UAC confirmation anyway? Vista should not ask for UAC permission for correctly certified programs as far as I can understand...

And I add: it opens an orange UAC requester that means it's not certified.

Read what UAC docs says explained by Russinovich: http://technet.microsoft.com/en-us/maga ... 38019.aspx

Thanks, but the link is dead.

We’re sorry! The page you were expecting to see has been removed or is unavailable.

Visit a TechCenter from the list below, or visit the TechNet home page.

Strange... it works for me... have you tried through proxy?

Try http://social.technet.microsoft.com/sea ... nt+control
should give you those results... e.g. http://download.microsoft.com/download/ ... /58_64.pdf

News about this strange fact?

haven't had the time to research this yet.

I've seen 0.99.4 still has same behaviour and pops up an orange (not certified) UAC requester...

Yes, I currently don't have a solution for this.

In this case you will never be able to simply set the application in startup because of number of things it does at a time when the system is flip-flopping between secure states. You have the same situation with linux and to a lesser extent BSD.

If you had a pure driver starting - not problem,
If you have a pure user mode app running at startup - no problem.

Mix the two and UAC has to pop up to request confirmation that app can start.

Using the method I specified does not trick UAC in any way, it is how you pre-authorise the app and driver to run in a safe an legitimate fashion.

The actual explaination is very complicated, so I have simplified it a huge amount in this post.
The method for starting CoreTemp using the Task Scheduler is the 'legal' way for such an application. It waits until all priviledges are known and then starts Core Temp with the appropriate permissions. There is no way around this - if there were it would lead to a fully exploitable attack vector for trojans and viruses. Indeed this type of attack is the only sort of thing that works on Linux and BSD. And yes, I know nix and Windows are different because I do Kernel programing in both!!!!

Thank you for the great explanation!

aeomer wrote:In this case you will never be able to simply set the application in startup because of number of things it does at a time when the system is flip-flopping between secure states. You have the same situation with linux and to a lesser extent BSD.

If you had a pure driver starting - not problem,
If you have a pure user mode app running at startup - no problem.

Mix the two and UAC has to pop up to request confirmation that app can start.

Using the method I specified does not trick UAC in any way, it is how you pre-authorise the app and driver to run in a safe an legitimate fashion.

The actual explaination is very complicated, so I have simplified it a huge amount in this post.
The method for starting CoreTemp using the Task Scheduler is the 'legal' way for such an application. It waits until all priviledges are known and then starts Core Temp with the appropriate permissions. There is no way around this - if there were it would lead to a fully exploitable attack vector for trojans and viruses. Indeed this type of attack is the only sort of thing that works on Linux and BSD. And yes, I know nix and Windows are different because I do Kernel programing in both!!!!

This doesn't change the fact that CoreTemp pops-up an Orange UAC requester: it means the sys identifies it as not certified, as it should be...
There is something wrong IMHO....

Hello, rolloLG.

The orange UAC requester will not pop up if you follow the instructions at the beginning of this thread. As I said, as long as the driver is signed it will be allowed to run, but running it from a user level app is a security issue and hence the the UAC message. Follow the instructions and the whole thing is 'pre-authorised'.

If the driver where installed separately from the Core Temp application then there are valid ways around the UAC requester, but as they are bundled together - which in my opinion is the correct option for a smallish app - then you need to follow the installation instructions.

That's just the way it is - and in this case it is certainly correct, if annoying. Try spending a day with driver access stuff in KDE and you will start to find UAC ain't that bad - Though I must say Gnome does it better, and the latest Mac (leopard) is just plain annoying (like UAC). Maybe Snow Leopard will show a better way

Hi all, i just joined today to ask about an issue i have running both Coretemp
9.4 and the beta 9.5 in Vista Home Premium sp2. I have Core Temp running as a scheduled task and it runs without UAC prompt only it is only running in Task manager and Not in the System tray. So i have to kill it and restart to get it in the tray. How come?

Not quite sure why it would happen.
Did you set the program to start minimized? Because if Windows starts Core Temp before the taskbar is loaded and it's set to start minimized, you won't be able to bring it back up.

The Coolest wrote:Not quite sure why it would happen.
Did you set the program to start minimized? Because if Windows starts Core Temp before the taskbar is loaded and it's set to start minimized, you won't be able to bring it back up.

Yes. It is always minimized to the tray. The first time I restarted the computer after making the Scheduled task yesterday it worked fine.
Today I have rebooted twice and both times it is running but only in Task manager, no icon in the tray.So load order may have something to do with it huh?

Most likely, I see what can be done.

The Coolest wrote:Most likely, I see what can be done.

Ok thanks.

The Coolest wrote:Not quite sure why it would happen.
Did you set the program to start minimized? Because if Windows starts Core Temp before the taskbar is loaded and it's set to start minimized, you won't be able to bring it back up.

Follow-up . This morning the 9th I booted my computer twice and both times Core-temp was in the Tray where it belongs. So you are probably right that is a boot anomaly which I will live with because I only reboot my computer once a month on average. Thanks.

This doesn't work if you run Seven as a standard user. Even if you try to start Core Temp as an administrator with the Task Scheduler, Windows is reporting an error "can't load driver". But I found a workaround, you need 3 scheduled tasks, but it works.

1. Task: Start Core Temp with the Account "System", this loads the driver without prompting an error but the process is not interacting with your desktop
2. Task: Use pskill (sysinternals) to kill the started Core Temp process (delayed about 30 seconds after login)
3. Task: Start Core Temp again with your standard user account (delayed about 40 seconds after login). No driver errors is popping up and Core Temp runs fine.

I needed the whole evening yesterday to find this solution

Of course, you need to be an Admin for Core Temp to work. It's the same even in normal situation when you just start Core Temp manually.

Thanks jack_steel for the workaround! It works for me too. For the second task I used the Windows tool "taskkill" instead of "pskill":
taskkill /f /im "Core Temp.exe"

Perhaps it would be a little easier if Core Temp had an option "OnlyLoadDriver" or something like that. Then the second task would be unnecessary.

Wouldnt be possible to create two (or more) executables? One for driver and one for app... I only need the G15 module or windows gatget, so i run the driver and then exe with G15/gadget module. And if i need a Core Temp gui, then i run another exe...

Sorry for my english & thanks for the great app

Here's what I did to get it to run at startup in Win7 x64.
Followed the steps from the OP(original post) except I put the folder on the root.
Then I changed the security on the CoreTemp folder, gave the "Users (username\Users)" Full Control.

Hope this helps.

This is a great program and a nice tutorial to have it run at start up - I got this to work for me in Vista. Though, is there a way to have it start up hidden? I have tried to have it run minimized but that doesn't work - I still have to select File > Show/Hide.


Thanks.