Windows asks me to activate my product key – what do I have to do?

09
2014-02
  • SJDN

    I downloaded a copy of Windows 7 Home Premium to my computer. Now there are messages popping up saying "activate your product key".

    What should I do now? All my Microsoft programs title bars has turned into red, showing the above message.

    Do I have to get a genuine product key for this? and what should I do with this?

  • Answers
  • MDT Guy

    All my Microsoft programs title bars has turned into red

    Sounds like OFFICE needs to be activated, not windows

    assuming the key you used was legit, you can activate Office from the comand line.

    From the command prompt:

    cscript "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act
    

    If you don't have a key, you need to get one. You could even use the ospp.vbs script to add one once you get one.

  • Tom

    Assuming you've bought a genuine copy, you should have a key and need to activate within 30 days per the instructions here.

  • karel

    This shouldn't prevent you from using the computer. You just have to click OK on the annoying popups.

    I recommend you to get a valid product key.

    In case you bought a Windows 7 Home Premium copy from an online shop, make sure you got a product key, if you haven't seems like you should contact the store and request it.

    In case you downloaded your copy of Windows 7 Home Premium from the internet for free, you need to buy a product key from Microsoft.


  • Related Question

    Make a clone of VirtualBox Machine that doesn't cause Windows Re-Activation after installing Windows
  • palswim

    Most guides for installing Windows on VirtualBox to act as a template for quick Windows jobs tell you to take a few steps to prepare the Virtual Machine before installing Windows (the best guide I found: grahamrhay.wordpress.com; another fairly good guide: www.windowstablettv.com). Unfortunately, I didn't read these guides before installing and activating Windows on the VM I wanted to use as a template.

    I want to know how to clone my already-active VM in such a way that would not require re-activation from Windows.

    Looking in the template VM Definition file (the VBOX or XML file for the VM), the /VirtualBox/Machine/Hardware (XPath ID) node has no uuid attribute. But, if I try to use VBoxManage modifyvm <uuid|name> --hardwareuuid <uuid> to set a new UUID for the template VM, then the template VM loses its activation status! (Thankfully, I had made a backup of the template.) So, to accomplish my aim, I can't just follow those guides pretending that I haven't installed Windows yet.


  • Related Answers
  • palswim

    Thankfully, I noticed something about all of my Virtual Machines that I hadn't prepared as those guides had outlined.

    I ran VBoxManage showvminfo <uuid|name> and noticed that the UUID valued matched the Hardware UUID value, leading me to surmise that if any VM Definition didn't have a uuid attribute in the /VirtualBox/Machine/Hardware node, then the VM would use the "Machine UUID" value as the "Hardware UUID" value. So, for my template VM, it did have a "Hardware UUID" that I could use; I just had to find how to transfer it to any clones I would make.

    To ensure that the UUID transfers, you can take one of two approaches:

    • You can edit the VM Definition file directly. The "Hardware UUID" will only transfer to clones if the /VirtualBox/Machine/Hardware has the uuid attribute. So, copy the /VirtualBox/Machine uuid attribute and add it to the /VirtualBox/Machine/Hardware uuid attribute. You probably want to re-initialize the VirtualBox machine database after this, by closing/killing any VirtualBox process you're running. (VBoxSVC sometimes lingers on Windows; you may have to kill it from the Task Manager.)
    • You can clone your template and make a new template VM, and then use VBoxManage modifyvm <uuid|name> --hardwareuuid <uuid> to set the new template's "Hardware UUID" to the original template's "Machine UUID"/"Hardware UUID". I say you have to clone the VM to create a new template VM because if you try to set the "Hardware UUID" with this command on the original template, it won't add the uuid attribute to the /VirtualBox/Machine/Hardware node, since it can still imply it from the "Machine UUID", and thus won't copy this value to any clone it makes.