My avast isnt updating

??? , I was really happy that I’ve atlast had the ultimate antivirus for my simple laptop, but recently, when i try to update the program which is avast home edition 4.7, it gives me this message,( Last encountered error: Other HTTP error (404), while trying 69.93.98.186:80//iavs4x/vps-7110100.vpu)
and i dont know why it doesnt want to update, and here is a second time i try to update it,
(Information about current update:
Last encountered error: Other HTTP error (404), while trying 74.54.25.2:80//iavs4x/vps-7103100.vpu)
and thank you ;).

Well error 404 is page not found, so that is quite strange I have just tried a manual update and that was able to check, though because my avast is fully up to date.

Earlier it was able to complete a VPS update 071103-0.

The latest version of avast is 4.7.1074 is that what you have ?

The update check appear to have been trying to get updates from the 1st of Nov to today 3rd of Nov. So it may appear that you also didn’t get the 2 VPS updated on the 2nd Nov, 071102-0 and 071102-1.

I assume you have tried a manual update ?

Please, post the last 100-150 lines of avast log: C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log

Also check:

  1. If your subscription allows the update right now (i.e., if it is not expired). Home (free) version need registering each 14 months.

  2. If your firewall settings and allow avast.setup to connect.
    If you’re not sure, just turn off your firewall (to be sure the update failure is not due to it).
    Maybe you should ‘remove’ avast.setup entry, try to update, receiving a new alert from the firewall, allowing it and checking it to remember.

  3. Check your proxy settings into avast!:
    Left click the avast icon > Settings
    Update (Basic) > Details > Proxy
    Make sure your browser is not set to “Work Offline” (this option is generally in the File menu).
    If it doesn’t help, try switching from “Auto-detect” to “No proxy” (I’m assuming you’re not connecting to the Internet via proxy).

Indeed, like David said, the 404 error is strange…