Right. The other issue is that the only executable that we are currently "signing" with a certificate is the installer that you download. There are a couple of .exe files (Rainmeter.exe and SkinInstaller.exe) for example, that are extracted and delivered as a part of the installation process, and while they won't trigger the SmartScreen stuff that is all about "downloads", they could get some extra scrutiny from some tools since they are not digitally signed. We are looking at correcting this, but it might take a little while.Oh, that makes perfect sense - thanks for the link and explanation, they're spot on as usual. I already allowed the executable and it's perfectly fine as expected.
I posted this not necessarily because of the message / action itself, I was referring more to the fact that I didn't need to do it for the previous Rainmeter version. On a second thought though, this might not necessarily be about the new version triggering the alert on its own, but rather the AV reacting to the executable being different than the one in its "database" of known executables on my system...
Statistics: Posted by jsmorley — Yesterday, 10:29 pm