I am using Vista Business, and have for quite some time. About a month ago, I installed avast and had some minor issues. I then found out that Kaspersky had a Vista Compliant Version, so I bought that and am using it now. But, I still have traces of avast! laying around…including the Vista Security Center. So, I found the aswclear.exe and that removed the Program Files folder, but I still see it in the Vista Security Center as showing that avast! antivirus 4.7.942 [VPS 000705-0] and is reporting a conflict because I have Kaspersky installed as well.
Anyway I can get EVERYTHING avast removed from my system, including the Vista Security Center? I still love avast, and recommend it to everyone for a Free Solution…but I needed Security NOW, and Kaspersky had it and I’ve grown to love it for personal use…but not free But, I still use avast! on other machines, and recommend it to all friends. Please help me out removing it on this one machine though!
This sounds like the issues with the XP Windows Security Center have been carried over to Vista.
There were many posts in the forums about avast not being detected by WSC and others were previous software, firewall and AV was still detected by WSC, despite having been removed as you have.
This is an issue with WSC or now VSC’s WBEM not refreshing its database.
Also check this if it might work with Vista, it too is XP SP2 related. http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx#EQKAC
Windows XP SP2, Start, Run, type cmd and click OK from the command prompt type ‘rundll32 wbemupgd, RepairWMISetup’ without the quotes and enter.
[b]Microsoft Windows XP, Service Pack 2[/b]
If you are running Windows XP, Service Pack 2 you can use a single command to detect and repair a corrupted WMI Repository. To do so, type the following from the command prompt (note that the parameter UpgradeRepository is case-sensitive and must be typed exactly as shown):
rundll32 wbemupgd, UpgradeRepository
After running UpgradeRepository you can verify the results by looking ay the Setup log. If inconsistencies are detected and if the operating system was able to rebuild the Repository you should see information in Setup.log similar to this:
(Wed Oct 12 13:46:36 2005): ===========================================================================
(Wed Oct 12 13:46:36 2005): Beginning WBEM Service Pack Installation
(Wed Oct 12 13:46:36 2005): Current build of wbemupgd.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:36 2005): Current build of wbemcore.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
(Wed Oct 12 13:46:52 2005): Inconsistent repository detected; it will be recreated
…
…
(Wed Oct 12 13:47:33 2005): Wbemupgd.dll Service Security upgrade succeeded (XP SP update).
(Wed Oct 12 13:47:33 2005): WBEM Service Pack Installation completed.
(Wed Oct 12 13:47:33 2005): ===========================================================================
Note. There will probably be other entries in the log as well, but you should specifically look for the ones shown above.