7 replies to this topic

[Nvyseal]

images/news/security.jpgAn update from AVG on Wednesday night rendered 64 bit Windows 7 systems unstable after it was applied.

Several Register readers have been affected by the problem, which leaves machines in a continuous reboot loop.

AVG has pulled the problem update (3292) and published an advisory apologising for the cock-up and providing instructions on how to get hobbled systems back up and running again.

Recovering a Blue Screened PC is more involved than simply rebooting in safe mode, as the security vendor explains. Desktop versions of Windows 7 seem particularly prone to the bug.

It's unclear whether or not other versions of Windows are vulnerable to going weak at the knees after applying the misfiring update from AVG. Both free and paid-for versions of the software seem to be problematic.

Users have vented their understandable frustration through AVG's online forum.

AVG hasn't said what caused the problem, but normally such auto-immune snafus occur when security software packages identify a vital Windows component as potentially malign. Such problems are far from unknown in the anti-virus biz and have affected multiple vendors in the past.

Register

[Christopholofigus]

That is why I stick with Microsoft Security Essentials.

Edited by Christopholofigus, 03 December 2010 - 02:08 AM.

[m.oreilly]

Christopholofigus, on Dec 2 2010, 06:07 PM, said:

That is why I stick with Microsoft Security Essentials.

i pushing this too

[scaramonga]

Christopholofigus, on Dec 3 2010, 02:07 AM, said:

That is why I stick with Microsoft Security Essentials.

+3

Although I nearly ditched MSE.

I kept getting the quite popular 'Microsoft Security Essentials OOBE" stopped due to following error; 0xC000000D' in Event Viewer every single day, never affected the running of the software, but dammed annoying. Fixes on the net do not work, nothing worked, uninstall, reinstall, format, delete files, install beta builds of MSE etc, I done them all!! Was pulling my hair out at this one, until, wait for it, I uninstalled the ATI drivers and the errors went away. I thought, what the hell does that have to do with it?

Now, before peeps jump in and say 'here we go' lol , I ain't blaming ATI, as maybe it could be incompatible drivers/software clashing from either side, whatever?? I don't know and I don't care now lol.

This was one of the many problems I did have since installing ATI drivers, but not the sole reason I switched back to Nvidia.

My Event Viewer has been clean since thankfully, and I enjoy Microsoft Security Essentials even more

[os collector]

how they published that kind of update without testing. anyways i am with AVAST

[VROSA]

Quote

anyways i am with AVAST

Me too. I love its daily updates

[hog]

Avast! here too! Actually it's you guys that made me ditch AVG last summer, after reading some thread.

[BlueIce]

I used Avast until I updated my Motherboard. Avast kept causing BSOD even after a clean install of Windows with this new motherboard. I am n ot the only person who got BSODs after getting this motherboard and using Avast. I switched to MSE and haven't looked back. Don't know how well it works but it doesn't slow my system down.