@  - just read what I wrote and you will understand that the comment: "Thank you for nothing EVGA support tech!" Was a way of being ironic. I don't think of it as an insult. 
I worked with EVGA tech support for over 3 months (all logged with EVGA tech support)  and they basically told me that there is nothing else that they can do. The official tech support from EVGA had no clue on what to do anymore. 
If I could not care less of about this I would have fixed the issue and stayed quiet and let other people run into the same issue but not I decided to share that with the forum, so if others have the same issue - I explained what worked for me. 
This was the last answer from EVGA:
"Hello,
I'm sorry about this ongoing problem but you are the only customer I have encountered having this issue with this particular CLC. I myself also have one installed on a X299 micro and it works right at boot up with the only minor issue being the implementation of Microsoft's annoying UAC pop up but that's all on the OS. 
There is no known incompatibility between Asus motherboards and any of our CLCs being that it does work and I would highly encourage you to test it on another system to confirm for yourself that the issue is isolated and neither the CLC, the motherboard or the software are at fault."
 
And yet I fixed the issue (myself) with a very simple solution..... 
 
I still like EVGA products, particularly this AIO, very effective - better than most 360 AIOs out there (in terms of performance). (although I might go custom loops after this AIO dies for other reasons) 
 

Got it

ftmiranda
After I posted my comment here, I was just doing some more tests like disabling the power savings from all USB HUBs on Device manager on Windows 10, disabling all possible power management options on USB. Did the same on the BIOS. Nothing helped - but then I figured it out - 



If you are getting the CPUWB error, Device Not Found message only when you load Windows (meaning that if you double click on flowcontrol after the error message and it will load)

- to make this annoyance go away, press Windows key then R - then type shell:startup, this will open the startup folder - copy the flowcontrol app there - it worked. 

Now Windows 10 successfully loads the flowcontrol in the right order and it does not show the error message anymore.


The way it was before, I would start flowcontrol manually - then use the computer for gaming, after the gaming session I would shutdown normally - next day I would start Windows and that annoyance would happen,  CPUWB error, Device Not Found, then I would double click on the flow control icon and load it then start my gaming session.

After I explicitly added the flowcontrol to the startup folder on Windows 10, the problem was magically fixed. 

Thank you for nothing EVGA support tech! 

After I explicitly added the flowcontrol to the startup folder on Windows 10, the problem was magically fixed.

Thank you ftmiranda - for sharing Your Solution with the EVGA Community
 
[I edited your Quote for Clarity / Readability]
 
I would like to note that trouble shooting issues that only happen to some setups / PCs - is hard to troubleshoot, especially if it can not be Replicated.
 
Look at My AIO Folding build.  It uses an Asus MB & EVGA CLC cooler ... I did not have the issue you experienced
 
 

Interesting !!  
 
I  had noticed some times when setting up NEW builds/systems the "Device Not Found" error  ( EVGA CLC)
but after installing other programs ( internet security - Acronis protection - lots of Windows updates )
the error was gone.
 
At the time thought it was a later added  driver that fixed it or the security software delaying starting of third party programs.
 
I also seem to have less problems with start up error on a SSD or M.2 based boot windows 10 vs a hard disk system