Security issues

[David0944]

I have a concern about the security area of Vista. I had McAfee Command
Centre ready installedon my PC when it was delivered. Because I didn't want
it, I uninstalled it. It left some files which I removed with the removal
tool provided by McAfee. I run my own antivrus tool, aVast which I think is
great.

Anyway, I turned on Windows firewall and I got a message saying that there
was a conflict. For some reason Windows seems to think that McAfee is still
running both as a firewall and for anvirus.

This is crazy, because McAfee is no longer on my computer. I can't find
anyway to remove these references form Windows Vista Security area.

Can anyone please help.

 

[Malke]

I have a concern about the security area of Vista. I had McAfee Command
Centre ready installedon my PC when it was delivered. Because I didn't
want it, I uninstalled it. It left some files which I removed with the
removal tool provided by McAfee. I run my own antivrus tool, aVast which I
think is great.

Anyway, I turned on Windows firewall and I got a message saying that there
was a conflict. For some reason Windows seems to think that McAfee is
still running both as a firewall and for anvirus.

This is crazy, because McAfee is no longer on my computer. I can't find
anyway to remove these references form Windows Vista Security area.

Right-click Command Prompt and Run as Administrator. Type the following
command:

winmgmt /verifyrepository

If the system returns "WMI repository is not consistent", run this command:

winmgmt /salvagerepository

The first time you run this it will fail. It will issue stop commands to
the services causing it to fail. It might take a couple minutes for the
services to shut down. Run the command again. You actually may have to
run it 3 times before it finally runs and completes on its own. Reboot your
system.

Note: I believe that one of the brilliant posters here (and I'm sorry but I
don't remember who it was right now) said that you don't need to do the
"verifyrepository" command, just the "salvagerepository" bit because if
nothing is marked as wrong, nothing will be done. So that may save a step.
FWIW, the only thing that has worked for me on clients' machines is the
technique below.

If the above doesn't work or you get "WMI repository is consistent", do the
following from an elevated cmd prompt:

net stop winmgmt [enter]
cd /d %windir%\system32\wbem [enter]
ren repository repository.old [enter]
net start winmgmt [enter]

Malke