PogoCheats CommunityDownload Cheats | Club Center | Pogo Help
Pogi Constellations | Anagram Solver
Pogo Daily Checklist
January 06, 2026, 03:58:04 PM

This week's Club Pogo challenges!
Yahtzee! Wild : Create 8 Yahtzees this week!
Pogo Daily Sudoku : Collect 45 stars this week!
World Class Solitaire HD : Use the grab power up 26 times this week!

Main Menu

Post reply

The message has the following error or errors that must be corrected before continuing:
Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Note: this post will not display until it has been approved by a moderator.
Other options
Verification:
Please leave this box empty:
Shortcuts: ALT+S post or ALT+P preview

Topic summary

Posted by FreecellFanny
 - November 13, 2008, 04:18:35 AM
Quote from: Homer on November 11, 2008, 12:31:17 PM
AVG sucks!  bbq21.gif

You got that right.  !@#$
Posted by Homer
 - November 12, 2008, 10:11:20 AM
Quote from: Tara on November 12, 2008, 09:48:39 AM
So do you.   :%#

:{: :{: :{:
Posted by Tara
 - November 12, 2008, 09:48:39 AM
Quote from: Homer on November 11, 2008, 12:31:17 PM
AVG sucks!  bbq21.gif

So do you.   :%#
Posted by Homer
 - November 11, 2008, 12:31:17 PM
AVG sucks!  bbq21.gif
Posted by Stinkerbell
 - November 11, 2008, 11:56:33 AM
Thanks for the update, Mayhem.  I don't use it either but enough people do that it's worth posting.  But I would imagine if they have already updated, they can't get online to read your warning.   !@#$ 
Posted by IndianLover
 - November 11, 2008, 11:53:56 AM
tks for info. and boy am I glad I don't have that  :)))
Posted by Mayhem
 - November 11, 2008, 11:52:27 AM
An update for the AVG virus scanner released yesterday contained an incorrect virus signature, which led it to think "user32.dll" contained the Trojan Horses PSW.Banker4.APSA or Generic9TBN. AVG then recommended deleting this file; this causes the affected systems to either stop booting or go into a continuous reboot cycle. So far, the problem only appears to affect Windows XP, but there is no guarantee that other versions of Windows don't have the same issue.

Both AVG 7.5 and AVG 8.0 were affected by the update; a revised signature database has just been published that corrects this issue.


Make sure you update the virus definition file before scanning your system!