John, The last two major version of Avast Internet Security (Ver 8 & 9) have had some qualms about Legacy install files.
This was a problem seen in Legacy 7.x also; it is not new to Legacy 8. It has something to do with how the Legacy installer file is constructed. To keep it as small as possible, it is a compressed file. The file is uncompressed into a temporary file that has a different name, probably created by Windows on your PC, each time it is created so you cannot tell Avast that the file of that name is OK as it is seeing a concern about the created temp file. If Avast were the only part of the problem, this would not be an issue. However, Windows (I use Win 7 Pro) jumps in after Avast starts analyzing the file, Windows thinks it is not opening quickly enough, so it comes up with what is effectively a "Not Responding" Window (which you just have to X out of) and then a Program Compatibility Window that you can just close and then the install proceeds without a problem. A further complication can be that, if you choose to download the installer file and rename it - I append the build number, you will get another Program Compatibility Alert asking if the program installed correctly. Just say yes, and you are good. I get annoyed about this, but this should give users, confidence that the installer is a safe file. As a tester, I got the privilege of dealing with this almost every day for months. I have tried contacting Avast support, but I do not think they understand what is the problem. They do not understand that new installer files are created regularly so I cannot just upload one and have them clear that one when they get around to it, as a new copy will likely be available before they process it. I invite other Avast users to contact them also. I have not found an Avast option to limit this behavior just for Legacy setup files. Nor have I found what Windows options need to be tweaked to deal with the alerts they are posting. BTW, I seen these problems with other software I have installed on my PC. john. At 05:49 PM 11/26/2013, John Magyari wrote: >After being hit by several viruses this year >and having to reformat the drives on 2 PCs >I started using Avast, which has prevented many infections so far. > >Avast indicated >We did not find enough evidence to identify the file as malware, >However you should still use extreme caution when accessing it. > >msdev.exe > >reason: The file prevalence/reputation is low. > >Is this file uninfected or should I override >the Avast Antivirus Software during installation? > > > > > >Legacy User Group guidelines: >http://www.LegacyFamilyTree.com/Etiquette.asp >Archived messages after Nov. 21 2009: >http://www.mail-archive.com/[email protected]/ >Archived messages from old mail server - before Nov. 21 2009: >http://www.mail-archive.com/[email protected]/ >Online technical support: http://www.LegacyFamilyTree.com/Help.asp >Follow Legacy on Facebook >(http://www.facebook.com/LegacyFamilyTree) and >on our blog (http://news.LegacyFamilyTree.com). >To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
