Update: March 27, 2014
GeekSquad says that the credit card charge does not happen until thte due date, and therefore the repeated appearance of the Webroot renewal notification icon is normal. This seems a bit sloppy.
GeekSqaud used a java applet to look at the signon problems. You sign on to GeekSquad, they give you a six-digit temporary pin, which lets them push an applet. Windows will ask for permission for it to run. You need java on your machine, but I do seem to have it as part of W8. I suppose I can see how java could make a machine more vulnerable to hackers, who could mass attack by generating pins. I'm not sure what the safest strategy to deal with this idea would be right now. We'd have to look at what the Webroot Threat Blog has written about java recently.
They weren't able to resolve the logon issue, so I'll have to call Webroot directly soon. It seems to have to do with the way it was originally set up at Bestbuy and the fact there is more than one machine. That is uspposed to work.
The Webroot Secure Anywhere does run; it's just that I can't get on to my account on their webserver. because of this deadly embrace.
Update: April 4, 2014
As I logged on this morning, Webroot would not start until I updated again. But then the Best Buy Script told me my credit card wouldn't be charged until 2015! My American Express still doesn't show the charge due today, but maybe it is too early in the day. I can activate it when I boot up with doing the card transaction over again. Obviously, if they don't catch this and fix it today, I will have to call again. This seems to be a problem on Best Buy's servers. It seems that Webroot is going through Best Buy to guarantee that the fee is paid, which is another possible point of apllication failure.
I talked to Geek Squad a couple times. One representative said that my machine should have been up and connected when the charge was applied. I'm not sure this makes sense, because you need a java applet to connect to the machine, or do you?
But this morning, Microsoft suddenly informed me that I needed to do an urgent update to Windows 8 with KB2922229. I did the restart, and this time Webroot started normally without the warning. But it may have been a startup problem.
here. The vulnerability seems urgent.