Win32:Kryptik-PFA [Trj] - False Positive ? 

schester · 2015-05-07T00:42:42.000Z

schester post:76:

HAAAAALP post:74:

Assuming you use the Enterprise Administration Console and have already deployed the latest definitions that correct the false positives: create a “Manipulate Virus chest” client-side task and check the box to “Restore all files from the Infected folder of the Virus Chest in which no infection is detected using the current virus database”

This didn’t appear to be working at first, but looks like it may be now.

Do I want to have the task remove the files from the virus chest after restoring them?

Well this seemed to only work on one computer. I ran the task on the group and checked another computer that said done and the files weren’t there. I then tried running the task on that single computer and waited for it and the task still reported done, but the files were not restored. From the local machine I was able to restore them and it instantly worked.

What gives?

system · 2015-05-07T01:08:46.000Z

Unfortunately I can’t seem to find the option to restore files from the virus chest by using the Small Business Administration Console. Does anyone know how to do this? Or do I have to upgrade/migrate to the EAC to be able to do this?

We had major issues with this as it affected custom software on one of our servers and would love to be able to reverse this the quickest way possible vs. visiting every machine manually.

Thanks

Michael504 · 2015-05-07T01:12:03.000Z

danf post:71:

Yup, just swapped the entire company to Bitdefender. This was out of control bad and Avast will never see another dollar of our money.

I have had bitdefender before, slows the machine down too much and it missed stuff.

system · 2015-05-07T03:38:33.000Z

Can a system restore bring back files removed during an Avast boot scan?

Before I knew about this false positive I thought my whole computer had somehow been infected. Now I’m worried I deleted essential files. I didn’t send them to the chest like I should have. :-[

system · 2015-05-07T12:35:07.000Z

schester post:78:

Well this seemed to only work on one computer. I ran the task on the group and checked another computer that said done and the files weren’t there. I then tried running the task on that single computer and waited for it and the task still reported done, but the files were not restored. From the local machine I was able to restore them and it instantly worked.

What gives?

I’ve been doing it manually as well. What a nightmare. I just had 200 computers blow up yesterday. It cost my client a LOT of money to have everyone go down like that. It ate everything from email to database software. Really really really bad. I was able to get the update pushed out to the bulk of them last night, but there were still a handful that required manually restoring files from the vault on the local machine to work properly. I can’t believe how bad this is. I haven’t even gotten a generic emergency support email or a “sorry” email or anything either, disappointed that there’s basically been radio silence from Avast. I had to go online & dig to find this thread to figure out what was going on.

Will I change antivirus vendors for the future? Not sure. Mistakes happen. The software has been very good up until this point, and they did roll out the fix-it patch same-day. I’ve had this happen with Windows Updates as well, so no company is immune to problems of this magnitude. The Avast fix hasn’t been 100% effective for every machine, but as of this morning I have 95% of my users back up & running. I understand that mistakes happen. Just a bit upset that they didn’t even send out an email notice or anything for a status update.

polonus · 2015-05-07T12:50:32.000Z

Hi kaidomac,

Lucky for those that skipped that update. When some things go wrong, they often go wrong big scale.
All vendors suffer from these mishaps some day or other, “someone pushing a wrong handle there”.
Prepare for it in the future with a pre-update emergency back-up scheme, but that is wisdom in hindsight.

polonus

mmanous · 2015-05-07T13:07:03.000Z

kaidomac post:82:

schester post:78:

Well this seemed to only work on one computer. I ran the task on the group and checked another computer that said done and the files weren’t there. I then tried running the task on that single computer and waited for it and the task still reported done, but the files were not restored. From the local machine I was able to restore them and it instantly worked.

What gives?

I’ve been doing it manually as well. What a nightmare. I just had 200 computers blow up yesterday. It cost my client a LOT of money to have everyone go down like that. It ate everything from email to database software. Really really really bad. I was able to get the update pushed out to the bulk of them last night, but there were still a handful that required manually restoring files from the vault on the local machine to work properly. I can’t believe how bad this is. I haven’t even gotten a generic emergency support email or a “sorry” email or anything either, disappointed that there’s basically been radio silence from Avast. I had to go online & dig to find this thread to figure out what was going on.

Will I change antivirus vendors for the future? Not sure. Mistakes happen. The software has been very good up until this point, and they did roll out the fix-it patch same-day. I’ve had this happen with Windows Updates as well, so no company is immune to problems of this magnitude. The Avast fix hasn’t been 100% effective for every machine, but as of this morning I have 95% of my users back up & running. I understand that mistakes happen. Just a bit upset that they didn’t even send out an email notice or anything for a status update.

I’ve had zero luck running the restore task as well. I temporarily disabled Windows Firewall on both my AEA server and the client I was trying to run the restore task to. It still didn’t work with both firewalls turned off.

I also discovered that I was unable to use the Remote Virus Chest feature (I’ve never had a need before now). For those that don’t know, you need to open port 135 and 16108 for the Remote Virus Chest to work. This can be configured in Group Policy. Computer Configuration → Policies → Administrative Templates → Network → Network Connections → Windows Firewall → Domain Profile → Windows Firewall: Define inbound port exceptions. At least now I don’t have to go office to office or use VNC to manually restore.

system · 2015-05-07T13:12:34.000Z

This is just great. i called support and they are saying i need to submit a support ticket. which i did yesterday I have over 100 pc down and they don’t even want to talk to you. what a POS customer service.

system · 2015-05-07T13:44:22.000Z

polonus post:83:

Hi kaidomac,

Lucky for those that skipped that update. When some things go wrong, they often go wrong big scale.
All vendors suffer from these mishaps some day or other, “someone pushing a wrong handle there”.
Prepare for it in the future with a pre-update emergency back-up scheme, but that is wisdom in hindsight.

polonus

The difficulty is two-fold:

Receiving email viruses that come out same-day
Quantity of users

As much as I hate not having time to test A/V updates on a test group beforehand, it’s important to have the updates come in as fast as possible because I’ve run into issues not doing that - as soon as a virus fix is identified by Avast, added to the database, and rolled out to users, they are protected. So to me, it’s worth the risk for the occasional hiccup like this to have the most up-to-date protection possible, because it has bitten me before in bad ways with zero-day exploits. Plus, I support several companies & several branches as well, so it’s not really feasible to babysit everything 24/7 due to workforce budgets being what they are.

The second issue is quantity of users. Even with backups, reverting 200 users who have physical machines & are not on a Terminal Server is a logistics nightmare. I spent all last night trying to fix things remotely & have had to go on-site to patch up all the little bits & pieces remaining. Reverting to a prior backup is possible, but then the users lose all of their work for the day (times however many users you have), versus just restoring from the vault. Although restoring from the vault hasn’t fixed 100% of the issues I’ve run into, so I’ve had to do some further work, like re-installations of certain software.

Very frustrating all around.

system · 2015-05-07T13:50:03.000Z

amit12 post:85:

This is just great. i called support and they are saying i need to submit a support ticket. which i did yesterday I have over 100 pc down and they don’t even want to talk to you. what a POS customer service.

I have not had great CS from Avast in general, which is probably my only real complaint. The pricing & feature set is great, it does a great job of detections (other than this snafu), and it doesn’t slog down your PC. I use different A/V packages depending on the client, but aside from the mediocre customer service, I’ve grown to really like the product & service because it runs well & runs reliably. So again, not sure if I will dump them after this, but their response to this issue has been rather dismal, which is very annoying when I’m stuck explaining to a paying customer why all of their computers are down & why their $100-an-hour engineers can’t work. I think they have a great product & I understand that occasionally things go wrong, but Avast needs to step it up with their customer service responses. What I’m hearing today is "Why didn’t we just stick with Norton?

system · 2015-05-07T13:53:23.000Z

has this junk been resolved yet? I have not seen a thread indicating that it has. Quite frankly I am quite astounded that the product in itself with that update acted as a Trojan by definition.
So what is the final statement? Is this problem fixed yet??

Pondus · 2015-05-07T14:08:19.000Z

jbarth post:88:

has this junk been resolved yet? I have not seen a thread indicating that it has. Quite frankly I am quite astounded that the product in itself with that update acted as a Trojan by definition.
So what is the final statement? Is this problem fixed yet??

see post #67 also here https://forum.avast.com/index.php?topic=170730.0

system · 2015-05-07T14:16:39.000Z

jbarth post:88:

has this junk been resolved yet? I have not seen a thread indicating that it has. Quite frankly I am quite astounded that the product in itself with that update acted as a Trojan by definition.
So what is the final statement? Is this problem fixed yet??

This is what has worked for me:

Make sure your server & clients have the latest Avast updates
Reboot the clients twice (from what I can tell: it grabs then update, then applies the update with the vault issues etc.)
2a. Restore anything from the vault that is still not working (I’ve had a dozen computers or so that didn’t play nice)
2b. Reinstall anything that won’t restore (maybe half a dozen computers that needed apps reinstalled)

As of 10am this morning, I am back to 100%. That was a long night

system · 2015-05-07T14:38:13.000Z

I agree that “mistakes happen” , especially with this type of software.

However, Avast owes it to their users to explain why this happened, and what they are doing to prevent it in the future. This was not some minor problem… but was a very serious issue that had a large impact for many paying customers. If Avast expects us to STAY as their customers, they need to respond and help us understand what they are doing internally to prevent this from happening again.

Further, considering how obviously broken that definition update was, it is clear that Avast does not do any testing of their updates prior to pushing them to production release. That’s not great.

system · 2015-05-07T17:34:30.000Z

Well, my laptop is “working fine”, running like nothing happened, but still my intel/nvidia drivers aren’t running, or at least when I try to open them it gives me an error, like there are missing files and stuff, my cousin which happens to be a tech with this stuff is going to help me, but for sure I’m changing my AV, avast worked well for me, but this is just a no, even though my laptop is “fine”, it isnt. I’m one of the people that had to reboot and had files deleted thinking it would help.

system · 2015-05-07T17:54:57.000Z

BTW - this happened before. December 2009:

“On Thursday 12.3.2009 avast! had a bad false positive issue. At around 12:15 AM GMT (4:15 PM PST) we released VPS update 091203-0 which started flagging hundreds of innocent files as a ‘Win32:Delf-MZG’ Trojan (or, in less common cases, as 'Win32:Zbot-MKK). Among the files affected were high-profile programs produced by Adobe, Realtek, sound card drivers, various media players etc.” - A VPS update 5 hours later solved it.

On April 2011, a VPS update was causing WebShield to report widespread viruses on random websites. Was fixed 5 hours later with a new VPS update.

Again in March 2013 - Avast accidentally flagged Adobe Acrobat as a virus and killed the software for many users - fortunately a repair of the Acrobat software resolved it after a VPS update (3 hour response time).

system · 2015-05-07T20:05:32.000Z

This is a disgrace and not something I expect from my anti virus software. This has created me untold work because I trusted Avast and means I have totally wasted my week trying to fix this rubbish. I truly find it unbelievable and it beggars belief how it got through your release management processes. Yours, a very disgruntled customer. If you put as much effort into ensuring this sort of thing doesn’t happen as you have into scrambling the verification this would not happen, I am sure.

bob3160 · 2015-05-07T20:53:20.000Z

john477 post:94:

This is a disgrace and not something I expect from my anti virus software. This has created me untold work because I trusted Avast and means I have totally wasted my week trying to fix this rubbish. I truly find it unbelievable and it beggars belief how it got through your release management processes. Yours, a very disgruntled customer. If you put as much effort into ensuring this sort of thing doesn’t happen as you have into scrambling the verification this would not happen, I am sure.

This doesn’t happen often but unfortunately I don’t know an AV that it hasn’t happened to.

Pondus · 2015-05-07T21:08:34.000Z

Panda had a big one some weeks ago

www.404techsupport.com/2015/03/panda-cloud-and-antivirus-false-positive-hits-hard/

www.theregister.co.uk/2015/03/11/panda_antivirus_update_self_pwn/

bob3160 · 2015-05-07T21:19:40.000Z

Pondus post:96:

Panda had a big one some weeks ago

www.404techsupport.com/2015/03/panda-cloud-and-antivirus-false-positive-hits-hard/

www.theregister.co.uk/2015/03/11/panda_antivirus_update_self_pwn/

I don’t think we need to rehash the occurrences.
It’s bad enough when it happens and, as I said it’s happened to all of them.

Announcements