Avast wont instal winxp x64 pro

Avast Free Antivirus / Premium Security
1

Hi all,

Ive used avast before and just recently had to uninstall as my internet went when used with outpost firewall.

Ive just decided to reinstall to try to get them to work together and opened a ticket with augitium.

My problem is now avast wont reinstall.

Here is the last half of the setup log.

19.01.2008 14:40:28 package: Full of package winsysgui was set to 1
19.01.2008 14:40:28 package: IsFullOkay: vps-70300.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: vps-70300.vpu - not okay
19.01.2008 14:40:28 package: Full of package vps was set to 1
19.01.2008 14:40:28 package: IsFullOkay: vpsm-70301.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: vpsm-70301.vpu - not okay
19.01.2008 14:40:28 package: Full of package vpsm was set to 1
19.01.2008 14:40:28 package: IsFullOkay: news409-32.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: news409-32.vpu - not okay
19.01.2008 14:40:28 package: Full of package news409 was set to 1
19.01.2008 14:40:28 package: FilterOutExistingFiles: 144 & 0 = 144
19.01.2008 14:40:28 package: IsFullOkay: setif_av_pro-3ae.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: setif_av_pro-3ae.vpu - not okay
19.01.2008 14:40:28 package: Full of package setif_av_pro was set to 1
19.01.2008 14:40:28 package: IsFullOkay: setup_av_pro-3ae.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: setup_av_pro-3ae.vpu - not okay
19.01.2008 14:40:28 package: Full of package setup_av_pro was set to 1
19.01.2008 14:40:28 package: IsFullOkay: av_pro_core-360.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: av_pro_core-360.vpu - not okay
19.01.2008 14:40:28 package: Full of package av_pro_core was set to 1
19.01.2008 14:40:28 package: IsFullOkay: av_pro_dll409-158.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: av_pro_dll409-158.vpu - not okay
19.01.2008 14:40:28 package: Full of package av_pro_dll409 was set to 1
19.01.2008 14:40:28 package: IsFullOkay: av_pro_hlp409-28a.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: av_pro_hlp409-28a.vpu - not okay
19.01.2008 14:40:28 package: Full of package av_pro_hlp409 was set to 1
19.01.2008 14:40:28 package: IsFullOkay: av_pro_skins-13.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: av_pro_skins-13.vpu - not okay
19.01.2008 14:40:28 package: Full of package av_pro_skins was set to 1
19.01.2008 14:40:28 package: IsFullOkay: avscan-276.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: avscan-276.vpu - not okay
19.01.2008 14:40:28 package: Full of package avscan was set to 1
19.01.2008 14:40:28 package: IsFullOkay: winsys-2.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: winsys-2.vpu - not okay
19.01.2008 14:40:28 package: Full of package winsys was set to 1
19.01.2008 14:40:28 package: IsFullOkay: winsysgui-2.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: winsysgui-2.vpu - not okay
19.01.2008 14:40:28 package: Full of package winsysgui was set to 1
19.01.2008 14:40:28 package: IsFullOkay: vps-70300.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: vps-70300.vpu - not okay
19.01.2008 14:40:28 package: Full of package vps was set to 1
19.01.2008 14:40:28 package: IsFullOkay: vpsm-70301.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: vpsm-70301.vpu - not okay
19.01.2008 14:40:28 package: Full of package vpsm was set to 1
19.01.2008 14:40:28 package: IsFullOkay: news409-32.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: news409-32.vpu - not okay
19.01.2008 14:40:28 package: Full of package news409 was set to 1
19.01.2008 14:40:28 package: FilterOutExistingFiles: 144 & 0 = 144
19.01.2008 14:40:28 package: FilterOutExistingFiles: 144 & 0 = 144
19.01.2008 14:40:28 package: IsFullOkay: setif_av_pro-3ae.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: setif_av_pro-3ae.vpu - not okay
19.01.2008 14:40:28 package: Full of package setif_av_pro was set to 1
19.01.2008 14:40:28 package: IsFullOkay: setup_av_pro-3ae.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: setup_av_pro-3ae.vpu - not okay
19.01.2008 14:40:28 package: Full of package setup_av_pro was set to 1
19.01.2008 14:40:28 package: IsFullOkay: av_pro_core-360.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: av_pro_core-360.vpu - not okay
19.01.2008 14:40:28 package: Full of package av_pro_core was set to 1
19.01.2008 14:40:28 package: IsFullOkay: av_pro_dll409-158.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: av_pro_dll409-158.vpu - not okay
19.01.2008 14:40:28 package: Full of package av_pro_dll409 was set to 1
19.01.2008 14:40:28 package: IsFullOkay: av_pro_hlp409-28a.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: av_pro_hlp409-28a.vpu - not okay
19.01.2008 14:40:28 package: Full of package av_pro_hlp409 was set to 1
19.01.2008 14:40:28 package: IsFullOkay: av_pro_skins-13.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: av_pro_skins-13.vpu - not okay
19.01.2008 14:40:28 package: Full of package av_pro_skins was set to 1
19.01.2008 14:40:28 package: IsFullOkay: avscan-276.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: avscan-276.vpu - not okay
19.01.2008 14:40:28 package: Full of package avscan was set to 1
19.01.2008 14:40:28 package: IsFullOkay: winsys-2.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: winsys-2.vpu - not okay
19.01.2008 14:40:28 package: Full of package winsys was set to 1
19.01.2008 14:40:28 package: IsFullOkay: winsysgui-2.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: winsysgui-2.vpu - not okay
19.01.2008 14:40:28 package: Full of package winsysgui was set to 1
19.01.2008 14:40:28 package: IsFullOkay: vps-70300.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: vps-70300.vpu - not okay
19.01.2008 14:40:28 package: Full of package vps was set to 1
19.01.2008 14:40:28 package: IsFullOkay: vpsm-70301.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: vpsm-70301.vpu - not okay
19.01.2008 14:40:28 package: Full of package vpsm was set to 1
19.01.2008 14:40:28 package: IsFullOkay: news409-32.vpu - not okay
19.01.2008 14:40:28 package: IsFullOkay: news409-32.vpu - not okay
19.01.2008 14:40:28 package: Full of package news409 was set to 1
19.01.2008 14:40:30 general: Selected group: Instant Messaging
19.01.2008 14:40:30 general: Selected group: P2P Shield
19.01.2008 14:40:30 general: Selected group: Internet Mail
19.01.2008 14:40:30 general: Selected group: Outlook/Exchange
19.01.2008 14:40:30 general: Selected group: Network Shield
19.01.2008 14:40:30 general: Selected group: Web Shield
19.01.2008 14:40:30 general: Selected group: Standard Shield
19.01.2008 14:40:30 general: Selected group: Skins
19.01.2008 14:40:30 general: Selected group: English language extension
19.01.2008 14:40:30 general: Selected group: English help
19.01.2008 14:40:30 package: FilterOutExistingFiles: 144 & 0 = 144
19.01.2008 14:40:30 package: IsFullOkay: setif_av_pro-3ae.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: setif_av_pro-3ae.vpu - not okay
19.01.2008 14:40:30 package: Full of package setif_av_pro was set to 1
19.01.2008 14:40:30 package: IsFullOkay: setup_av_pro-3ae.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: setup_av_pro-3ae.vpu - not okay
19.01.2008 14:40:30 package: Full of package setup_av_pro was set to 1
19.01.2008 14:40:30 package: IsFullOkay: av_pro_core-360.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: av_pro_core-360.vpu - not okay
19.01.2008 14:40:30 package: Full of package av_pro_core was set to 1
19.01.2008 14:40:30 package: IsFullOkay: av_pro_dll409-158.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: av_pro_dll409-158.vpu - not okay
19.01.2008 14:40:30 package: Full of package av_pro_dll409 was set to 1
19.01.2008 14:40:30 package: IsFullOkay: av_pro_hlp409-28a.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: av_pro_hlp409-28a.vpu - not okay
19.01.2008 14:40:30 package: Full of package av_pro_hlp409 was set to 1
19.01.2008 14:40:30 package: IsFullOkay: av_pro_skins-13.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: av_pro_skins-13.vpu - not okay
19.01.2008 14:40:30 package: Full of package av_pro_skins was set to 1
19.01.2008 14:40:30 package: IsFullOkay: avscan-276.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: avscan-276.vpu - not okay
19.01.2008 14:40:30 package: Full of package avscan was set to 1
19.01.2008 14:40:30 package: IsFullOkay: winsys-2.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: winsys-2.vpu - not okay
19.01.2008 14:40:30 package: Full of package winsys was set to 1
19.01.2008 14:40:30 package: IsFullOkay: winsysgui-2.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: winsysgui-2.vpu - not okay
19.01.2008 14:40:30 package: Full of package winsysgui was set to 1
19.01.2008 14:40:30 package: IsFullOkay: vps-70300.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: vps-70300.vpu - not okay
19.01.2008 14:40:30 package: Full of package vps was set to 1
19.01.2008 14:40:30 package: IsFullOkay: vpsm-70301.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: vpsm-70301.vpu - not okay
19.01.2008 14:40:30 package: Full of package vpsm was set to 1
19.01.2008 14:40:30 package: IsFullOkay: news409-32.vpu - not okay
19.01.2008 14:40:30 package: IsFullOkay: news409-32.vpu - not okay
19.01.2008 14:40:30 package: Full of package news409 was set to 1
19.01.2008 14:40:30 package: FilterOutExistingFiles: 144 & 0 = 144
19.01.2008 14:40:31 general: progress thread start
19.01.2008 14:40:31 general: progress start - 1
19.01.2008 14:40:31 general: progress start - 2
19.01.2008 14:40:31 general: progress start - 3
19.01.2008 14:40:31 general: Under Jolly Roger! ()
19.01.2008 14:40:31 general: progress end - 2
19.01.2008 14:40:31 general: progress end - forced
19.01.2008 14:40:31 general: progress thread end

Please help, thanks.

2

OK, addition. I managed to get Avast to install after deleting registry values.
Although regedit wouldnt let me delete some legacy values, dont know why as im no expert.

Either way, after reinstaling avast my original problem still exists.

My internet is broken, only way to get it back is to uninstall one or the other.
This problem only occured since i upgraded my Outpost to 2008.
Outpost has all the exceptions still set up for avast and in some cases in the logs it says that the connection is working others are sent 0 bytes recieved 0 bytes.

Either way no internet connection is actually seen for example the web page is unavailable or i cant connect to my mail server.

If anyone at Alwil or the avast team or anyone else has any pointers i would appreciate it greatly.
Ive sent the outpost logs to Augnitum also.

Thanks.

3

You need to take ownership of the keys and delete values before deleting the folder (key).
You can use Registrar Registry Manager 5.60 (http://www.resplendence.com/registrar).

4

What if you disable the WebShield provider in avast? Does that allow you to access the Internet?

Cheers
Vlk

5

I dont know what take ownership of the keys means ???

And no, even when i disable avast components it still doesnt let anything through, i have to uninstal Avast completely.

Still waiting for a response from augnitum.

6

It’s an advanced task, for sure. Follow Vlk’s suggestions first.
Just to post a screenshot about that task.

7

Hello all again, i just want to update and finish this thread rather than leave it open ended.

Ive been in multipe emails contact with Augnitum about this problem and i knew that Avast had conflicts with Outpost firewall but the exclusions in outpost should of sorted it.

Aparrently it was something called Avast TDI which was causing the problem for me.

A quick google told me it was something to do with an Avast firewall?? Not too sure if this is correct but i never had an Avast firewall.
Can someone confirm what this is for me please?

Either way Augnitum sent me a regestry patch which disabled this Avast TDI shield and now they both work perfectly together.

After an initial issue where Avast did an update straight after i installed the patch, the problem returned.
I reinstalled the registry patch again and all has been fine for about a week now.

Just as a footnote for anyone else reading this having the same issue, i first had this problem when upgrading my Outpost firewall pro to the Outpost 2008 version.

This is the regestry key that was in the patch.
[ H K E Y _ L O C A L _ M A C H I N E \ S Y S T E M \ C u r r e n t C o n t r o l S e t \ S e r v i c e s \ a s w T d i ]

" S t a r t " = d w o r d : 0 0 0 0 0 0 0 0

Thankyou to those who responded in my OP, i wish you all well.

8

Well… there are other users with both avast and Outpost… they shouldn’t be in conflict…

It’s the avast low level driver.

avast is not a firewall… the one who said that doesn’t know avast very well.

Disabling the driver will disable the antivirus protection in some way… It’s not a patch, you’re killing your antivirus protection. When avast update it restore the correct installation and the problem… returns.

You’re disabling it… the correct should be “Start” = dword : 00000001

9

Hi,

things would be so much easier for us if we could similarly to Outpost just disable any offending driver on the clients machines. Unfortunately we are pushed to make them compatible. I truly don’t understand what is so wrong on the Outpost TDI driver (the firewall) that it doesn’t work with other TDI filters (aswTdi).

On the other hand, AswTdi.sys implements the Network Shield and this component I think can be safely uninstalled when other software is guarding your ports. Go to “add-remove programs”, select avast! Antivirus and uncheck the “Network Shield” component. This will free you from the need to re-apply this disabling patch every time avast gets updated.

Lukas