Cannot Update : Broken Package Error.

Hello, im trying to update my avast, the current version is 6.0.1.1289 my engine and virus definition is 110928-0

When i try to update it just says broken package error, i have tried to look in my avast setup folder, and servers.def is as it is supposed to be, i also tried to go to avast settings, go to connection and change the proxy to direct connection only… nothing is working what can i do now

“Add/Remove Programs” → change → Repair Avast → reboot → let the automatic update work whenever it is automatically activated.

When i try to do that it just pops up with an error saying…

Avast Pro anitivurs setup
error processing packages
please use full package.

I can click OK or view Log

Download the latest version of Avast VPS http://www.avast.com/download-update and run it. Reboot after it.

Test this situation for the next database updates (at least 12 hours, up to 24).

If you still have this problem after a day of testing, you’d need to download the latest stable version of Avast again and run it over the current installation.

So im confused that thing just said everything is up to date, i still try to update on avast and it says the same error.? what am i waiting for

What “thing” say “what”?

I gave you (clear?) suggestions. If you can’t follow them for some reason, please be clear in your question and I’ll try my best to help you (or I’ll try to clarify my previous suggestions, if they weren’t such).

Well you saying im gonna test this, what u suggested me, and wait 12 - 24 hours to see if it works, well what difference did this do what u gave me? because im not quiet clear with what oyu trying to do

Did you reboot after running the full VPS install as the User Interface will still have an out of sync condition as to what VPS is reported and what you have installed.

The repair and reboot normally rectify that condition.

And that was part of my clear suggestion. If the OP cares about getting actual help, he might want to be a little more specific and clear.

Which is why I sought confirmation they had done that, as it should have resolved the out of sync issue.