So as you can see horinius telling somebody to shutup doesn’t help solve problem. You concentrated on expressing your anger rather than explaining the problem properly like warlock did in a very fashionable matter-nice job
But thank you for pointing out the problem in the first place anyways
All about communication ;D
If you still have a sample, send the sample to virus@avast.com zipped and password protected with password in email body and undetected malware in the subject, so that it might be analysed and added to the detection signatures.
@ avvidro
I couldn’t agree with you more. If people are reading this, check the first thing those avast! Evangelist said. igor said it’s not a big problem instead of appreciating user to report a problem they encountered. Didn’t say “could you” nor “please try”. What’s worse! First thing that Eddy said is assuming it’s horinius’ problem. Or should I say he “thinks” that it’s horinius’ problem? I would be so angry to help a company to improve their software by reporting bugs and they treat me like crap and tell me to spend more time on learning how to use their product. It is just not reasonable and not how you should do the business. Also, @al968, what you said makes it even worse!! Please try to think as if you were in horinius’ shoes. You must have extremely good temper to be not mad.
I was trying to seek for the solution of a problem that my friend encountered with Avast! and I saw this thread. And now, I won’t even bother looking for it. Instead, I will tell him to use Avira AntiVir, the anti-virus I am using now. I feel bad for recommending Avast! to many of my friends and family.
By the way, those developers should really work on Avast!'s UI. Just keep it simple and elegant. That’s one thing I couldn’t stand. Also, why not doing what Avira AntiVir does. I mean automatically renewing the serial number as soon as it expires. It would make everything easier!
If you want an example of a convoluted interface take a look at Kaspersky. KAV also has some issues at the moment - there are a number of silly bugs in the latest version.
NOD32 causes problems (for some) with Outlook. The add-in can cause Outlook to crash. It also has a terrible UI and plays havoc with Java based apps.
And now Avast…(I’m trialling ‘Pro’)
I find (after a short learning curve) that Avast has a very appealing UI and I enjoy using it.
Avast has extensive functionality without causing browsing / e-mail problems or slowdowns (apparently).
Avast has again achieved the Virus Bulletin 100% award, which is good enough for me. There are a few bugs maybe, but then aren’t there always…? It goes with the territory, and I’ve been in the software business for 25 years. It’s a question of finding the right balance, and the product needs to work without interfering with day to day computing activity. Essentially, you need that ‘nice warm feeling’ that it’s doing it’s job…
Just the kind of software company I’d love to work for…
I reproduced this “problem” by doing the same thing (I think) as the original poster. I copied the text string of the eicar test into notepad, clicked ‘save as’ and then inserted unicode into the filename and saved it as .exe
Avast immediately popped up and recognized it and propted for action. When I told it to delete the file, it couldn’t, and generated an error to this effect. I also noticed that notepad locked up. This behavior is actually expected and in no way a security risk. Allow me to explain:
When you have a file open for editing (word, excel, notepad etc), windows locks it to prevent data corruption. To test this, try opening a text file in notepad, then using windows explorer try and delete it while it is still open. It won’t work. This is what you are asking Avast to do with this test. This is an operating system feature and a good one at that. When a virus tries to execute on your system, it is not opened in the same way as a text editor would open it for writing. The point here is that this ‘test’ doesn’t really serve a useful function. The real way to test this is save the file as before, but when avast pops up, tell it to do nothing (because the file is still open for writing in notepad). Then exit out of notepad and then browse to the directory where you saved the בּ.exe or whatever. Now see how Avast handles it. If it still is unable to delete the file when the file is not locked by the OS, this is something you should report.
I hope this clears things up. Also, this is a good example of why you shouldn’t act like a troll when other forum users don’t give you the response you want. The conclusion here is user error/lack of knowledge.
nate@rn ty. I have to admit, I was laughing my butt off until I saw that someone finally caught on to the run time error, (windows is famous for these.), but as you point out, with out these little safeties built in, most systems would probably be trashed in the first couple of weeks. I am still laughing about this, because I do not see that the question has ever been answered…lol. So I will answer it.
My avast free edition caught it and gave me options…I chose…MOVE IT TO VAULT…hmmm…novel idea don’t you think?
I like the vault option for all things because I then have the time to examine a file, decide weather or not it is a false positive, (these things do happen), and then deal with it, or just leave it locked up.
As to horinius, I think someone needs to take a chill pill…lol. But thanks for the entertainment. ;D