Widget Reports "key Is Invalid"

Since starting my laptop (XP Media Edition) today, the Widget says that I have an invalid key. The program itself says everything is alright and current with 400+ days left on my license which is correct.


Anybody have any ideas?

Comments

  • That's odd. It could be an invalid key from another software. Can you post a screen shot about this? I'm looking for hints if it's from BD. smile2.png

  • That's odd. It could be an invalid key from another software. Can you post a screen shot about this? I'm looking for hints if it's from BD. smile2.png


    Same problem here after upgrading to Bit Defender Internet Security 2013 on Windows XP

  • columbo
    edited August 2013

    Hi whitst, and welcome :)


    As long as your days show correct at the bottom of your BD main UI console, and your Upper Toolbar shows green you're probably fine. Just try restarting your PC a couple of times, or wait a couple of days and see if it resolves itself (sometimes, these things work themselves out). Otherwise, in a few days and restarts and updates, you could try to run a repair and see if that helps: http://forum.bitdefender.com/index.php?showtopic=35489


    Keep us posted,


    Scott

  • I hadn't started my laptop in a while (only use it on rare occasions). The problem is still occurring! The widget is just a black circle and across the circle is the wording "Your key is invalid Renew Now."


    The widget will light up and show normally if there is an update or a notification.


    It seems that a Repair doesn't work. I have to do a complete uninstall w/clean uninstall and then reinstall BD. This only lasts for a while, usually until there is a weekly update, then back to the "key is invalid" widget.


    The program reports that my license is valid and everything else seems to be fine.


    Hope to get some help here from a BD employee.

  • Installed BD 2014 today on the laptop. All went well but the Widget problem still exists. Would have thought the upgrade would cure the problem <img class=" />


    This must be due to a bad registry value.


    Hope the tech team can help!