1. Avast “Screen Saver Scanner” is detecting itself :o “AvastSvc.exe” in memory as Malware “HTML:RedirME-inf [Trj]” see pix
2. For some strange reason i now can not scan “klmcodec551.exe” on any of my drives see pix
NOTE Both of the above problems started after going to sleep this morning 6 am CST SK CND
3. To take these screen shots i use the default Windows “paint v5.1” but i am unable/unsure how to make the pix use less space. 176 KB for this pix is HUGE compared to others i have seen here. I have 2 other pix that i would have upload here as they are both related to my problem but both are over 200 KB. Is this a good pix program to use or is there a better more functional FREE pix program to use?
UPDATE: I now notice that when i open the Avast GUI it takes a long time to show and when switching from one area of the GUI to an other a get a blank/white out GUI for 10 to 40 seconds ???
Strange that as a right click scan on the avast5 folder finds nothing and that is the most thorough of the avast scans.
Ensure that you have the latest virus definitions and scan again, there has also been a new program update, 5.0.462 today, so do a manual program update from the avast UI and that also does any virus definition update also.
Crop the image so it is only showing relevant information.
You don’t have to many programs password protect their files so avast can’t know that password nor even if it did has any means of entering it. I can only assume that this is a self-extracting archive file (hence the .exe file type).
Where did you get this file from as there are many google hits relating to this being a torrent download and a number of them also associating it with a crack + keygen ?#
So if this is a legit codec, it is also one which has to be paid for so presumably it would be protected in some way.
lol why cant ppl read ???
As i said in my first post “NOTE Both of the above problems started after going to sleep this morning 6 am CST SK CND”
In version 4.8 i did not have this problem with the codec file. I upgraded to v5 and still didn’t have this problem. Then all of a sudden with no changes on my part avast cant scan the file unless is during an off line scan which say all is good.
Where i got the file is of not consequence! And NO it isn’t a crack file!
Problem #1 has been corrected. Avast no longer detects “avastsvc.exe” in memory as malware. I don’t know what fixed it. I did not change any settings. It was prob corrected in an update.
Problem #2 still exists
It say “Error:Archive is password protected. (42056)”
I did NOT put any such pass word on this file [klmcodec551.exe] The problem did not exist in the past as ive had this file for over 2 years.
UPDATE:
I now notice that when i open the Avast GUI it takes a long time to show and when switching from one area of the GUI to an other a get a blank/white out GUI for 10 to 40 seconds
hmmmm that seems to be the answer here lately “just exclude it” >:( This action is not a fix but just a cover up!
AGAIN i will state that in version 4.8 i had no problem with scaning the file. I then upgraded to version 5 and had no problem with the file for about 4 days but now for some unknown reason avast now will not scan it :
Well, the reason is known - the files inside are password protected.
Yes, the installer doesn’t actually require any password because a compiled script inside somehow fills the corresponding field automatically - but the files are encrypted with an unknown password and it’s not possible to scan them.
As for why avast! 4.8 “had no problem”… well, the unpackers there are older than in avast! 5, so it probably didn’t recognize the (Inno) installer archive at all, i.e. didn’t have any change to report that the files inside are encrypted.
Again i said "I then upgraded to version 5 and had no problem with the file for about 4 days but now for some unknown reason avast now will not scan it :
"
And I told you the reason - the files in the installer are password protected, and avast! could never have scanned them.
The unpacking engine is part of the virus database in avast! 5 - so yes, it’s possible that even avast! 5 didn’t recognize the archive property until recently.
In any case, if the error message didn’t appear previously, it only means that the archive wasn’t detected at all, so there was nothing to report - certainly not that it was unpacked and scanned.
