Catching cloudcar.exe in the off-line real-time scan engine would cut down on the perceived impression that there is an issue with the scan engine. So doing so is a smart move. I did find a posting on the AMTSO web site of a study that became the model for the Cloudcar test: http://www.amtso.org/wp-content/sp-...e_Cloud_Testing_Metrics_and_Methodologies.pdf . It did recommend for scanning of external media data transfers but not on a cloud basis; rather by offline content scanning based on hash or code. Actually the diagram shows all content scanning being performed outside of the cloud with only url and domain validation being performed in the cloud. As a test, I did copy the cloudcar.exe file to a thumb drive and deleted cloudcar.exe from my internal HDD. I then proceed to copy cloudcar.exe from the thumb drive back to the internal HDD and Eset did not detect it. Again, I am sure Eset scanned the file upon creation on my internal HDD but did not alert due to the fact the file is not malicious. Nor for that matter is it suspicious since it is not a valid executable. All Eset has to do is include the clouldcar.exe hash in the offline blacklist or include a signature for it and this issue is resolved.