No sir, AVG updated and caused corruption of its own drivers making it unbootable then someone else hosed the file system trying to make the AVG .sys files .bak to allow the machine to boot and uninstall AVG.
No sir, AVG updated and caused corruption of its own drivers making it unbootable then someone else hosed the file system trying to make the AVG .sys files .bak to allow the machine to boot and uninstall AVG.
Apparently AVG has had this problem since Dec. 2010 but is playing hell trying to find the root cause of it. At one point, they were on Cnet trying to insinuate that they may not be at fault here but, with swiftness, had their ass handed to them by some very knowledgeable yet irate users affected by this problem.
And for the record, the "someone else" wasn't me.
My computer skills don't even qualify me to be a "someone else" yet. lol
Comment