Instructions for Windows 7 PCs Bricked by New AVG Free Version

December 3rd, 2010 by Anna Attkisson, LAPTOP Managing Editor  

If you’ve downloaded the latest, mandatory 2011 AVG Anti-Virus Free software update, all is not necessarily lost. According to a report by PCWorld, the December 1 update caused 64-bit Windows 7 PCs to breakdown completely. The update, when it runs the code that requires the PC to restart, causes PCs to present the c0000135 error that prevents them from booting fully.

AVG has pulled the update to keep the problem from spreading. And the company has offered the following step-by-step instructions for fixing the glitch.

  1. Use the AVG Rescue CD to boot
  2. When the CD launches, select Utilities > File Manager
  3. Go to the mounted system drive, usually labeled /mnt/sda1/
  4. From there go to the folder labeled /Windows/system32/drivers/
  5. Then rename all files starting with avg using the F6 key by adding the suffix .sys or .bak. This includes files with names such as avgldx86.sys and avgtdix.sys. This creates a backup of those files.
  6. Remove the CD
  7. Press CTRL + ALT + DELETE to reboot. This will stop AVG from being involved in the boot process.
Comments (3 Responses) 

Our Related Content

From Other Sites

Related Deals

 

3 Responses to “Instructions for Windows 7 PCs Bricked by New AVG Free Version”

  1. CW Says:
    December 3rd, 2010 at 10:15 am

    This fix does NOT work on every system. I had to rename the entire AVG folder in Program Files (x86) to “Garbage” or anything else. If you don’t have a disk drive in your laptop like me, do this:

    1. Press F8 during boot-up and choose the first option “Repair your computer”
    2. Follow the prompts and login until you get to the main menu
    3. Choose the last option to a command prompt
    4. Rename the AVG program folder within Program Files (x86) – This location can be different according to your install. I have a system reserved partition that mounts as C: within the repair console so my Program Files (x86) directory is on D: oddly enough. The command to use is “rename D:\Program Files (x86)\AVG D:\Program Files (x86)\Garbage”. You must have the proper location in the command or it obviously will not work. You may need to look around a bit if you can’t remember where you installed the program.

  2. AVG Technologies Says:
    December 3rd, 2010 at 1:24 pm

    We’re very sorry for the inconvenience. Over the past 24 hours, AVG has had two update issues. The problems affected Windows 7 users on 64-bit products. As soon as we were first notified about these issues, we immediately began fixing the problems. AVG is taking swift action on this matter. We remain committed to our customers, and, as such, we are taking the following actions:

    1-Updates have been issued for both of these issues and are currently being propagated to the broad AVG user base.

    2-For the next 48 hours, we are offering free technical support to our entire user base; anyone who has been affected by either of these issues.

    PAID CUSTOMERS: Support for System crash after the recent AVG 2011 update 3292 (BSOD)
    If you have encountered the above mentioned issue with the latest AVG update and FAQ 4079 didn’t help you, please contact our English support team by dialing the following numbers:

    1-Home and Free customers: 24/7 support +1-877-367-9933

    2-Business customers: 9:30am-6:30pm EST +1-828-459-5436 or skype:avg-nc
    You can also email us at updateissuehelp@avg.com.

    FREE CUSTOMERS: Support for System crash after the recent AVG 2011 update 3292 (BSOD)

    1-If you have encountered the above mentioned issue with the latest AVG update and FAQ 4080 didn’t help you, please contact our English support team by dialing the following number:

    2-24/7 support: +1-877-367-9933

    You can also email us at updateissuehelp@avg.com

    AVG sincerely regrets any inconvenience this issue has caused and we are ready to help you resolve this as quickly as possible.

  3. TC Says:
    December 3rd, 2010 at 7:49 pm

    I’ve had the crash after an updating the free version (which I’ve been using for over 1yr). I did not do precisely the instruction provided above (b/c it didn’t see at the time) but, on my own, I moved everything in /Windows/system32/drivers/avg* to another folder. Didn’t work. I ultimate ended reloading the OS. Thanks AVG!!!

    I’m staying *far* anything from AVG from now on….

Leave a Reply

Featured Sponsors