Don't know about this. IE11 definitely doesn't like the download. -EDIT- Strange .......... Just looked at the sig. on the original download and it is validly signed.
No, SHA1 not the issue. I just downloaded an Eset utilty w/SHA1 cert. and not a peep from IE11. -EDIT- Oops! You were indeed correct. The Eset download was signed prior to 12/13/2015: I believe IE is reporting this problem because the code signing certificate used to sign that EXE is using SHA1 for the signature, and it was signed after Dec 31, 2015. Microsoft describes this here: http://social.technet.microsoft.com...thenticode-code-signing-and-timestamping.aspx
Uploaded to Jotti. ONLY Clam flagged. So I ran it & it changed the group policy. Which I thought I had already done. Doh!