Panda AV is having a bad day

COMODO told me that Part of Avid MC was a Virus yesterday (c:\program files\avid\editor transcode\transcodeservice\servicescripts\setsecdescbg.exe) not cool.

Do not let users reboot their machines for the time being. How can you stop them?

thanksajdotcom

If the solution to a problem is "don't reboot", that's a pretty sad solution.

scottalanmiller

@thanksajdotcom said:

If the solution to a problem is "don't reboot", that's a pretty sad solution.

Hence why the panda is sad.

thanksajdotcom

@scottalanmiller said:

@thanksajdotcom said:

If the solution to a problem is "don't reboot", that's a pretty sad solution.

Hence why the panda is sad.

Agreed.

scottalanmiller

The Panda just had a slight sneeze.
Youtube Video

thanksajdotcom

@thecreativeone91 said:

The Panda just had a slight sneeze.
Youtube Video

That's funny!

nadnerB

nadnerB

Annnd because Red Panda's are awesome:

Dashrender

I got bit by this - I'm almost more sad I didn't get to bring this to group

We got hit with this at 7:45 this morning. Of course at first we weren't sure what was wrong (but looking at the streams of emails coming in from out AV some of them claiming files in the AV folder were bad made me think the AV was suddenly broken).
I started a mad dash at first thinking I should tell everyone to shut down their computers, but quickly rethought about that and instead just told everyone 80+ people to just walk away - stop using your computers (in retrospect I should have told them to get off the network too). I was running under the assumption that a bad DAT has been pushed (felt awesome to be right) and I grabbed a stack of unused laptops and started booting them up, disconnecting from the internet as soon as possible (disable wireless) and then proceeded to uninstall the AV. This worked! I was in business with machines that didn't seem to have the issue. We handed these machines around to get key areas access to our main applications. This surprisingly took a long time, finally around 11:30 we received notice via email (I called support and left a voicemail since they didn't answer - and still now 12 hours later still no call back) that they were aware of the problem, had pulled the bad DAT and were researching solutions to the affected machines.

around 12:30 I was able to start checking all of the computers around the office and found that we only had 15 machines that actually had downloaded the update and need to be fixed. As of now I'm still waiting on the aforementioned fix.

Damn it's been one hell of a day!