Developer: Problems with updating 268 to 278

[kubecj]

Hello,

this problem _very probably_ occurs to the customers, which manually updated to version 268. There was one additional 268 update. This bug shouldn't affect the users of other versions.

The bug in the setup lies in inability to delete broken package and trying again to do the wrong diff.

The solution:
1) tested one:
Download manually:
http://www.avast.com/iavs4x/setup_av_pro-116.vpu
http://www.avast.com/iavs4x/setif_av_pro-116.vpu
put them into avast4\setup and rerun program update manually

2) untested one (looking for brave young man to test it)
Delete files setup_av_pro_10c.vpu & setif_av_pro_10c.vpu from avast4\setup directory and rerun program update manually.

We apologize for the inconvenience, the setup/update program is after serious rewrite and is still buggy (at least I hope that 278 is much, much better).

HTH,

[Lisandro]

Hello,

this problem _very probably_ occurs to the customers, which manually updated to version 268. There was one additional 268 update. This bug shouldn't affect the users of other versions.

The bug in the setup lies in inability to delete broken package and trying again to do the wrong diff.

The solution:
1) tested one:
Download manually:
http://www.avast.com/iavs4x/setup_av_pro-116.vpu
http://www.avast.com/iavs4x/setif_av_pro-116.vpu
put them into avast4\setup and rerun program update manually

2) untested one (looking for brave young man to test it)
Delete files setup_av_pro_10c.vpu & setif_av_pro_10c.vpu from avast4\setup directory and rerun program update manually.

We apologize for the inconvenience, the setup/update program is after serious rewrite and is still buggy (at least I hope that 278 is much, much better).

HTH,

I´ll try to post the results soon (manually updated and deleting the files).  

I can do just the following, please kubecj, correct me before the test:

1) Desinstall version 4.1.278 (which is working perfectly)
2) Install version 4.1.260
3) Update manually to version 4.1.268 (I mean install updated).
4) Delete the files you mentioned
5) Try to apply the update with vpsupd.exe

repeat the process for the second step you mentioned...

Is it useful or not?  

[techie101]

My computer still wants to restart after the update.

Is this normal?

 

[Lisandro]

My computer still wants to restart after the update.
Is this normal?

Techie, my computer asks just one restart...
After one boot, everything is ok.  

[TC17]

Hello,

this problem _very probably_ occurs to the customers, which manually updated to version 268. There was one additional 268 update. This bug shouldn't affect the users of other versions.

The bug in the setup lies in inability to delete broken package and trying again to do the wrong diff.

The solution:
1) tested one:
Download manually:
http://www.avast.com/iavs4x/setup_av_pro-116.vpu
http://www.avast.com/iavs4x/setif_av_pro-116.vpu
put them into avast4\setup and rerun program update manually

2) untested one (looking for brave young man to test it)
Delete files setup_av_pro_10c.vpu & setif_av_pro_10c.vpu from avast4\setup directory and rerun program update manually.

We apologize for the inconvenience, the setup/update program is after serious rewrite and is still buggy (at least I hope that 278 is much, much better).

HTH,

Just wanted to say I had this problem again with version 278.  I was about to install another virusscanner until I read your message.  I tried method#2, and only found one of those files in my directory (can't remember which one it was though), and deleted it.  That fixed the problem, now it updates without saying the program is broken.

[Lisandro]

That fixed the problem, now it updates without saying the program is broken.

Thanks TC17...
Kubecj, do I have to make the test yet?  

[Culpeper]

The directions worked fine on my machine.  Now updated to current version.  

[mantra]

i did a built in update....

right ? or ?
what have i to do?

[Amerk_5]

Using solution #1 I was able to update avast with the built in updater without any problems.

[techie101]

Unfortunately, updating from 268 to 278 has caused some problems.  It varies from OS to OS and in the manner of update.

My XP machine updated automatically to 278 without a hitch, but my W98 did not seem to even try to update.
I did a manual update and received the "broken packet" error.

I did NOT manually update my older version to 268 so I do not hold to the theory that the problem is caused by manually updating to 268.

I did examine the content of the Avast Setup folder and noticed as Kubey stated in his comments.....that there are 2 setup files 10c and 116.
Instead of deleting 10c, I just renamed it and tried the update again.  THIS WAS SUCCESSFUL.

I noticed that the most of the dll files were overwritten and the setup file 116 updated.

Apparently, there is a confusion to AVAST when it attempts to utilize setup10c and setup116.

I would recommend that 10c be deleted or renamed first.
This is simpler to do, and seems to be a proper fix.  I will not be able to tell if this works long term until my AVAST autoupdates.

 

[sluice]

FYI, I tried solution 2 to the broken update successfully.

[Lisandro]

Unfortunately, updating from 268 to 278 has caused some problems.  It varies from OS to OS and in the manner of update.

My XP machine updated automatically to 278 without a hitch, but my W98 did not seem to even try to update.
I did a manual update and received the "broken packet" error.

I did NOT manually update my older version to 268 so I do not hold to the theory that the problem is caused by manually updating to 268.

I did examine the content of the Avast Setup folder and noticed as Kubey stated in his comments.....that there are 2 setup files 10c and 116.
Instead of deleting 10c, I just renamed it and tried the update again.  THIS WAS SUCCESSFUL.

I noticed that the most of the dll files were overwritten and the setup file 116 updated.

Apparently, there is a confusion to AVAST when it attempts to utilize setup10c and setup116.

I would recommend that 10c be deleted or renamed first.
This is simpler to do, and seems to be a proper fix.  I will not be able to tell if this works long term until my AVAST autoupdates.

 

Thanks, Techie for your hard work and post (maybe it´ll be usefull for a lot of users, including mantra that is finding troubles under W98).
Btw, anything happens with new 4.1.280 ?  

[kubecj]

Btw, anything happens with new 4.1.280 ?  

What you mean? It's just 'empty' update for correcting the bug of 268 inability to upgrade to 278.

[techie101]

kubey...

The only thing I know I have.... IS A BIG HEADACHE  

It took me most of the morning to figure out how to fix 268 and download 278.

NOW...you want me to download and install 280!

If 280 is an EMPTY update, then do we need it if we already have 278 installed?

Love you guys. hahaha

Should we wait for the auto download, or try a manual??

 

[kubecj]

As 278 should be bug free, it should download 280 automatically or do it manually, as you like.

It's 268 what was buggy.


That 'urging' message was for the non-updating users, those with <268 or even with 4.0.