Author Topic: [Resolved] Update from 864 to 889 problem  (Read 8133 times)

0 Members and 1 Guest are viewing this topic.

jwall

  • Guest
Re: [Resolved] Update from 864 to 889 problem
« Reply #15 on: January 14, 2011, 01:56:55 PM »
The latest update seems to have fixed this.
I tried direct connection and it went through, no error.

Will keep checking on it though.

Offline Vlk

  • Avast CEO
  • Serious Graphoman
  • *
  • Posts: 11658
  • Please don't send me IM's. Email only. Thx.
    • ALWIL Software
Re: [Resolved] Update from 864 to 889 problem
« Reply #16 on: January 14, 2011, 02:35:59 PM »
Yep, we did some change on the server that should solve this issue (i.e. updates should now work again even in the "direct connection" mode).

Thanks
Vlk
If at first you don't succeed, then skydiving's not for you.

Offline Gopher John

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2098
Re: [Resolved] Update from 864 to 889 problem
« Reply #17 on: January 14, 2011, 02:46:46 PM »
Yep, we did some change on the server that should solve this issue (i.e. updates should now work again even in the "direct connection" mode).

Thanks
Vlk

Vlk,  I can confirm that direct connection mode does work again as Jwall posted.  Thank you.

And, thanks to Jwall for finding the workaround in the meanwhile.
AMD A6-5350M APU with Radeon HD Graphics, 8.0GB RAM, Win7 Pro SP1 64bit, IE11
i7-3610QM 2.3GHZ, 8.0GB Ram,  Nvidia GeForce GT 630M 2GB, Win7 Pro SP1 64bit, IE 11
Common to both: Avast Premium Security 19.7.2388, WinPatrol Plus, SpywareBlaster 5.5, Opera 12.18, Firefox 68.0.2, MBam Free, CCleaner

jwall

  • Guest
Re: [Resolved] Update from 864 to 889 problem
« Reply #18 on: January 14, 2011, 02:48:56 PM »
Yes, thanks for the prompt fix Vlk, and you're welcome Gopher John
« Last Edit: January 14, 2011, 07:11:49 PM by jwall »

Offline Snagglegrain

  • Sr. Member
  • ****
  • Posts: 221
Re: [Resolved] Update from 864 to 889 problem
« Reply #19 on: January 14, 2011, 02:53:26 PM »
Yep, we did some change on the server that should solve this issue (i.e. updates should now work again even in the "direct connection" mode).
Working again here, as stated.  Thanks for the change.  :)