Sometimes, Windows Security Center stop recognizing your antivirus or firewall… The fix could be fairly easy for the most part.
Go to control panel and open Administrative tools.
Click on services.
Go down to Windows Managament Instrumentation.
Stop this service. Stop Security Center service too.
Let them to Automatically start.
Exit out of this area to your desktop.
Right click Start and choose Explore.
Go to c:\windows\system32\wbem\repository.
Delete this subdirectory ONLY. Let the others there.
Sometimes, only using Unlocker, MoveOnBoot or Delete FXP you can delete these files.
Exit back to your desktop and reboot your computer (maybe you need to boot twice).
This will rebuild the deleted folder and the database. Once restarted, Windows Security Center should show the correct info and antivirus and firewall should now be recoginized
I still think one should turn OFF ( "Disable" ) the entire
"Windows Security Center" based on the security flaw
in the WMI as discussed in :
www.pcmag.com/article2/0,1759,1639276,00.asp
This is the dirty old method that was used before Win XP SP2 made it simpler! It is better to rebuild the repository. Microsoft have an article about WMI that details how to do this on Win XP SP2 and Win 2K3 SP1.
I assume is what you are talking about, this UpgradeRepository for XP SP2.
If so I doubt we will have long to wait to see if it works as this appears quite frequently in the forums, thanks for the link.
[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.
I can attest that Tech’s method works since I’ve had to use it.
I also know that the scripting method is beond my skills and probably
most non expert computer users but thanks for the information.
It isn’t that complex, Start, Run, type cmd and click OK, at the command prompt type ‘rundll32 wbemupgd, UpgradeRepository’ (without the quotes) and enter, it’s done.
The confirmation I guess isn’t a must do as it either works and avast is recognised or it fails, if it fails there isn’t much you can do.
I tried it as I outlined above and it ran OK and updated the C:\WINDOWS\SYSTEM32\wbem\Logs\setup.log file.
I also tried as a Windows, Start, Run, and typed the command, no errors displayed I assume it worked, but it was very fast. Since the instructions mention ‘To do so, type the following from the command prompt’ so my guess is you have to open a cmd window to run it.
Edit: tested the windows Run command again and this time checked the setup.log file and the windows run method also works, mind you that is run against a working wbem repository.
I’ve tested last time I had a problem and it does not solve my problem.
Seems that I’m on the users that should go to MS support… which I’ve tried and receive none.
Outside of US, MS support has a lot of holes, dark holes…
If the repair fails or if your script still does not work then you will need to contact Microsoft Product Support Services.
Thank you. It only took the first step for me just now. I stopped the security service, then I waited a few seconds, then started it again. Voila! Now Security Center reads my Avast! protection.
Would this work with Vista Home Premium OS too?
I have just installed Avast! on a friends new DELL after removing McAfee (with some difficulty). Avast seems to work okay but Vista does not recognise it.
Any other possible ideas re: the security center not recognizing AVAST? I 've tried " Solution when Windows Security Center does not recognize antivirus or firewall
« on: September 10, 2006, 08:18:42 PM »
Sometimes, Windows Security Center stop recognizing your antivirus or firewall… The fix could be fairly easy for the most part.
Go to control panel and open Administrative tools.
Click on services.
Go down to Windows Managament Instrumentation.
Stop this service. Stop Security Center service too.
Let them to Automatically start.
Exit out of this area to your desktop.
Right click Start and choose Explore.
Go to c:\windows\system32\wbem\repository.
Delete this subdirectory ONLY. Let the others there.
Sometimes, only using Unlocker, MoveOnBoot or Delete FXP you can delete these files.
Exit back to your desktop and reboot your computer (maybe you need to boot twice).
This will rebuild the deleted folder and the database. Once restarted, Windows Security Center should show the correct info and antivirus and firewall should now be recoginized