Trying to register the free version of 9.0.2021 on Win7.
On the Registration page in Avast, If I press the “Register now” button, I get a “Loading” box with a spinning wheel, but it does not progress any further. The box then disappears after about 5 seconds.
I have tried requesting an offline key by email. But it shows the key “is not a valid licence key” message after I insert it.
So how does one register this software?
Is there a link to an older version for download, like 9.0.2018?
It appears the licence keys generated by the key generator on the Avast server are incompatible with the current release version.
The solution to this problem is to uninstall 9.0.2021. Reboot. Then install 9.0.2018. Input the licence key from the email. Then install 9.0.2021.
Another worry is Avast does not publish the MD5 checksums on their web site. So how do you know if the Avast executable has not been compromised during the download? This is basic stuff and they have failed to impress me.
MD5 for Avast 9.0.2021
27D9039FC25B4418755AC54E0E09FA32
MD5 for Avast 9.0.2018
18D3A804CB97BB62DBC5AC7C957CD3E7
To find 9.0.2018 to download, just do a search using the above MD5, as I could not find old versions anywhere on the avast website.
Maybe Avast could add MD5 checksums to the file downloads page and also on the virus definition updates page.
Hi Jagdwurst! Did you try repairing avast via add/remove?
If that doesn’t work do the following!
So how do you know if the Avast executable has not been compromised during the download?avast has that covered during install as well as after install (eg: self defense) If the download is compromised avast will not install and/or give you an error.
How do you know if these files from here are authentic:
http://www.avast.com/en-us/download-update
There is no https certificate. I do not know if this page is really avast or not?
There is no MD5 for the files. I do not know if I have downloaded a valid file or a compromised file?
I could run it, but then it would be too late.
Whenever I download files like this elsewhere, there is always an MD5. At avast there is not. It is worrying.
How do you know if these files from here are authentic: http://www.avast.com/en-us/download-updateEh, perhaps because it is the official avast website? DUH! :P
And what use is it to have a md5 mentioned at the same website you are downloading from?
None at all !
Let’s say I have a website https://www.ispreadmalware.yes
You download avast-setup.exe (or whatever it is called) from there and you see the md5 on the same site.
You check the md5 from the downloaded application with the one that is on the website and they are the same.
The only thing you know is that the md5’s are both the same.
It doesn’t mean you have a authentic file.
Unless there is an https certificate you cannot confirm if it is the official avast website. The avast webpage you see, could be different from the page I see. I could duplicate the avast domain and stick it on a server outside your house, or in the next country along the cable, and intercept your traffic to avast and redirect it to this server. You would think it is legitimate because it looks right. This is one of the reasons why sites use https. The certificate is the proof that the domain is valid and not a middleman.
If the MD5 is on a page with https, I know the file is authentic and provided by the authentic source.
Here is an example on how to do it right. Link and checksums on the same https.
https://www.openssl.org/source/
As antivirus software sits close to the operating system, you need to trust it is authentic. Avast make no effort at all to build trust. I think they are pulling my leg.
Avast make no effort at all to build trust
Apparently that’s not what it takes to build a big user base.
In many ways Avast acts more like malware than a serious anti-malware solution. Big Shiny Button tricks to get you to upgrade? Tiny little checkboxes to install Chrome? Pop-ups that supposedly because of a years-old bug advertise things instead of letting you know the database is updated?
But you CAN configure around this stuff, and it DOES work. There IS a better mousetrap in there.
-Noel
Oh, and I don’t mean to be too terribly picky, but you used the word trust…
Let’s say all the things you say were satisfied (https, MD5, etc.). You’re still trusting Avast to be a legitimate software package, and not a vector for a cyberattack should your country and Avast’s fall out of favor with one another.
There’s always some risk. And there’s always some benefit.
-Noel
I have the same problem registering version .2021 with Vista. I opened a ticket with tech support last week, and none of the solutions worked. I uninstalled it today after it expired, rebooted, and downloaded it again. As before, the spinning ball appeared without bringing up the online registration form, so as before I did the offline registration. Got the new key by email, and as before, when inserting it per the offline registration via the Settings/Registration/Offline Registration, I get the “xxxxzzzzzzccccc-etc” is not a valid license key! popup.
Seems like Avast! would have fixed it by now if it is a problem with .2018 keys not working with .2021.
Maybe it is a problem with the free version default download via CNET? I suspect that opening another trouble ticket with tech support will not fix anything.
I installed Avast Free 2014 9.0.2021 on a neighbor’s Win7 Pro new install yesterday, and then registered it via the AvastUI shortly afterwards. There was no problem with the process.
should your country and Avast's fall out of favor with one another.Sorry NoelC but that isn't factual. Falling out of favor has nothing to do with Avast. :)
None of my business but just curious about why you would download Avast from CNET.
None of my business but just curious about why you would download Avast from CNET.That's the default download site when you download from the avast website.
Have you tried renewing from within the User Interface ???
The following video shows you how that is done:
http://youtu.be/jmbe2m2gvnQ
What isn’t factual? There’s nothing about my statement that you can dispute.
The FACT is that we have to trust the software we run or we shouldn’t run it.
It makes no difference what example scenario someone cites. The point I was trying to make is that there’s always some risk even if you’re sure the software is genuine - in other words it’s not black and white. Sorry for being too subtle.
-Noel