f.lux triggers repeated explorer registry access on v4.130
i found a very weird effect when f.lux is running, even when it is in disabled mode. Procmon by Sysinternals shows that explorer.exe constantly reads the registry keys and subkeys
HKLM\OSDATA\Microsoft\Windows\CurrentVersion\RetailDemo\OobeWrite(doesn't even exist).
This happens every second precisely and stops if f.lux is exited, so there is definitely a link between explorer.exe and flux.exe in this case. Is there something happening every second in f.lux, like a timed function call?
herf last edited by
@Girofox123 thank you - it looks like the Windows API (called "SHQueryUserNotificationState") which tells us if it is a good time to notify someone actually writes to the registry, so we have stopped doing it so much (v4.131 should have the fix). There may still be a way to trigger this in the future, but it will be rare.