Serge

@Retr0680 not yet, try to do following: ``` Set-Service -Name "AsusSAIO" -StartupType Manual ``` Then run ``` Get-Service -Name "AsusSAIO" | Select-Object StartType ``` it should say it's set to...

@Retr0680 if it doesn't work still, post what does this command outputs for you ``` Get-WmiObject Win32_SystemDriver | Where-Object { $_.Name -like "*AsusSAIO*" } ```

@Retr0680 ok, it seem to be running now ... can you try if G-Helper manual control works now ?

@Retr0680 ok, i have some bad news :) I had to dig deeper, and managed to reproduce it. It seems like asus has restricted access to the driver only to...

@Retr0680 did you manage to launch it via `psexec` ? What does Fans + Power window show when you run it ? can you post a screenshot ?

@Retr0680 ok, so it confirms reason - is a new permissions. I currently don't know how to tackle this besides running app as SYSTEM. I might try to write a...

@Retr0680 for the sanity check, can you test if https://github.com/Karmel0x/AsusFanControl works for you with 41 ? That app uses asus own DLL for setting fan speeds, but under the hood...

@Retr0680 ok, thanks for confirming. It's same for me. Then looks like the only solution would be writing a separate service app (cause it runs with SYSTEM permissions) that would...

@injkgz it's not related to Experimental manual fan control :) But it depends on the model, G14 and G16 **2024** firmware require both fan curves + power limits to be...

@orionflame you can just use previous version of Asus Control interface (3.0.1.40) for now :) For the newer one, I need to find a way for (user friendly) access to...