Security Center weird behaviour

[Moody Marco]

Suddenly today Security Center on my Vista PC has started acting funny - it
says "No antivirus software found" despite NOD32 being installed and
up-to-date. It also says Windows Defender is turned off, but when I click
Turn On, it says "checking for new definitions", then says "Definitions
already up to date", but it remains saying "Turned off".

If I open Windows Defender manually, it reports back as everything being ok.

The PC was working fine when I logged on this morning, I left it on, came in
at lunch time, and it's acting like this.

Tried restarting, no luck.

 

[munchie]

Suddenly today Security Center on my Vista PC has started acting funny - it
says "No antivirus software found" despite NOD32 being installed and
up-to-date. It also says Windows Defender is turned off, but when I click
Turn On, it says "checking for new definitions", then says "Definitions
already up to date", but it remains saying "Turned off".

If I open Windows Defender manually, it reports back as everything being ok.

The PC was working fine when I logged on this morning, I left it on, came in
at lunch time, and it's acting like this.

Tried restarting, no luck.

Found this on techcenter. It should rebuild the repository, reseting
Security Center. Seems like it's worth a try:

-------------------------------------

From the command line, type:

Net stop winmgmt /y
Rename %windir%\system32\wbem\repository %windir%\system32\wbem
\repository.old

 

[Moody Marco]

Found this on techcenter. It should rebuild the repository, reseting
Security Center. Seems like it's worth a try:

-------------------------------------

Net stop winmgmt /y
Rename %windir%\system32\wbem\repository %windir%\system32\wbem
\repository.old

Presuming the above should be entered as 2 separate commands (line one, then
lines 2 and three), I get "The syntax of the command is incorrect" at the
2nd step

 

[Moody Marco]

Presuming the above should be entered as 2 separate commands (line one,
then lines 2 and three), I get "The syntax of the command is incorrect" at
the 2nd step

Ok, I did the 2nd bit the point & click way thru Explorer, restarted, all is
well now, thanks

 

[Dave T.]

Presuming the above should be entered as 2 separate commands (line one,
then lines 2 and three), I get "The syntax of the command is incorrect"
at the 2nd step

I believe the second line starts as "Ren" instead of "Rename".

 

[Nick Simpson]

I believe the second line starts as "Ren" instead of "Rename".

Actually, there are only 2 lines... the second one has wrapped. As for ren
vs rename.. they are one in the same. You may use either.

Nick

 

[Dave T.]

Nick Simpson wrote:

Actually, there are only 2 lines... the second one has wrapped. As for
ren vs rename.. they are one in the same. You may use either.

Nick

It's true then! An old dog can learn new stuff! d Thanks.

 

[Guest]

Hello, just want to say that I received similar warning about antivirus being
off, but before attempting the command prompts herebefore mentioned I created
a restore point just in case the security center got worse. For some reason
mine did, after following technet's instructions for command prompt syntax,
in that now my security center was warning not just virus protection turned
off but also firewall!!! which it was not. You have to be careful sometimes
with command prompts, for obvious reasons. System restore worked fine and
security center shows fully protected. My thinking is that in order to
perform system restore I turned off "protect my product" for my security
suite and "auto-protect" so that when system restored I had to turn
auto-protect etc. back on, forcing the security center to acknowledge my
virus program. Just giving this by way of background to anyone else out
there who is reading this and considering running the command prompt option.
My security system came pre-installed with Norton Internet Security 2007 and
it's still on, which I for obvious reasons in this forum am embarrased to
admit since haven't "taken it off" which seems to be the immediate answer
here in this forum, and probably with much reason. In any event, just
clarifying that in certain circumstances running this command may screw
things abit up abit more, so hopefully anyone in a similar situation to mine
may want to create a restore point. I'm glad for all the above answers and
to see that this problem seemed to have surface all of the sudden for many
yesterday and that there are ways of dealing with it. Thank you.