The Package Is Broken

It was working the last time I booted and now it tells me “The package is broken”
Here is the log…

LoadProductVpu: C:\Program Files\Alwil Software\Avast4\Setup\prod-av_pro.vpu
12.02.2010 01:11:46 package: ERROR: Unable to verify prod-av_pro.vpu, error 0x2000000B
12.02.2010 01:11:46 package: LoadAllDefs failed 0x20000011
12.02.2010 01:11:46 general: Err:The package is broken.

What’s wrong with this puppy?
TIA for any help.
Bob Helms

Try a repair of avast. Add Remove programs, select ‘avast! Anti-Virus,’ click the Change/Remove button and scroll down to Repair, click next and follow.

OK I give up. I booted this morning and Avast is performing updates like nothing ever happened! I haven’t changed a thing. I sent a ticket into support last night but have not heard anything back from them at this point. Can anyone comment on this very odd behavior? I’m running 4.8 Home version. Thanks.
Bob Helms

Computers and software often have glitches that are resolved by a reboot.

Personally if I were you I would be getting the latest version of avast 5.0.418 unless you have win9.x or winME as they can’t run it.

Hi DavidR,
You are right, glitches do occur, unless you’re running Apple (LOL). If I’d paid for Avast then I might have a reason to be upset but instead I’m going to take your advice and try the 5.0 Pro upgrade route. I think one should pay for any services and benefits they have received and Avast has done well for me so far. After reading several post on this forum there seems to be more that one opinion / way on how to upgrade from Home 4.8 to Pro 5.0. What is your opinion on the best way to upgrade? Do I need to worry about Windows uninstaller leaving something behind? Do the guys at Alwil have an installation package that works well? If you can’t address all my questions can you point me to somewhere / someplace / someone who can? I’m running W7 Pro 64-bit. Thanks for the advice and your reply.
Bob Helms

The problem is that this is a support forum and generally you will only see those with a problem. Whilst the update to avast 5.0, the upgrade from avast Home/free to the pro version is another issue again.

It is possible to install avast 5.0 over 4.8 (some experienced problems, mainly XP users and with early 5.0 versions) as it retains the registration information from avast 4.8 for use with 5.0. It clears avast 4.8 and installs 5.0, for me (even as an XP Pro user) this was a painless issue and my registration was carried over without problem. So that is going from 4.8 home to 5.0 free.

If you wanted to go straight to the pro version you could download the pro trial version (30 days use), since no registration data is relevant from 4.8 home, it would probably be best to do a clean install of 5.0 Pro trial (uninstall 4.8, reboot, install 5.0). I would certainly use the 30 days trial version and once installed and you are happy with what you have, purchase the Pro license on-line at avast. You would receive an email with the attached license file, which you can have the avast user interface (UI) detect. How to register avast 5 pro on page 7 - 8
http://www.avast.com/documentation/quick-start-guide-pro-en-ww.pdf also see http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=459.

Well the 5.0.418 download and install completed without incident and was very fast. However the un-install of 4.8 left the shortcut on the desk top and all it’s empty program file folders behind. I wonder what it left in the registry? The 5 UI is IMHO very easy to use and much nicer that the ‘car radio’ used by 4.8. I’ll post an update before the end of my trial period. This was a refreshing experience after too many battles with Norton. Thanks for all your advice / help DavidR.
Bob Helms

You’re welcome.

No such problems with my installation, everything cleaned out.

You could run the avast! Uninstall Utility, find it here get the version5 one, aswClear5.exe and save it to your HDD (that has options to uninstall other versions).

  • run the avast! Uninstall Utility for 4.8 from safe mode- once complete reboot into normal mode.