AVG won't delete Trojan Zbot.IDW
I went to update my AVG and there were 3 Trojan horses - 2 deleted no problem - but Trojan Zbot.IDW will not erase and is held in quarantine in the AVG. In the process of trying to erase this final Trojan horse, a sign with a lock appeared (looking like our trustworthy Mac signs), requesting the password "to make changes" and I entered the password. (Maybe this was a stupid move on my part?) I haven't done any online banking since this happened, terrified my accounts will be compromised/emptied.
There was no option but to contact AVG, which I did, but their system to ask a question is aggravating and finally, very annoyed, I forwarded a short sharp note to them. Surprisingly, at nearly midnight, I received a reply, so I wrote back immediately. - It's now past noon the next day and no answer from AVG. My AVG ap is free, but as I pointed out to them my word of mouth advertising, i.e., "it's a good program for a Mac" (this will change if they don't smarten up soon) is a type of payment.
My basic reaction to what's happened is that this is a set-up by AVG to get you to purchase their product and I am unable to afford it and why I took the trouble to highlight that word of mouth advertising is similar to payment. (As is negative verbal advertising).
The situation is as follows:
1. I cannot connect to AVG
2. Forced into a screen to create AVG MyAccount - please connect to a Zen Network - with a login
Can anyone Mac tell me if my computer's at risk from my possibly dumbo move in paragraph 1 here?
AVG insists you can't just put their Icon in our Mac trash and get rid of it; you must use their de-installer, whatever. Is that true? But if I un-install the AVG what happens to the Trojan horse it's holding?
I'm about ready to move to BitDefender. Any thoughts there? I'm kind of sorry Thomas Reed has gone to be part of that Malware company. He was such a help. However, I've also been given some superb advice here and grateful to anyone who might take the time to answer my questions.
Mac mini, OS X Mavericks (10.9.3), This happened without my knowledge.