Author Topic: WORLD OF WARCRAFT BLOCKING IS BACK  (Read 3744 times)

0 Members and 1 Guest are viewing this topic.

morgganna

  • Guest
WORLD OF WARCRAFT BLOCKING IS BACK
« on: October 05, 2010, 06:29:21 PM »
10/2 update blocked logging in.  Then everything was fine for a couple of days.  As of this morning the problem is back again.  Same exact problem that that thousands reported 10/2.

TechDude

  • Guest
Re: WORLD OF WARCRAFT BLOCKING IS BACK
« Reply #1 on: October 05, 2010, 08:43:26 PM »
Yes indeed. Had to add the exclusion again to get WoW working.

Not impressed  :-\

Jiminimonka

  • Guest
Re: WORLD OF WARCRAFT BLOCKING IS BACK
« Reply #2 on: October 05, 2010, 08:50:11 PM »
Same here, telling me its a Malware and blocking it until I turn off the File Shield. There is no file in the chest, but this is the log file.

Code: [Select]
05/10/2010 19:37:04 C:\ProgramData\Blizzard Entertainment\Battle.net\Cache\24\e0\24e0dab53762d83c513db9897ebb8fccf7cc7bf83079d47de361f72646196792.auth|>[UPX] [L] Win32:Malware-gen (0)
While moving file to chest, error occurred: Virus chest server is not running. RPC communication failed.
During the file delete, error occurred: The system cannot find the file specified

Offline Nightwalker097

  • Jr. Member
  • **
  • Posts: 21
Re: WORLD OF WARCRAFT BLOCKING IS BACK
« Reply #3 on: October 05, 2010, 08:56:30 PM »
Yes, I am having the same problem. Guess the fix they had did not get rolled into the updates for today.

halcinlatsmir

  • Guest
Re: WORLD OF WARCRAFT BLOCKING IS BACK
« Reply #4 on: October 06, 2010, 08:33:01 AM »
I have also had to exclude warcraft folders so I can continue to play.

I hope someone from Avast will make a public announcement when this problem has been properly fixed.

Dch48

  • Guest
Re: WORLD OF WARCRAFT BLOCKING IS BACK
« Reply #5 on: October 06, 2010, 08:49:03 AM »
As of the 101005-1 update, everything is back to normal----for now

ReddGator

  • Guest
Re: WORLD OF WARCRAFT BLOCKING IS BACK
« Reply #6 on: October 07, 2010, 08:32:13 PM »
I have exactly the same problem, and I too had to enter the exclusion that Blizzard posted.  I'm not impressed either.