Windows 7 Ultimate 64Bit: manual update does not work since Dec 16th.

[system]

@Tech post:19

Something weird here:

1. Bad Windows version detection.
2. Access error.

But, I wish I could see “all” the lines of the log and not a stripped version of them.
Maybe you could upload to a free file storage service and post here the link to it. Thanks.

I do not understand what you mean by “stripped version”?
I copied the last part of today starting with

30.12.2011      11:10:50.000    1325239850      (null)  Started: 30.12.2011, 11:10:50

[Lisandro]

@ady4um post:20

But that’s in addition to the possibility of the full VPS indeed having some problem, independently (or not) of the wrong report of Windows version.

Sure. The problem could be on the updater.
Maybe if he runs the internal update (repair of Control Panel will work), we can compare the logs.

@PMaff post:21

I do not understand what you mean by “stripped version”?

Are you using this file? C:\ProgramData\AVAST Software\Avast\log\Setup.log

[system]

@Tech post:22

@ady4um post:20

But that’s in addition to the possibility of the full VPS indeed having some problem, independently (or not) of the wrong report of Windows version.

Sure. The problem could be on the updater.
Maybe if he runs the internal update (repair of Control Panel will work), we can compare the logs.

@PMaff post:21

I do not understand what you mean by “stripped version”?

Are you using this file? C:\ProgramData\AVAST Software\Avast\log\Setup.log

Yes, C:\ProgramData\AVAST Software\Avast\log\Setup.log
Shall I save that to some other place and try another repair?

[Lisandro]

@PMaff post:23

Shall I save that to some other place and try another repair?

No need for that. The new (internal) repair will append the log at the end of it.

[system]

I may have missed it, but I didn’t see any VPS updates in the log besides the one for 2011DEC16, which according to the posts was successful after the latest repair and reboot.

So, if the VPS full update was reporting that info in the same log, I have not seen those attempts for 2011DEC29 or 2011DEC30 in it.

[system]

@Tech post:24

@PMaff post:23

Shall I save that to some other place and try another repair?

No need for that. The new (internal) repair will append the log at the end of it.

Tried the repair via Windows System Control (it is named different in German),
the Avast dialog comes up,
I select “Repair”,
and there I get the error:

http://img6.imagebanana.com/img/mrsq6gmz/thumb/RepairError30122011.jpg

Logfile from this error dialog is attached.
That is the point where I made a complete
uninstall, reboot, install, reboot,
vps update with the Dec 16th update,reboot
the last time.

[Lisandro]

Something is wrong with the vpsupd.exe.
Nothing is being logged in my computer, no visual return (window) come after I run it… Nothing happens.
I’m sure all the update/repair tasks are being logged.

Let’s try two things:

1. chkdsk /F
2. Set proxy to “None” into avast settings.

Reasons for that: the error on signature and the infamous error 0x20000011.

[system]

@Tech post:27

Something is wrong with the vpsupd.exe.
Nothing is being logged in my computer, no visual return (window) come after I run it… Nothing happens.
I’m sure all the update/repair tasks are being logged.

Let’s try two things:

1. chkdsk /F
2. Set proxy to “None” into avast settings.

Reasons for that: the error on signature and the infamous error 0x20000011.

What does that error 0x20000011 mean
and why should I check the disk?
It is a new system where I checked the disk just recently.
I copied all the vpsupd.exe back onto a USB stick and
back on my Linux machine.
vpsupd.exe are ok according to their checksums and
the diff that I made on my Linux machine.
So if the vpsupd.exe would be different from the ones
I downloaded then I would get some error when doing a diff.

Meanwhile I tried all the vpsupd.exe updates.
The following do not show anything, not any visual return window:
2 vpsupd.exe from 2011DEC27
1 vpsupd.exe from 2011DEC29
1 vpsupd.exe from 2011DEC30
These files also do not log into the setup log when executed.

The update from 2011DEC18 finally showed that all is up to date
(although Avast “thinks” that the last update was 2011DEC16)
The part of the log after applying 2011DEC18 is attached.

Edit: I did the disk check, Windows 7 says that all is ok.

[system]

@PMaff,

Independently of the full VPS update, the repair of avast in your system is failing.

You don’t need to uninstall it. Just download the setup_ais.exe (not the VPS exe), right click and “run as administrator” so to install it over the current installation. Once the installation finishes, reboot.

After the reboot, the date of the definitions might be old, but at least avast would be repaired.

Trying to fix the definitions updates in your system is not wise if avast itself is not “perfect”.

To be clear, I have no way to know if you current installation is OK or not. It may be just the installation package and not the program itself. But anyway, I would recommend re-downloading ANEW and installing a new setup_ais.exe with “run as administrator” and reboot.

The VPS update problem should be of second priority for you if avast installation itself is not solved.

[system]

@ady4um post:29

@PMaff,

Independently of the full VPS update, the repair of avast in your system is failing.

You don’t need to uninstall it. Just download the setup_ais.exe (not the VPS exe), right click and “run as administrator” so to install it over the current installation. Once the installation finishes, reboot.
…

setup_ais.exe ?
Where do I get this?

Or do you mean the Setup file setup_av_pro.exe?
That’s something I’ve already done.
md5sum of the setup file: b5d0d7c09c5d34062768386cc62fb47e

[system]

@PMaff post:30

setup_ais.exe ?
Where do I get this?

Or do you mean the Setup file setup_av_pro.exe?
That’s something I’ve already done.
md5sum of the setup file: b5d0d7c09c5d34062768386cc62fb47e

Sorry, for some reason I though you had AIS, not Pro. Anyway, I know you already did an uninstall and reinstall before, but now you just reported that the recent repair attempt failed.

You shouldn’t need a new uninstallation. Downloading ANEW the setup_av_pro.exe and installing over your current install (and then reboot) should be enough to repair the current installation, but probably not the definitions.

Re-read my previous post, replacing “setup_ais.exe” with the correct “setup_av_pro.exe”. Of course, using the latest stable version only.

Better yet, I would recommend downloading and installing first the original English latest stable version, reboot and then change the language settings and reboot again.

[Lisandro]

PMaff, you can test this or that…
Right now, after all this mess, I suggest an installation from scratch:

1. Download the latest version of avast! Uninstall Utility and save it.
2. Download the latest avast! version and save it.
3. Uninstall avast from Control Panel (if possible). If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after that.
4. Run the avast! Uninstall Utility saved on 1. If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after you’ve run it.
5. Install avast! using the setup saved on 2. Boot.
6. Register your free copy or add the license key for Pro. Or even upgrade your key from old versions.
7. Check and post the results. If, for any reason, you did not solve, try doing the step 3 in Safe Mode anyway.

[system]

@Tech post:32

PMaff, you can test this or that…
Right now, after all this mess, I suggest an installation from scratch:

1. Download the latest version of avast! Uninstall Utility and save it.
2. Download the latest avast! version and save it.
3. Uninstall avast from Control Panel (if possible). If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after that.
4. Run the avast! Uninstall Utility saved on 1. If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after you’ve run it.
5. Install avast! using the setup saved on 2. Boot.
6. Register your free copy or add the license key for Pro. Or even upgrade your key from old versions.
7. Check and post the results. If, for any reason, you did not solve, try doing the step 3 in Safe Mode anyway.

I tried:

1. booted to safe mode at first, uninstalled Avast without any problems
2. reboot
3. downloaded that avast! Uninstall Utility on another machine,
   copied it to the UBS stick
   then put it on the Windows 7 machine.
4. reboot to safe mode as said on the webpage of the Uninstall Utility.
   Uninstall Utility showed the correct directory and uninstalled without
   problems.
5. reboot
6. installed the already downloaded 6.0.1367 with md5sum
   b5d0d7c09c5d34062768386cc62fb47e
   which is the same when you download it now.
7. when installing I use the key that I always used
   During install I get one message (of course, I am offline but why
   does Avast need some server at this point?):
   
   http://img6.imagebanana.com/img/ves0gcpx/thumb/ErrorInstallCannotconnecttoserver.jpg
   
   but installation goes on and says “Successful” at the end.
8. reboot
9. install of updates from 2011DEC16
10. reboot
11. avast shows that update is from 2011DEC16
12. tried to install update from 2011DEC18, get message that all is up to
    date (behaviour is still the same) so the error is not solved
13. reboot
14. try the update from 2011DEC30 and I got no ready message.
    Avast still says the last update was 2011DEC16

So the error is not resolved by this erase/install cycle.

Edit: wait a minute.
When looking at the logs I see that after installation Avast says:

30.12.2011	16:17:13.000	1325258233	(null)	Started: 30.12.2011, 16:17:13
30.12.2011	16:17:13.000	1325258233	(null)	Running setup_ais-557 (1367)
30.12.2011	16:17:13.000	1325258233	(null)	Operating system: Windows 7 ver 6.1, build 7601, sp 1.0 [Service Pack 1] x64

and when I start the 2011DEC16 update it says:

30.12.2011	16:21:47.000	1325258507	(null)	Started: 30.12.2011, 16:21:47
30.12.2011	16:21:47.000	1325258507	(null)	Running setup_ais-557 (1367)
30.12.2011	16:21:47.000	1325258507	(null)	Operating system: Windows Vista ver 6.0, build 6000, sp 1.0 x64

Is it possible that the 2011DEC16 update runs ok but ruins it all?

Edit: I’ve redone the above points.
Difference: in the above I installed the English version so that you don’t have
problems reading the dialogs. The English Version wants some server when installing.
This time I tried the German version (as before) and there was no question about some server, which is strange.
This time I omitted update 2011DEC16 and tried 2011DEC30 at first.
2011DEC30 did not display any success message and it did not
put something into the logfile.
Tried 2011DEC18 afterwards and got the bug
http://www.imagebanana.com/view/x9c1mf9m/ErrorcodesUpdate18122011.jpg
2011DEC18 wrote into the logfile that the OS is Windows Vista.

[system]

Greetings from France
Got the same problem with Windows XP since December 16th
I submited the problem to the Avast support and here is the answer :

Hello,

Thank you for contacting our support center with your concerns.

I have tested the virus update file on Windows 7 and Windows XP and you are right that it is causing the problem.

The error log has been sent to our developers team and the issue will be hopefully resolved in a due time.

Best,

Merry Christmas and a happy new year from avast! team

http://public.avast.com/reseller/Christmas/pf-2012-3.jpg

Petr Bucek
Technical Support

AVAST Software a. s.
Budějovická 1518/13A
140 00 Prague, Czech Republic

[system]

@fbedin post:34

Greetings from France
Got the same problem with Windows XP since December 16th
I submited the problem to the Avast support and here is the answer :
…

Ok, so they know that there is an issue and they are working on it
since they answered you.

Would be good thing if they put some “Attention!” message on the download page
http://www.avast.com/download-update

[system]

@PMaff post:33

Is it possible that the 2011DEC16 update runs ok but ruins it all?

Yes, it is possible. That was the whole point of my suggestion (without the uninstall).

I would bet that the repair will again fail now. I don’t know if it is worth of uninstalling again, and I don’t know if it is worth of running the setup of Avast Pro over your current install. It may be possible that when they solve the VPS problem, that it will also solve the current corruption of avast in your system.

Since the solution may take some days (I don’t really know), I would at least run the setup over to solve the current bad status of your installation, and would keep the last definitions date that you know for sure it worked correctly without tampering with the system. It’s up to you.

About Avast Team knowing about the potential problem, they already knew since the first reports, but yet no official comment about it (nor comfirming nor denying the problem).

[system]

to ady4um : I don’t think so

I tried with an old image of my Windows XP (2009) and it crashed as well with the update

[system]

@fbedin post:37

to ady4um : I don’t think so

I tried with an old image of my Windows XP (2009) and it crashed as well with the update

I don’t understand what you mean or what you are not agreeing with. My posts were directed to PMaff, if that helps you.

[system]

@ady4um post:38

@fbedin post:37

to ady4um : I don’t think so

I tried with an old image of my Windows XP (2009) and it crashed as well with the update

I don’t understand what you mean or what you are not agreeing with. My posts were directed to PMaff, if that helps you.

I’m just saying that the 16 december manual update is not responsible for the crash we have now with the manual updating. It did not ruin all.

[system]

@fbedin post:39

I’m just saying that the 16 december manual update is not responsible for the crash we have now with the manual updating. It did not ruin all.

I don’t think anyone said so, and we still don’t have any official info about since when nor why the offline updates are failing. Let’s concentrate only on what PMaff is reporting in this topic.