Thanks for the Avira idea. If Avira is launched after f.lux does that trigger the problem?

The only difference between the "autorun" behavior and the manual launch is that the autorun does /noshow, which hides the f.lux window (rather than showing it).

The v4 version uses different resolution icons and makes fewer tooltips, but I can't think of too much else that is different.

The 4.59 build fixes a potential crash bug, so I would try it just in case it helps: https://justgetflux.com/flux-setup4.exe

Thank you herf. I tried that version but still crashing.

About launching Avira after the flux: when I disable flux to start with windows, and I open it manually (after Avira) everything works good. So may be the issue has to be with that.

Do you know a possible solution for this issue?

The only difference between the "autorun" behavior and the manual launch is that the autorun does /noshow, which hides the f.lux window (rather than showing it).

The v4 version uses different resolution icons and makes fewer tooltips, but I can't think of too much else that is different.

The 4.59 build fixes a potential crash bug, so I would try it just in case it helps: https://justgetflux.com/flux-setup4.exe

During the start of my Windows 7 Pro 64-bit V. 4.55 and the newest beta both lead to a crashing explorer. The process of the explorer automatically starts new after that. And there is an issue with two other programs (for example avira) in autostart which are disturbed by f.lux. After going back to Version 3 everything runs fine again.

This happens exactly to me as well. I actually created this acc to make the topic about this issue because is extremely annoying, but I've found this topic so I'll continue here. I use Avira as well by the way

This information might be useful: the autorun of flux leads to crashing explorer when the system starts. But if I disable the autorun and once the system starts I open flux, everything works good.