Article ID: 9295, created on Nov 12, 2010, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Windows


Either an existing container or all new containers are reported as "Not Genuine" by Windows. Background is black and you can see message "This copy of Windows is not genuine" in the right-bottom corner of a desktop:

This copy of Windows is not genuine


Microsoft Windows stores it's license data in the following file:


inside of containers it should be absolutely the same as on the Hardware Node itself. If this file gets changed on a hardware node - newly created containers will be created based on an old cache of the OS template, thus file will not be in sync with the node, and containers will report themselves as "not genuine". If file is getting changed inside of a container - that will cause same effect for a single container.


The issue might be fixed for particular containers as well as for the OS template:

How to fix Activation for a template

Solution is to copy tokens.dat file from the Hardware Node inside of a template (will fix only future created containers, it won't fix existing containers). It can be achieved by following these steps:

  1. Find where templates are located on your server by executing following command:

    C:\>vzcfgt gettemplatespath
  2. In the path returned from the previous step's command find your OS template folder:

    C:\>dir C:\vz\Templates /B /A:D

    In example above we found directory windows_2008R2_dc_sp1-6.1.7601-20110211. Inside of it's subfolder private you will find root.efd - this image is used for deplyment of new containers.

  3. Mount the template's *root.efd:

    C:\>mkdir mount_point
    C:\>vzdskctl mount_shared C:\vz\Templates\windows_2008R2_dc_sp1-6.1.7601-20110211\private\root.efd
    GUID = {84b4c837-8aa2-4a35-a142-dc0e6fde1f86}
    C:\>vzdskctl set_mp C:\mount_point {84b4c837-8aa2-4a35-a142-dc0e6fde1f86}

    NOTE: C:\mount_point directory should be created on the same drive, where the OS template resides.

  4. Replace tokens.dat inside of the OS template with one copied from the node:

    C:\>copy /Y C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat C:\mount_point\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat
        1 file(s) copied.
  5. Remove the mount point and unmount template's root.efd:

    C:\>vzdskctl delete_mp C:\mount_point
    C:\>vzdskctl umount {84b4c837-8aa2-4a35-a142-dc0e6fde1f86}

How to fix Activation for an existing container

  1. Ensure the container is stopped:

    C:\>vzlist 100
        100     --  stopped  --       activation.issue
  2. Mount the container:

    C:\>vzctl mount 100
    Container is mounted
  3. Copy tokens.dat file from the node into the container:

    C:\>copy /Y C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat C:\vz\private\100\root\\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\tokens.dat
        1 file(s) copied.

    NOTE: replace C:\vz\private\100\ with the path to your container's private area. You can retrieve full path to this folder by executing following command:

    C:\>vzcfgt getctprivate 100
  4. Unmount container:

    C:\>vzctl umount 100
    Container is unmounted

Search Words

windows license

Windows のライセンス認証

Windows VPS - Activation Issue


d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF