Webroot AntiVirus 6.1.0.145 not being "recognized"

I'm running Win 7 Ultimate x64 with Webroot AntiVirus with Spy Sweeper 6.1.0 build 145 and for some reason it is not being "recognized".

That is, in the task bar, I have the a flag with the "red x" icon and when I open the Action Center, it says that Windows did not find any antivirus software. See the attached files for screenshots.

I do recall that when I used an earlier build of Webroot that I never had this problem, but I am not sure whether this issue is due to the the new build and/or because of a Windows update.

I know I can turn off these types of messages in the Action Center, but I that's not the solution I'm looking for. I just want Windows to recognize Webroot AntiVirus and not report that there's no antivirus software running.

Webroot support has been totally useless. All I got back from them were canned responses which did not address my problem at all.

Has anyone else experienced this? Or do you have any idea as to what the cause may be?

Let me know if you have any ideas.

Thanks!

Yes, that is the latest version.

Also, prior to installing this version, I had unistalled my previous version. But perhaps it is worth trying this again.

I will let you know the result.

Thanks.

Yep, it worked this time. Thanks for the suggestion.

But now I'm considering switching to Spyware Doctor, as I was not impressed with Webroot's totally inadequate support. First, they just sent a canned response (based on keywords I wrote in the description). Then, after I replied to them, telling them that they need to read my issue and send an appropriate response, I still had to keep pinging them to get a response!

When they did respond, they couldn't even suggest what you said or even just try to replicate my issue. Instead, they sent me the following message:

We can't be responsible for the messaging in the Windows Security Center. You have confirmed that our software is active and running, so that means Window Security is wrong, and that is a Microsoft problem. You will need to contact MS about this, especially as Windows 7 is still very new, there may be a bug they need to correct.


Pathetic!

Once again, thanks for your help!