|
Yesterday(10th) I was able to install 4.17.4 on one of my Win7 PCs ( I have 4 and 2 laptops.) Today I am continuing to upgrade but I am prevented by my Avast security system. It is telling me that? 4.17.4 is contaminated with FileRepMalware. Your comments will be appreciated.
I'm running Windows 10. Yesterday's download was on a Win 7 PC.
Thanks, Mike.
|
Every time a new version is released, the various anti malware and anti virus programs think it is contaminated. Hundreds of posts in this forum to that effect. You need to first make sure you are downloading the files from ? then temporarily disable or tell your virus program to ignore the warning about the program. After enough users download it, it gets added to the various programs safe list. Tom Wilson
Colorado Springs, CO
On Wed, Sep 11, 2019, 9:13 AM MICHAEL PAYNE via Groups.Io <mikepayne1402= [email protected]> wrote: Yesterday(10th) I was able to install 4.17.4 on one of my Win7 PCs ( I have 4 and 2 laptops.) Today I am continuing to upgrade but I am prevented by my Avast security system. It is telling me that? 4.17.4 is contaminated with FileRepMalware. Your comments will be appreciated.
I'm running Windows 10. Yesterday's download was on a Win 7 PC.
Thanks, Mike.
|
Thanks Tom, I don't normally have a problem downloading.? I have the same Avast? security on all my PCs. Just ?wondering why I' having a problem today. First thing that comes up is a box telling me I may not have permission! By the way I'm about 4500miles east of you in the UK, wish I was in Colorado! Best, Mike.
On Wednesday, 11 September 2019, 16:19:50 BST, Tom Wilson <thomasthetrainengine@...> wrote:
Every time a new version is released, the various anti malware and anti virus programs think it is contaminated. Hundreds of posts in this forum to that effect. You need to first make sure you are downloading the files from ? then temporarily disable or tell your virus program to ignore the warning about the program. After enough users download it, it gets added to the various programs safe list. Tom Wilson
Colorado Springs, CO
On Wed, Sep 11, 2019, 9:13 AM MICHAEL PAYNE via Groups.Io <mikepayne1402= [email protected]> wrote: Yesterday(10th) I was able to install 4.17.4 on one of my Win7 PCs ( I have 4 and 2 laptops.) Today I am continuing to upgrade but I am prevented by my Avast security system. It is telling me that? 4.17.4 is contaminated with FileRepMalware. Your comments will be appreciated.
I'm running Windows 10. Yesterday's download was on a Win 7 PC.
Thanks, Mike.
|
Mile,? For some reason, it seems the anti virus programs and particularly with Windows 10 seems to be way more aggressive in blocking things than they were before.
I have never been to UK. Have a friend from York living here now. Would love to go there sometime. Tom Wilson
Colorado Springs, CO
|
Thanks Tom, What's puzzling is that it is installed and works fine on my second PC? but I can't load it onthe other! Avast keeps putting it in their security vault; maybe it will work tomorrow! Mike.? ps .you'll love York, 300 miles north of me. I'm 25m north of Portsmouth.??
On Wednesday, 11 September 2019, 19:49:32 BST, Tom Wilson <thomasthetrainengine@...> wrote:
Mile,? For some reason, it seems the anti virus programs and particularly with Windows 10 seems to be way more aggressive in blocking things than they were before.
I have never been to UK. Have a friend from York living here now. Would love to go there sometime. Tom Wilson
Colorado Springs, CO
|
My experience with this one is:
I use IE to view the release note so I can save it to the folder as "archive (single file)" -- unfortunately neither of the other browsers I have has that option.? Since I already have the note open there I go ahead and download from IE and click the just-do-it-anyway option when IE complains.? This in the past has never given any problem subsequently.? This time when I tried to run the installer AVG blocked it, which has never happened before.? Even after telling AVG to create an exception, though, it refused to let the installer run.? I deleted that file and did a second downlad attempt with the same results.? I then copied the download link and pasted it into Xtreme Download Manager and it came through without a hitch and ran without a peep from AVG.
Rick
|
I'd have to ask the following questions:
1. Did you copy the one download to all the computers or did you use
multiple downloads?
2. If you ask the AV to scan the file before trying to install, does that
say it is clean?
3. Check the file size (in the properties of the file) to make sure they
match.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
|
You can see the steps in the build and release process here: A long time ago, there was a step included to submit the released Windows executable to McAfee / Norton for whitelisting. That stopped working due to some changes on their and the step was removed. IIRC, they required running some Windows executable that wasn¡¯t available during our release process, which is run on a mix of Linux and Mac machines. If somebody could write up detailed instructions for submitting to whitelist(s) that can be done from a non-Windows machine, I¡¯d be happy to add those. If they¡¯re scriptable, that would be even better, as building a test/production release already takes quite a bit of time and attention already. Automation really helps reduce errors. Alternately, if somebody wants to take on the role of doing the submissions once the files are available (typically a day or so before the release email), that would be _really_ great. Bob On Sep 11, 2019, at 9:19 PM, forfoum@... wrote:
What are the probabilities of a Test or Production version we download from JMRI.org having been infected with a virus or get infected during the download process ?
All these " False Positives " would tend to indicate infection to be very unlikely.
- - - - -
Tom, it is not the "enough users" that download that helps, it is the anti-virus apps getting the information back to the mother ship and getting the
" WhiteListing " updated. People with the FREE Avast are not sending back data unless they submit the file from the Virus Chest. Paid subscribers are sending back data and they are the ones getting the NEW file on to the Whitelist.
As I recall, JMRI DEV has stopped submitting new versions for Whitelisting. That or the service used is slow to propagate the info. Or certain Anti-virus apps do not care about propagated whitelist from other sources. Avast wants MONEY from dev who want to add there apps to the Avast Whitelisting, it is a paid subscription.
This will not go away and people just need to know it can happen with each NEW RELEASE, be it Test/Dev or Production.
Marc
-- Bob Jacobsen rgj1927@...
|
Hi,
I just tried to install? 4.17.3 same problem! Mike.
On Thursday, 12 September 2019, 06:39:38 BST, Bob Jacobsen <rgj1927@...> wrote:
You can see the steps in the build and release process here:? A long time ago, there was a step included to submit the released Windows executable to McAfee / Norton for whitelisting. That stopped working due to some changes on their and the step was removed. IIRC, they required running some Windows executable that wasn¡¯t available during our release process, which is run on a mix of Linux and Mac machines. If somebody could write up detailed instructions for submitting to whitelist(s) that can be done from a non-Windows machine, I¡¯d be happy to add those.? If they¡¯re scriptable, that would be even better, as building a test/production release already takes quite a bit of time and attention already. Automation really helps reduce errors. Alternately, if somebody wants to take on the role of doing the submissions once the files are available (typically a day or so before the release email), that would be _really_ great. Bob > On Sep 11, 2019, at 9:19 PM, forfoum@... wrote: > > What are the probabilities of a Test or Production version we download from JMRI.org? having been infected with a virus or get infected during the download process? ? > > All these " False Positives "? would tend to indicate infection to be very unlikely. > > - - - - - > > Tom, it is not the "enough users"? that download that helps, it is the anti-virus apps getting the information back to the mother ship and getting the > " WhiteListing " updated. People with the FREE Avast? are not sending back data unless they submit the file from the Virus Chest. Paid subscribers are sending back data and they are the ones getting the NEW file on to the Whitelist. > > As I recall, JMRI DEV? has stopped submitting new versions for Whitelisting. That? or the service used is slow to propagate the info.? Or certain Anti-virus apps do not care about propagated whitelist from other sources.? Avast wants MONEY from dev who want to add there apps to the Avast Whitelisting, it is a paid subscription. > > This will not go away and people just need to know it can happen with each NEW RELEASE, be it Test/Dev or Production. > > Marc > -- Bob Jacobsen rgj1927@...
|
Just a thought; could this be something to do with this new HTTPS ? Mike.
On Thursday, 12 September 2019, 07:47:16 BST, MICHAEL PAYNE via Groups.Io <mikepayne1402@...> wrote:
Hi,
I just tried to install? 4.17.3 same problem! Mike.
On Thursday, 12 September 2019, 06:39:38 BST, Bob Jacobsen <rgj1927@...> wrote:
You can see the steps in the build and release process here:? A long time ago, there was a step included to submit the released Windows executable to McAfee / Norton for whitelisting. That stopped working due to some changes on their and the step was removed. IIRC, they required running some Windows executable that wasn¡¯t available during our release process, which is run on a mix of Linux and Mac machines. If somebody could write up detailed instructions for submitting to whitelist(s) that can be done from a non-Windows machine, I¡¯d be happy to add those.? If they¡¯re scriptable, that would be even better, as building a test/production release already takes quite a bit of time and attention already. Automation really helps reduce errors. Alternately, if somebody wants to take on the role of doing the submissions once the files are available (typically a day or so before the release email), that would be _really_ great. Bob > On Sep 11, 2019, at 9:19 PM, forfoum@... wrote: > > What are the probabilities of a Test or Production version we download from JMRI.org? having been infected with a virus or get infected during the download process? ? > > All these " False Positives "? would tend to indicate infection to be very unlikely. > > - - - - - > > Tom, it is not the "enough users"? that download that helps, it is the anti-virus apps getting the information back to the mother ship and getting the > " WhiteListing " updated. People with the FREE Avast? are not sending back data unless they submit the file from the Virus Chest. Paid subscribers are sending back data and they are the ones getting the NEW file on to the Whitelist. > > As I recall, JMRI DEV? has stopped submitting new versions for Whitelisting. That? or the service used is slow to propagate the info.? Or certain Anti-virus apps do not care about propagated whitelist from other sources.? Avast wants MONEY from dev who want to add there apps to the Avast Whitelisting, it is a paid subscription. > > This will not go away and people just need to know it can happen with each NEW RELEASE, be it Test/Dev or Production. > > Marc > -- Bob Jacobsen rgj1927@...
|
Hi michael,
Absolutely not.
This is between you and your virus scanner.
Good luck, Wouter
On Thu, 12 Sep 2019 at 08:10, MICHAEL PAYNE via Groups.Io <mikepayne1402= [email protected]> wrote:
Just a thought; could this be something to do with this new HTTPS ? Mike.
On Thursday, 12 September 2019, 07:47:16 BST, MICHAEL PAYNE via Groups.Io <mikepayne1402= [email protected]> wrote:
Hi,
I just tried to install? 4.17.3 same problem! Mike.
On Thursday, 12 September 2019, 06:39:38 BST, Bob Jacobsen < rgj1927@...> wrote:
You can see the steps in the build and release process here:? A long time ago, there was a step included to submit the released Windows executable to McAfee / Norton for whitelisting. That stopped working due to some changes on their and the step was removed. IIRC, they required running some Windows executable that wasn¡¯t available during our release process, which is run on a mix of Linux and Mac machines. If somebody could write up detailed instructions for submitting to whitelist(s) that can be done from a non-Windows machine, I¡¯d be happy to add those.? If they¡¯re scriptable, that would be even better, as building a test/production release already takes quite a bit of time and attention already. Automation really helps reduce errors. Alternately, if somebody wants to take on the role of doing the submissions once the files are available (typically a day or so before the release email), that would be _really_ great. Bob > On Sep 11, 2019, at 9:19 PM, forfoum@... wrote: > > What are the probabilities of a Test or Production version we download from JMRI.org? having been infected with a virus or get infected during the download process? ? > > All these " False Positives "? would tend to indicate infection to be very unlikely. > > - - - - - > > Tom, it is not the "enough users"? that download that helps, it is the anti-virus apps getting the information back to the mother ship and getting the > " WhiteListing " updated. People with the FREE Avast? are not sending back data unless they submit the file from the Virus Chest. Paid subscribers are sending back data and they are the ones getting the NEW file on to the Whitelist. > > As I recall, JMRI DEV? has stopped submitting new versions for Whitelisting. That? or the service used is slow to propagate the info.? Or certain Anti-virus apps do not care about propagated whitelist from other sources.? Avast wants MONEY from dev who want to add there apps to the Avast Whitelisting, it is a paid subscription. > > This will not go away and people just need to know it can happen with each NEW RELEASE, be it Test/Dev or Production. > > Marc > -- Bob Jacobsen rgj1927@...
|
Thanks,Wouter. Just a thought. So what has happened to my virus scanner? On Tuesday? I downloaded? 4.17.4 to my no2 PC, no problem .My no1 and no3 PCs which all have the same Avast anti virus won't look at it.? Only other thing is there have just been a pile of Windows updates. Mike.
On Thursday, 12 September 2019, 08:12:18 BST, whmvd <vandoornw@...> wrote:
Hi michael,
Absolutely not.
This is between you and your virus scanner.
Good luck, Wouter
On Thu, 12 Sep 2019 at 08:10, MICHAEL PAYNE via Groups.Io <mikepayne1402= [email protected]> wrote:
Just a thought; could this be something to do with this new HTTPS ? Mike.
On Thursday, 12 September 2019, 07:47:16 BST, MICHAEL PAYNE via Groups.Io <mikepayne1402= [email protected]> wrote:
Hi,
I just tried to install? 4.17.3 same problem! Mike.
On Thursday, 12 September 2019, 06:39:38 BST, Bob Jacobsen < rgj1927@...> wrote:
You can see the steps in the build and release process here:? A long time ago, there was a step included to submit the released Windows executable to McAfee / Norton for whitelisting. That stopped working due to some changes on their and the step was removed. IIRC, they required running some Windows executable that wasn¡¯t available during our release process, which is run on a mix of Linux and Mac machines. If somebody could write up detailed instructions for submitting to whitelist(s) that can be done from a non-Windows machine, I¡¯d be happy to add those.? If they¡¯re scriptable, that would be even better, as building a test/production release already takes quite a bit of time and attention already. Automation really helps reduce errors. Alternately, if somebody wants to take on the role of doing the submissions once the files are available (typically a day or so before the release email), that would be _really_ great. Bob > On Sep 11, 2019, at 9:19 PM, forfoum@... wrote: > > What are the probabilities of a Test or Production version we download from JMRI.org? having been infected with a virus or get infected during the download process? ? > > All these " False Positives "? would tend to indicate infection to be very unlikely. > > - - - - - > > Tom, it is not the "enough users"? that download that helps, it is the anti-virus apps getting the information back to the mother ship and getting the > " WhiteListing " updated. People with the FREE Avast? are not sending back data unless they submit the file from the Virus Chest. Paid subscribers are sending back data and they are the ones getting the NEW file on to the Whitelist. > > As I recall, JMRI DEV? has stopped submitting new versions for Whitelisting. That? or the service used is slow to propagate the info.? Or certain Anti-virus apps do not care about propagated whitelist from other sources.? Avast wants MONEY from dev who want to add there apps to the Avast Whitelisting, it is a paid subscription. > > This will not go away and people just need to know it can happen with each NEW RELEASE, be it Test/Dev or Production. > > Marc > -- Bob Jacobsen rgj1927@...
|
Hi Michael,
I'm no further help. The whole virusscanner (installation prevention) idiocy that rules the Windows world was one of the three main reasons to drive me to Linux. The increasing hassle with drivers is another, and the third is between me and Bill Gates. :-)
Wouter
On Thu, 12 Sep 2019 at 08:55, MICHAEL PAYNE via Groups.Io <mikepayne1402= [email protected]> wrote:
Thanks,Wouter. Just a thought. So what has happened to my virus scanner? On Tuesday? I downloaded? 4.17.4 to my no2 PC, no problem .My no1 and no3 PCs which all have the same Avast anti virus won't look at it.? Only other thing is there have just been a pile of Windows updates. Mike.
On Thursday, 12 September 2019, 08:12:18 BST, whmvd < vandoornw@...> wrote:
Hi michael,
Absolutely not.
This is between you and your virus scanner.
Good luck, Wouter
On Thu, 12 Sep 2019 at 08:10, MICHAEL PAYNE via Groups.Io <mikepayne1402= [email protected]> wrote:
Just a thought; could this be something to do with this new HTTPS ? Mike.
On Thursday, 12 September 2019, 07:47:16 BST, MICHAEL PAYNE via Groups.Io <mikepayne1402= [email protected]> wrote:
Hi,
I just tried to install? 4.17.3 same problem! Mike.
On Thursday, 12 September 2019, 06:39:38 BST, Bob Jacobsen < rgj1927@...> wrote:
You can see the steps in the build and release process here:? A long time ago, there was a step included to submit the released Windows executable to McAfee / Norton for whitelisting. That stopped working due to some changes on their and the step was removed. IIRC, they required running some Windows executable that wasn¡¯t available during our release process, which is run on a mix of Linux and Mac machines. If somebody could write up detailed instructions for submitting to whitelist(s) that can be done from a non-Windows machine, I¡¯d be happy to add those.? If they¡¯re scriptable, that would be even better, as building a test/production release already takes quite a bit of time and attention already. Automation really helps reduce errors. Alternately, if somebody wants to take on the role of doing the submissions once the files are available (typically a day or so before the release email), that would be _really_ great. Bob > On Sep 11, 2019, at 9:19 PM, forfoum@... wrote: > > What are the probabilities of a Test or Production version we download from JMRI.org? having been infected with a virus or get infected during the download process? ? > > All these " False Positives "? would tend to indicate infection to be very unlikely. > > - - - - - > > Tom, it is not the "enough users"? that download that helps, it is the anti-virus apps getting the information back to the mother ship and getting the > " WhiteListing " updated. People with the FREE Avast? are not sending back data unless they submit the file from the Virus Chest. Paid subscribers are sending back data and they are the ones getting the NEW file on to the Whitelist. > > As I recall, JMRI DEV? has stopped submitting new versions for Whitelisting. That? or the service used is slow to propagate the info.? Or certain Anti-virus apps do not care about propagated whitelist from other sources.? Avast wants MONEY from dev who want to add there apps to the Avast Whitelisting, it is a paid subscription. > > This will not go away and people just need to know it can happen with each NEW RELEASE, be it Test/Dev or Production. > > Marc > -- Bob Jacobsen rgj1927@...
|
MICHAEL PAYNE
Rick Uhlenkott
Ken Cameron
Bob Jacobsen