I think I found a solution to circumvent the inadequacy of AI Suite (at least for the first bug).
Here goes: I don't know where the issue lies, but it seems to go away if I stop and start again the AsusFanControlService. And since doing that manually would be almost the same as fiddling with AI Suite, I decided to automate it.
I had to enable Administrator since it's disabled by default in Windows 10. Here's a guide to do it. Set a password for it (it seems that this doesn't work with a blank one; moreover it's not a good idea to have an unprotected admin account).
Then I went into Task Scheduler and created a new task. It launches on resume from stand by. To do so, add a trigger and set it like this:
Next up, create a batch file with the following content:
Save it wherever you like (as .bat of course). I placed it in the same folder as AISuite3.exe for the sake of convenience. Back to Task Scheduler - go to the Actions tab and select that batch file (not pictured since there's nothing special about that step). Go to the General tab. Set it like this:
Upon clicking "OK" you will be asked for credentials. Enter "Administrator" and the password for it.
I just added another trigger ("At startup") since this seems to also be needed when restarting Windows. Haven't tested it, but it should work.
That should be it. Really hope this helps someone.
As for the second bug - I guess I'll have to fiddle around with the XMLs (found in C:\ProgramData\ASUS\Dip\FanXpert\Profiles). Now that I look at them again, it seems that saving a user profile doesn't save weights for any fan. Open a user profile side by side with a default one (the ones with "ASUS" in parenthesis) and you'll see that the user profile lacks the "weights" tag under a "fan" tag.
I'll play around, maybe I'll try to copy the weights from another profile and see if that works upon changing profiles. I also hope I'll find a way to switch profiles programmatically (i.e. without launching AISuite).
Shame on me for not coming up with this earlier. Shame on ASUS for apparently not caring about software. I doubt that any time soon I'd be buying hardware that may be crippled by software like this.
Here goes: I don't know where the issue lies, but it seems to go away if I stop and start again the AsusFanControlService. And since doing that manually would be almost the same as fiddling with AI Suite, I decided to automate it.
I had to enable Administrator since it's disabled by default in Windows 10. Here's a guide to do it. Set a password for it (it seems that this doesn't work with a blank one; moreover it's not a good idea to have an unprotected admin account).
Then I went into Task Scheduler and created a new task. It launches on resume from stand by. To do so, add a trigger and set it like this:
Next up, create a batch file with the following content:
NET STOP AsusFanControlService
NET START AsusFanControlService
Save it wherever you like (as .bat of course). I placed it in the same folder as AISuite3.exe for the sake of convenience. Back to Task Scheduler - go to the Actions tab and select that batch file (not pictured since there's nothing special about that step). Go to the General tab. Set it like this:
Upon clicking "OK" you will be asked for credentials. Enter "Administrator" and the password for it.
I just added another trigger ("At startup") since this seems to also be needed when restarting Windows. Haven't tested it, but it should work.
That should be it. Really hope this helps someone.
As for the second bug - I guess I'll have to fiddle around with the XMLs (found in C:\ProgramData\ASUS\Dip\FanXpert\Profiles). Now that I look at them again, it seems that saving a user profile doesn't save weights for any fan. Open a user profile side by side with a default one (the ones with "ASUS" in parenthesis) and you'll see that the user profile lacks the "weights" tag under a "fan" tag.
I'll play around, maybe I'll try to copy the weights from another profile and see if that works upon changing profiles. I also hope I'll find a way to switch profiles programmatically (i.e. without launching AISuite).
Shame on me for not coming up with this earlier. Shame on ASUS for apparently not caring about software. I doubt that any time soon I'd be buying hardware that may be crippled by software like this.
Several Windows 10 updates later and the workaround with resetting the service does not work anymore. Currently running Windows 10 15042 and this is what I have two hours after I've woken up my PC from sleep:
Come on, Asus, you can do better.
Come on, Asus, you can do better.
