NOD32 v2.7 & Vista Irritation

Hi,

I have an irritation where Windows Security Center is reporting that I don't have AV installed, even though I have NOD32 v2.7 (up to date) on the PC.

Anyone else had anything similar?

I have done a reinstall of NOD32 already.

Thanks,

James.

NOD32 antivirus system information
Virus signature database version: 2033 (20070203)
Dated: Saturday, February 03, 2007
Virus signature database build: 8981

Information on other scanner support parts
Advanced heuristics module version: 1.050 (20070203)
Advanced heuristics module build: 1142
Internet filter version: 1.002 (20040708 )
Internet filter build: 1013
Archive support module version: 1.052 (20070115)
Archive support module build version: 1179

Information about installed components
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Base
Version: 2.70.23
NOD32 For Windows NT/2000/XP/2003/Vista/x64 - Internet support
Version: 2.70.23
NOD32 for Windows NT/2000/XP/2003/Vista/x64 - Standard component
Version: 2.70.23

Operating system information
Platform: Windows Vista (TM) Business
Version: 6.0.6000
Version of common control components: 5.82.6000
RAM: 2046 MB
Processor: Intel(R) Pentium(R) D CPU 3.00GHz (2992 MHz)

 

Try this:

1. Open a Command Prompt by clicking on Start->Run, entering "CMD.EXE" as the name of the program to run, and click on the OK button. The Command Prompt window will appear.

2. In the Command Prompt window, type "NET STOP WINMGMT /Y" and press Enter.

3. Type "REN %WINDIR%\SYSTEM32\WBEM\REPOSITORY %WINDIR%\SYSTEM32\WBEM\REP.OLD" and press Enter.

4. Type "EXIT" at the Command Prompt to close the window.

5. Reboot the system. Windows should start up as it normally does, but you may be prompted to reboot the system once more in order to finish making the changes to the system caused by resetting WMI's core repository. Allow the computer to reboot if it prompts again. You may also need to reboot a second (or third) time if the Windows Security Center still does not detect NOD32.

 

Hi Marcos,

Thank-you very much. That's sorted out the problem (after the first reboot)!!

James.