Anyone know why Avast’s hardened mode keeps blocking the Chrome installer from launching? I have it set to aggressive. Anyone else get this?
I don’t use Chrome so I can’t really say.
But the Hardened Mode - Aggressive setting - will check the file against the avast cloud for that file, not just the name but it hash # MD5, etc. etc. to see if it is listed as good.
Is is giving you an alert window and if so what reason is given ?
- I suspect it may be reputation based.
Since Chrome is so frequently updated, there is a new chrome installer almost weekly - in the very early stages it won’t have a reputation and or high frequency of use amongst avast users. More so if this is for a beta/alpha/nightly build of chrome.
In the Hardened Mode - Aggressive setting alerts, you should have an option to add it to the exclusions. See attached image of such an alert (but was from Hardened Mode - Moderate), this is for an earlier version of avast 9, but it should still be similar.
That’s the alert that it gives me. I think there might be something about the installer’s hash that’s confusing it. If I run it through Virustotal (Comes up negative), then redownload the file and try running it through again, it won’t tell me that the file has already been analyzed. Maybe the hash is different somehow for each download and that’s why it isn’t on the exclusion list?
Really just wondering if this is just me or if everyone seems to get this.
I think there is problem in the way Avast! chose which version of file to check. From what I see in Software Updater, Avast! was unable to define which version is stable, which is beta, so it show the version which is newer, doesn’t care if this is stable and officially released or not. In your case, your Chrome installer may be reported as old version and blocked. If you don’t mind, try a beta version (above 35) and see if it pass.
If you have clicked the option to Add an exclusion, it should have added it - but I’m not sure if these are also added to the list of files you added manually - I think this happened in older versions of avast 9. But you could try manually adding it to the Hardened Mode exclusions.
Running it through VT won’t give the same results as I don’t believe it can replicate the Hardened Mode and any avast Cloud checking.
I don’t thing the hash # would be constantly changing for each download (this wouldn’t make sense) as it would mean more administration for some if they report the hash number in the download to allow you to check the file hash you got is valid.
I don’t think it is just you, but this could happen with frequently updated applications like chrome. It seems to be update very, very frequently.
If it is still troubling you you could temporarily disable the Hardened Mode before installing chrome. Or can you not update it from within the browser if you already have chrome.
Really, I’d just like to know if anyone else has this problem.