Asus GPU Tweak II Not on Startup List.

ScarletHY

Commendable
Sep 8, 2016
32
0
1,560
Since I installed Win 10 Home on my new build, I just couldn't get GPU Tweak II to auto start when Windows starts. I'm wondering if anyone has the same problem here...

The program is not on msconfig nor is it on Startup, which is weird 'cause I had that in Startup Programs in Win 7.
However, it does seems to work every time I change the setting, but only for 1 or 2 startups.

So here are a couple things I've tried:
-Clean install. (with GPU Tweak Remover)
-Install Win 8.1 version of GPU Tweak II.
-Put the shortcut to "C:\Users\UserName\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\ASUS" (don't know why).

Until now I'm starting to think it's a problem with either Windows 10 or Asus.... is there any way that I can force it to startup with registry?

Many Thanks.

My rig:
-Intel i7-6700k stock
-Asus Geforce 980ti Strix stock
-Asus Maximus Hero VIII
-2x8GB Corsair Vengeance LED 3200 stock
-Corsair Force LE 960GB TLC SSD



 
Solution
Since last update, win 10 only lets signed drivers run. This is something Asus need to fix as the change to only accepting signed device drivers was made a year ago and Microsoft only just started enforcing it. Asus needs to release a new version compatible with the latest version of Windows 10 and this problem will go away.

Similar thing happens with samsung Magician software currently, the drivers aren't signed so win 10 refuses to run them.
In GPU Tweak options, have you ticked Automatically start GPU tweak 2 when I logon to Windows under both GPU Tweak 2 startup and GPU Tweak monitor start up? As that is what it takes to get them to load at start up on my PC and I haven't noticed them not load once its set like that

Running Version 1183 - some of the earlier versions had problems remembering fan settings but they fixed that.
I only use it in summer as I set fans to always run as the added cooling helps.
 


Yes they are all checked, sorry I did not mention it earlier. My version is 1.3.6.0; should I downgrade to 1.1.8.3?



 
It seems its a bug with recent versions

Can confirm this update does still not auto start for me despite having this setting on in the settings menu.
What is causing this issue? Anyone know?
It also seems a little buggy. selecting OC mode seems to switch between Auto and User defined fan profiles.
Is there anyway to clear any user created fan profiles it may be picking up on?

https://rog.asus.com/forum/showthread.php?87274-GPU-TWEAK-II-version-1-3-4-1-is-out

depending on your card, you should be able to run a version prior to 1.3.4.1 and it should work as expected/

I followed a link to latest version of GPU Tweak and it led to a Asus site where my card wasn't listed... then did a google search for card and found it on another Asus site and saw that the version you have is latest for my card too. I won't update it till I know its fixed I guess. I don't need it for a few months.
 


I see, thanks for the digging. What you mean is there is a bug recently and I should not upgrade that for now, right?
I'll try other older versions and see if they work as intended, thanks.
I'll check back to see if I can find anything.. but it's pretty late here and I'll do it tomorrow.

Again, thank you for the help.
 
Looks like I have found something just before going to bed...

So I found two file locations for Asus (which I cannot tell the difference as to why there are two):

-C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ASUS
-C:\Users\UserName\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\ASUS

I removed the GPU Tweak shortcut from the first location and added that to the second (as the third method that I tried); apparently it seems to be working. However, I'm not sure how long that will last... will check back.
 
1st location is where program starts from, 2nd location is for settings associated with you and the program. 2nd is your profile. Something broken as the start up of program should be auto and you shouldn't have to add it to roaming as well.
 


I see what you mean, and yes what I did does not work after a day...
Anyway, I'm rolling back one version. We'll see what happens.
 
Rolling back didn't work. I'm solely guessing it's a bug with the operating system. Anyway, I've added the shortcut to Startup folder and disabled LUA in the registry. Hope this will do the trick.
 
Just wanted to say I am having the exact same issue...

MB - Asus Rog Hero Alpha
GFX - Asus Rog GTX 1080

Have to manually launch Asus GPU Tweak every time I start the PC...
 
My GPU is too old for LED, my case has no lights or side window, and I didn't even know GPU Tweak had that feature.

Shame program doesn't auto update its version as you will have to check for an update every week I guess. The rog post I linked above shows devs aware of the problem, but nothing new for 2 weeks.
 


After dayz of blindly checking; I finally found something that relates to the issue.

Basically the UAC is preventing it from starting, probably due to think GPU Tweak is a not trusted software.
Simple fix is just go to registry and disable UAC.... HOWEVER, now if you are using Win 10 Home, you'll most definitely run into problem that every Microsoft BASIC applications, like photo viewer, will not work. You will get a message saying the application cannot be opened using the administrative account..... something pretty bs and weird.

So then you'll have to enable UAC again... and then GPU Tweak won't work....

If you have Win 10 Pro and up, you can simply go to group policy editor and disable (a thing I forgot the name) to let admin bypass the restriction.



So simply, MS is doing something really really annoying there.

 
Since last update, win 10 only lets signed drivers run. This is something Asus need to fix as the change to only accepting signed device drivers was made a year ago and Microsoft only just started enforcing it. Asus needs to release a new version compatible with the latest version of Windows 10 and this problem will go away.

Similar thing happens with samsung Magician software currently, the drivers aren't signed so win 10 refuses to run them.
 
Solution


I see, thanks for the information.
.....looking at both MS and Asus.... that will probably not happen soon....

Weird thing is, it doesn't seem like many people have that problem even though they are also using Win 10.

Anyway, looks like I'm either gonna wait a bit, or re install windows and see if it magically goes away. (I messed up some drive security policies and tweaked too many registry, which really annoys me; re install os will definitely happen anytime I have some days off)
 
I'm using the GPU Tweak II 1.3.9.7 version. And here it seems to be extremely weird:

- It starts automatically when I do a normal boot f.e. after a reboot (new start / cycle directly out of windows).
- when Windows 10 does the hybrid boot after a shutdown - then GPU Tweak II will not start at logon. I have to start it manually.

Is this also because of the UAC and the not signed drivers?


I run Win 10 Home newest updates
 
A restart is when it loads everything from hdd, that would be when it should have troubles with drivers. Or in fact, both... it shouldn't be just choosing one type of load.

That sounds like GPU tweak itself doesn't like fast startup. or maybe update motherboard drivers
 
I had the same problem. Then I found instructions in a comment section for forcing the startup of applications from the registry. Here's the original comment:

//--//

"there is much better method to make program start with windows.

this is adding your program to windows regestry.

it makes your program start as soon as win starts.

this method is used by most software like antivirus,torrents,etc.

follow the instruction to add your program:

1) open regedit (run ->regedit).

2) goto,

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run (for current user RECOMMENDED)

or

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run (for all users)

3)in toolbar goto Edit->New->String Value

4)name the new string value. this will be the name of your startup program. you can use any name or or few words eg- my startup program.

5)double click new string value or modify.

6)under Value Data,write location of youe startup program.

click ok and you have done.

you can enable/disable through task manager also"

//--//

I've encapsulated the location of the application with " ". So the Value Data contains the following:

"C:\Program Files (x86)\ASUS\GPU TweakII\GPUTweak.exe"

Hope it helps.
 
Thanks chrisrezende for your answer. I tried exactly what you worte - the only difference is, that I had "GPUTweakII.exe" in the key, not "GPUTweak.exe". Do you know what's the difference? It seems to start the same program... but with GPUTweakII.exe it didn't work. Do you think it will be different with GPUTweak.exe?
Because for now I stay with the 1.1.8.3 and it works normally. That's why I have some doubts to try it again at the moment. Could you please test if there is a difference between what exe you autostart? That would be very nice of you. Then I can safely try it again. Last time it ended up with a full restore of drive C:\... because of system recovery doesn't work either at the moment. Even not in safe mode... but that's a different story.

Btw -> my mobo's a ASUS Maximus Extreme VI -> no new bios available since over a year...
 
Hi AgRessoRoNE-13,

I've tried GPUTweak.exe and then GPUTweakII.exe in the key. Both worked fine and I've ended up with the exact same result when starting the program. However, I forgot to mention an important detail (sorry guys). I'm using Windows 8.1, not Win 10. Maybe GPUTweakII.exe won't work under Win 10 autostart registry for some reason.
 


It's not in startup because it's not supposed to be. It launches via the Task Scheduler, probably to get past the UAC startup barrier.

If anyone is still having problems with it, reply here and I'll post detailed instructions. In the meantime, the short instructions are: When you configure it in Task Scheduler, use the Administrators group as the credentials, or it will silently fail. (That was the Asus developer's mistake.)

------------------------------------------------

Well, here we are back to this aggravating thing. My machine worked since before I posted here. Today I installed Creators Update, and it started the issue again. If I find out why, I let you know here. I think it's a different reason this time. It might have to do with the longer amount of time it takes to log-in in to the new version of Windows. (It's triggered by the login.)