Jesus, first a false alarm with that dll a few days ago and now Avast goes crazy across the board. Personally I’m affected because my Roboform password manager can’t start anymore unless I deactivate Avast. Nice choice. Either I’m vulnerable to Viruses or I can’t access any of my password-protected sites (including online banking). Of course it’s a dll again that is falsely detected as being a tojan or virus or whatever. And besides that other Roboform files are falsely detected as well. Avast, clean up your act or you will be history (which would sadden me).
Yes, I have the same problem this morning with a genuine bought copy of Roboform being flagged as Win32:Adware-gen. [Adw]. How can I revert to the previous level of Avast VPS file ? This is stupid not allowing a password manager !
There is no simple way (that I know of) to allow you to revert to and stay with an earlier VPS file.
However to help you over what appears to be a false positive …
In the avast Standard Shield click the Customize button > Advanced tab …
There is a box where clicking the “Add” button will allow you to add the path and filename of a file that you want to be excluded from avast scanning. You can add the filename that you believe to be a false positive so that you can continue normal operation until the avast team have a chance to take care of a false positive in an upcoming VPS update.
Please pack the misdetected file into a password-protected ZIP or RAR and send it to virus@avast.com.
Thanks.
Too bad, it would be nice if you could in cases like this.
When I used mcafee, the dat files where kept on a server for a few day after release, just in case. It was handy when a “bum” dat file was released. You could download a version hat you didn’t have trouble with and revert. You had to do it manually with a “f” switch. Maybe something for futre consideration?
While I understand the thought behind the proposal that route leads to much confusion of the “which VPS version are you using?”.
Just my view but far, far better just to fix and move forward and have us all on the same page.
I’m sure that the avast team takes on board the comments about the impact that false positives can have. They have committed to being faster at detection … in doing so they probably have to also work at better avoiding false positives too. It’s probably not an easy balancing act.
Yes, I agree that the best solution is to fix it asap. And usually the fix is out promptly. (pat on the back)
Some AVs have ‘rolling back bases’. It might have been of use in avast!. 
You can solve the problem by update RoboForm to the latest version 6.8.2.
http://www.roboform.com/dist/AiRoboForm.exe
Intriguing I use roboform and have never had a problem with it at all. Are you getting your copy from a reputable site ?
Same here. No problems at all with the free version of Roboform.
I am using Roboform 6.7.8 bought and downloaded from Siber systems website.
I’ve done as suggested and excluded Roboform (and Firefox due to the plugin relationship)
I’ve sent a zip file of the dll to Avast as requested.
So all is quiet again for the moment
Thanks - Martin
Which one?
Well… I never had a problem with Roboform, working perfectly with IE, Maxthon and Firefox.
So, as mauserme and essexboy, no troubles to me too…
Roboform works just fine here also with my browsers Maxthon and IE.
I paid for my copy of Roboform (the USB stick version). And the dll from a few days ago that I was talking about was that Wordpad dll (IIRCC). And yes I’m not using the latest version of Roboform (USB). My version is the one before the latest. But how would I know that my particular version causes a false positive. All in all and considering that other software causes false positives too and the Wordpad false positive from a few days ago I would say that it starts to get annoying. Really hope you clear that up because otherwise I love Avast.
Well, you don’t have too… False positives should be corrected by the antivirus manufacturer.
Are you using the last VPS version?
New iAVS update (VPS 645-3) for avast! program has been released recently.
I think the problem is fixed since the same version of Roboform runs now without Avast going crazy. The problem existed with the VPS version that was pushed yesterday (or the day before that). Anyways I was under the impression that Avast was going to become such a problem with the Wordpad false positive a few days ago and the random false positives across the board of different programmes yesterday that it would have to be dumped entirely. I sincerely hope that those problems are cleared since I would hate to dump my Avast.