Schrödinger update / lost configuration

[Kamil-Radzyminski]

Hi. A new user here, configured fan control for the first time last week.
Today I noticed popup with a new update, clicked it, cmd opened, performed update, and nothing happened.
Clicked it agin, it did the same thing, but version did not change.
I closed the app, opened it agin and it was 208 (updated) but my configuration was gone (Started to wonder - was that expected? There were no warrnings of such thing.., Would be a bit pissed off after 6 hours of grinding perfect curves to match noise levels of each sepparate fan to certain workloads if i didn't manage to get it back and at least screenshot).
Nevertheless, I closed the app, restarted the PC and 207 opens on startup agin (with old config).
Closing the app, win + FanControl + enter, and the 208 without config opens.
What is going on? It seems like another version of the app was installed instead of updating existing instance. Should I file an issue ticket, or is this something known/expected?

[Kamil-Radzyminski]

I'll mention that it was installed by .net 8.0 installer from release page.
Not sure if thats the best option / can cause unexpected behaviors for some reason?

[Rem0o]

Wait... the installer does not install in C:\Program Files\FanControl? Or did you run the installer and changed the path in there, and now you get this bug?

This has to be a bug with the polish character messing with the path. Never seen that before.

What I would do is stick the to the default install path of the installer, aka C:\program files.... and leave it there to avoid further problems.

[Kamil-Radzyminski]

The installer allows to choose a specific directory for instalation:

I assume these problems are caused by moving the app to another directory after installation.
I performed a fresh install in my chosen directory and will wait for another update to see if the issue persists.
If it does, I'll try installing in the default directory.

[Rem0o]

^ Moving the installation folder will definitely cause problems. It will also break the "start on user log on".

[Kamil-Radzyminski]

I didn't notice any problems besides update. Start on user log on worked fine.

[Rem0o]

The scheduled action needs a start-in folder:

This will not change if you move the folder.