Can you tell the f.lux team what you need help with?

Well i decided to really examine the motherboard.. and discovered some ports are seriously damaged, so i renabled the controller in the bios and went in windows and disabled the individual ports in the device manager until the ones pictured below had 0 on the multimeter.

Then I put some electrical tape over them, and also the power supply that came with the board I replaced with a spare one I have, and its running normal now f.lux is acting perfectly once again.

alt text

@Dong-Lee It uses sunset times, not your own times. If you, like most, don't sleep at 4 pm, you have to manually change the color every few hours after sunset in winter, or change your location to something in the world that matches your sleep patterns. I just move the the colors as needed, since the color I've comfortable with at 5 pm is vastly different than the color I'm comfortable with at 10 pm.

Sorry forgot to post driver info: Intel Corporation 22.20.16.4691: Intel(R) HD Graphics 620 (20170602)

@herf Tried it and it is indeed working as supposed to - thanks again.

It was definitely, 100% flux. I could control it by opening and closing the flux process. Tooltip refreshing could be the cause. It hasn't returned yet.

Yes we have a new version that will do this, but it still needs some tweaking.
Will make sure we work on it more.

@herf

Thank you for your reply.

@herf said in Strange behaviour on 1709 with Crimson 17.10.1:

Is Defender trying to remove f.lux?

No. The Defender Notification Icon in the Notification Area shows up although I disabled it (How to). It doesn't show an error, it does not inform me of something, it simply appears although I disabled the appearance. That is my problem. Apart from that f.lux and Defender work as intended. As I found out a week ago, with the Windows Store version of f.lux the Defender Icon does not show up.

So I am happy now but there is something in your code in the 4.55 standalone version that activates the Defender Notifiaction Icon.