Avast free registration key for older versions has a problem!!!

@INGBEAN

Thank you so much!!! :-*
(mein Seelenverwandter ;))

Best regards!
Sky

It is also available here:
https://forum.avast.com/index.php?topic=164936.msg1322691#msg1322691

This problem still persists as of the 19031404 vpsupd

I use Win2K and v8.0.1506

This was on 3/14 :

I tried the 3/10 vpsupd followed by online update. After the 3/10 vpsupd, everything was fine. After the online update it seemed sorta OK. (Actually, after the update I noticed AvastSvc was running more than it should). Then on reboot, Avast wouldn’t start, online update info reported ‘unknown’

I restored a backup build. Then I tried the 3/14 vpsupd directly. Seemed fine until the reboot, then Avast wouldn’t start, online update info reported ‘unknown’

Vpsupd is important for Win2K because I’ve noticed if you haven’t done an online update for a while, it will fail with a ‘not enough storage’ error. Then your only option is vpsupd, or a clean install.

I also use Avast5 and Avast7 on some of my Win2K builds. Updates failed here too.

+1

Sky

The second issue with sse2 instructions should be also fixed now, please try to update VPS to version 190315-00 and let us know, thank you.

I think isn’t because, I’ve 2 XP SP3 machines and another with Windows 7. Avast 5 works fine on Windows 7. A Windows XP machine has SSE2 and the other one haven’t, and both have the proble reported. So I think SSE2 isn’t the problem.
So, it’s a problem with the VPS after March 11th to fail on machines before Windows 7.
With Windows XP SP3 works fine if they have not updated after that date, else after the reebot the red cross appears and Avast service does not works :frowning:

Can you please retest one more, with VPS 190315-00? Thank you.

Checked on the non-SSE2 Windows XP machine, it seems the VPS 190315-00 works fine.
I’ll try on the other (SSE2 compliant) Windows XP later…
Thank you very much.

PD: What was the problem?? :?

Thank you for confirmation. The problem was one of the binaries (namely algo.dll) and the mistake in build servers configurations (the sse2 instructions were used because of some other and apparently unrelated option for Spectre mitigation).

Hello Avast-Team,

it seems, it works now on my Windows 2000-PC with avast!-Free AV 8.0.1497!!! :-* :-* :-*

I had nothing to do.

I started my PC today with the red Cross on the avast-symbol.

After a while the Online-VPS-Updates came in (190315-2) and now everything seems to be o.k.!!!

Registration till 2038 is o.k. again!!! :slight_smile:

Thaaaaaaaaaaaaaank you very much!!! :-* :-* :-*

Yes, on my other Windows XP SP3 PC (SSE2 compliant) now it’s working perfectly.
Booth Windows XP machines working fine with VPS 190315-02 and registered until 2038.
Thank you very much.

OK here too on a Win2k sp4 machine. ;D Only a PIII cpu so no SSE2 here.

Started with 190315-2 on a clean Avast install. Then updated to 190315-4 and it’s still working!

(Who puts that SOLVED thingy in the thread subject line? Me?)

@ Rickajho
As you are the topic starter, you can ‘modify’ the first post in the topic and add [Solved] or [Resolved] to the topics Subject.

As I have in the attached image, but that only changes my post. Yours would change the Subject displayed in the list of topics.

Hello =SKY=!

No Problem, you’re welcome. :-*

Have a nice weekend!
INGBEAN

Hello!

A summary:

In everyone’s interest, I want to declare a big THANK YOU to Avast (service and development) team!
It wasn’t a given that support for “old” software versions or operating systems is assured by companies.
Such cases are superb examples for service-oriented enterprises.
Keep it up! 8)

Best regards from Austria!
INGBEAN

+1 :slight_smile: :slight_smile: :slight_smile:

Sky

Yes, thanks to Avast for continuing to help the legacy OS users!

Theoretically, Avast 8.0.1506 and above is supported. I was kinda surprised how many Avast8 users chimed-in when the update system went buggy.

BTW, the fix worked for Avast5 and Avast7 also. These I still use with some builds on my Win2K Pentium 3 machine as they tend to use the OS resources less: Every bit helps when the machine is 550Mhz and limited to 256MB RAM

Ouch! And I thought I was hurting running w2k at 800 Mhz with 512MB RAM. ;D