I was also glad to find I was not the only one. Some people may say F.lux + DisplayLink is a rare combination.
I have contacted the F.lux developers about this and the reply is, "This has been reported to Microsoft and seems to be a displaylink issue... Will let you know what we find out."
I assume the bug is related to the whole new driver interface for DisplayLink devices with Windows 10 Anniversary (
http://support.displaylink.com/knowl...rticles/525125). For a whole new interface, I would say the transition went fairly well. Other than the incompatibility with F.lux it's been a smooth upgrade in my experience.