[Feature Request] Add silent auto update function

[xcabur1]

Motivation There are many product updates, which is generally very good, but the “Update available” message is often displayed and the installation must be confirmed manually. It would be helpful if there were an option to have new updates installed automatically in the background.

Expected result Add a option in settings menu that allows updates to be installed automatically.

Possible modifications

1. In the Settings menu, replace the option “Notify for updates at startup” with a dropdown option “On new updates”

2. The value “Do nothing” corresponds to the existing behavior “Notify for update at startup” = Off.

3. The value “Notify” corresponds to the existing behavior “Notify for update at startup” = On.

4. The value “Install automatically” starts a new behavior, in which a new update is installed automatically, silently, in the background at startup.

[Rem0o]

I treat FanControl kind of like a BIOS update. You wouldn't want your BIOS to update silently, because said update could have serious impact and any bug could prevent your PC from functioning properly.

It's a bit exaggerated, but FanControl updates have broken compatibility in the past more than once, and if the user isn't even aware of the update and it breaks something, he might only find out when his CPU cooks itself.

That's the whole reasoning.

[xcabur1]

Some BIOS versions, such as those from HP, are updated by Windows Updates, just to say. But I know what you're suggesting. On the other hand, problems can still occur when I get an update notification and install the update. I'm just aware of the update an a potential issue. Maybe you can show a update successful message after update is installed, so we are aware of the update, but without manual action.

[Ozzuneoj]

I treat FanControl kind of like a BIOS update. You wouldn't want your BIOS to update silently, because said update could have serious impact and any bug could prevent your PC from functioning properly.

It's a bit exaggerated, but FanControl updates have broken compatibility in the past more than once, and if the user isn't even aware of the update and it breaks something, he might only find out when his CPU cooks itself.

That's the whole reasoning.

This is exactly how it should be. No forced updates with something like this, ever. Even just taking into account all the time and work that goes into tuning a configuration... if the program updates and breaks something in the config, that can potentially cost the user a lot of time and irritation.

Also, when dealing with a small project like this, it's not like Rem0o can have a new version tested on 50,000 different setups before rolling it out to the public. Bugs\incompatibilities will be found and reported on Github relatively quickly, but they will be found by end users who update the program. If you aren't the type to want to deal with extra issues or extra updates, just wait a day or two after large updates and you may end up with a fixed version.

Personally, I just turn the update notifications off if I don't want to see them. Much like a BIOS update, if your configuration is working, there is probably no need to update it at all, let alone multiple times per month.

With the antivirus detection issues that came up this week (affecting all versions), I'm seeing many posts from people who have been using 1-2 year old versions of FanControl with no other problems.

[Rem0o]

if your configuration is working, there is probably no need to update it at all, let alone multiple times per month.

I feel like this is an underrated comment. I push updates regularly, but that doesn't mean you need to update every single time if your setup works fine without any bugs.