![Thumbs Up :thumbup:](./images/smilies/ay.gif)
EDIT: No problem downloading and installing the latest version on
Edition Windows 10 Pro
Version 22H2
OS build 19045.4046
I downloaded Rainmeter 4.5.19.3742 with three browsers:jsmorley wrote: ↑February 23rd, 2024, 9:18 pm I have created a new build of the software and put it in the first post of this thread:
https://forum.rainmeter.net/viewtopic.php?p=221656#p221656
Can we get another bit of help, and have you guys download and install this and let us know if there were any issues with your antivirus? Be sure to update your antivirus definitions before starting.
My Defender won't update as the other zillion MS stuff requesting connection for that are prevented to do so (don't want my stable Win 10 to become Win 11 or other unpleasant surprise happening overnight), but on VirusTotal only two vendors (the hopeless BitDefender Theta and the unknown Rising) still flag this latest release, on both my phone and my laptop, so it's all good. The browsers, as usual, are fine with this release too. My AV(ast) didn't detect it before and doesn't detect it now either, and its virus signatures are up to date. I'm on Win 10 21H1 Build 19043.1202 and there's definitely a major improvement in terms of AV detection in this release.
All good from my end. Same OS/version as yours.jsmorley wrote: ↑February 23rd, 2024, 9:18 pm Can we get another bit of help, and have you guys download and install this and let us know if there were any issues with your antivirus? Be sure to update your antivirus definitions before starting.
Microsoft Windows 11 Pro (64-Bit)
Version 23H2
Build 22631.3155
In case it matters, I just got this when trying to install a (clean) skin: I'm used to some of these "shields" being a little obsessed with otherwise normal things when it comes to this product, but still, as far as I recall, this didn't happen with the skin installer executable from the previous Rainmeter version. Not sure if it helps or is relevant to the subject here, but you said to let you know of any issues, so here is (a minor) one.
I assume this is related to Avast's variant of this:Yincognito wrote: ↑February 27th, 2024, 10:25 am In case it matters, I just got this when trying to install a (clean) skin:
SkinInstaller.jpg
I'm used to some of these "shields" being a little obsessed with otherwise normal things when it comes to this product, but still, as far as I recall, this didn't happen with the skin installer executable from the previous Rainmeter version. Not sure if it helps or is relevant to the subject here, but you said to let you know of any issues, so here is (a minor) one.
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.jsmorley wrote: ↑February 27th, 2024, 6:40 pm I assume this is related to Avast's variant of this:
https://forum.rainmeter.net/viewtopic.php?p=157423&hilit=protected+folder#p157423
Presumably, if you "allow" SkinInstaller.exe to access protected folders like Documents once, it will be fine from then on. Can't say for sure, as I have not run Avast for probably 20 years.
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.Yincognito wrote: ↑February 27th, 2024, 9:19 pm 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...
That explains it indeed - thanks. Time is not a problem, the important thing is that it can be done.jsmorley wrote: ↑February 28th, 2024, 10:29 pm 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.