Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ The same `AsusFanControl.exe` starts the **GUI** when you double‑click it or r
--get-cpu-temp
</details>

GUI: run `AsusFanControl.exe` with no arguments (or use `RunAsAdmin.bat` where provided).
GUI: run `AsusFanControl.exe` with no arguments (it will automatically request admin rights).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The note about automatically requesting admin rights is placed specifically under the GUI section. However, since the GUI and CLI share the same executable, any elevation mechanism (like an application manifest) will trigger a UAC prompt for both modes. It would be more accurate to state that the application itself requires administrator privileges. Additionally, the PR title mentions 'auto-start', which usually refers to starting with Windows, whereas this change is about 'auto-elevation'.

Suggested change
GUI: run `AsusFanControl.exe` with no arguments (it will automatically request admin rights).
GUI: run AsusFanControl.exe with no arguments (the application will automatically request admin rights).


![AsusFanControlGUI](https://github.com/Karmel0x/AsusFanControl/assets/25367564/fe197ad0-7079-4d51-ae78-177cb6369e96)

Expand All @@ -35,3 +35,9 @@ The release build embeds the same `AsusWinIO64.dll` (licenced to `(c) ASUSTek CO

[Works on](../../issues/13):
- ASUS: VivoBook, ZenBook, TUF Gaming, ROG Strix, ROG Zephyrus, ROG Flow

### Security & Antivirus

Because this application interacts with hardware-level drivers via AsusWinIO64.dll, antivirus software such as Windows Defender might falsely flag it as malicious.
If you experience this issue, please add the executable to your antivirus exclusions.
*(Alternatively, you can compile and code-sign the executable yourself to prevent false positives.)*
Loading