Actually that should fix itself without having to reinstall anything
Here is how it works. The AV writes itself to the WMI, which is what the security center pulls from to show the status. When my Repair WMI runs, and if the WMI is working, it will export the AV info out of WMI and then import it back in.
I did that because of what is happening here, the security center complains and it can freak a user out. But what happens is after a reboot or two or when the AV updates itself it writes itself back to the WMI anyways, it has to every time it does anything so it can report its status tot he security center.
So in your case I am curious to what status the AV is reporting to cause that. I have attached a screen shot and a zip file with a vbs script in it.
The vbs is script is a script that will read the AV info from the WMI. It will also show the current product state. I attached a screen shot of what it pulls up on my system.
The product state is suppose to be a number. Like these examples
266240 -> 0x041000:
ANTIVIRUS + active + dat_files_up_todate
266256 -> 0x041010:
ANTIVIRUS + active + dat_files_NOT_up_todate
397312 -> 0x061000:
ANTIVIRUS + AUTOUPDATE + active + dat_files_up_todate
397584 -> 0x061110 (Windows Defender started on Win7):
ANTIVIRUS + AUTOUPDATE + ???? + dat_files_NOT_up_todate
393488 -> 0x060110 (Windows Defender stopped on Win7):
ANTIVIRUS + AUTOUPDATE + ???? + dat_files_NOT_up_todate
So I want to see what yours is reporting. My repair tool takes that info and puts it into a mof file so WMI can import it back in.
Shane