{"id":32203,"date":"2026-10-06T14:16:51","date_gmt":"2026-10-06T14:16:51","guid":{"rendered":"https:\/\/support.buildsoft.eu\/?post_type=ht_kb&p=32203"},"modified":"2026-10-06T14:26:11","modified_gmt":"2026-10-06T14:26:11","slug":"error-codemeter-cannot-be-installed-on-your-system","status":"publish","type":"ht_kb","link":"https:\/\/support.buildsoft.eu\/fr\/knowledge-base\/error-codemeter-cannot-be-installed-on-your-system\/","title":{"rendered":"Error: Codemeter cannot be installed on your system"},"content":{"rendered":"\n

When installing Codemeter 9.10, you get the following error:<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

EN: Codemeter cannot be installed on your system. It does not support the supplimentary instruction set for AES-NI. The installation will be aborted. Please enable this supplementary instruction or use either a newer system supporting this supplementary instruction. <\/p>\n\n\n\n

Cause<\/h2>\n\n\n\n

AES-NI<\/strong> (Advanced Encryption Standard New Instructions) is a set of instructions built into the CPU that speeds up AES encryption and decryption in hardware, making it much faster and more secure than doing it in software. <\/p>\n\n\n\n


CodeMeter 9.x uses AES to protect license data, so it requires AES-NI and refuses to install without it. Almost every CPU since about 2010-2011 has it, but it can be switched off in the BIOS or be missing.<\/p>\n\n\n\n

So let’s check if the feature is disabled:<\/p>\n\n\n\n

    \n
  1. Download Coreinfo <\/a>(= tool from Microsoft).
    Remem<\/li>\n\n\n\n
  2. Unzip it.
    Remember the folder were the file is in.<\/li>\n\n\n\n
  3. Press Windows Key<\/strong>, type cmd <\/code>and hit Enter.
    This opens the command prompt.<\/li>\n\n\n\n
  4. The command you’ll have to execute will look like this: \"C:\\Users\\dorie\\Downloads\\Coreinfo\\coreinfo64.exe\" -f<\/code>
    But you need to replace C:\\Users\\dorie\\Downloads\\<\/code> with whatever location you used for the download.
    Paste the command and hit ENTER.<\/li>\n<\/ol>\n\n\n\n
    \"\"<\/a><\/figure>\n\n\n\n
      \n
    1. Search the list for AES.
      If a ( * ) is written behind it, AES-NI is enabled.
      If a ( – ) is written behind it, AES-NI is disabled. <\/li>\n<\/ol>\n\n\n\n
      \"\"<\/a><\/figure>\n\n\n\n

      <\/p>\n\n\n\n

      Solution in case of (-)<\/h2>\n\n\n\n
        \n
      1. Shut down your PC and boot into your BIOS\/UEFI menu<\/strong> (usually by spamming F2<\/strong>, F12<\/strong>, or Del<\/strong> right as it turns on).<\/li>\n\n\n\n
      2. Look for Advanced CPU Configuration<\/strong>, Security<\/strong>, or Processor Settings<\/strong>.<\/li>\n\n\n\n
      3. Locate Intel AES-NI<\/strong> (or Intel AES<\/strong>). If it is set to Auto<\/em>, explicitly change it to Enabled<\/strong>.<\/li>\n\n\n\n
      4. Save and exit, then let Windows boot up.<\/li>\n<\/ol>\n\n\n\n

        Solution in case of (*)<\/h2>\n\n\n\n

        1. Check for Antivirus\/Security Interference<\/h3>\n\n\n\n

        Some aggressive endpoint security tools or third-party antivirus software block applications from querying direct hardware instruction sets as a anti-exploit measure.<\/p>\n\n\n\n

          \n
        • If you are running third-party security software, temporarily disable its behavior monitoring<\/strong> or exploitation protection<\/strong> modules while running the CodeMeter installer.<\/li>\n\n\n\n
        • And possibly also while running Codemeter Control Center.<\/li>\n<\/ul>\n\n\n\n

          2. Clear Out Clashing System Environment Variables<\/h3>\n\n\n\n

          CodeMeter relies on standard open-source cryptographic libraries (like OpenSSL) to evaluate AES capabilities. If you have other developer tools installed that set a global OPENSSL_ia32cap<\/code> system variable, it can artificially turn off AES-NI detection for software trying to call it.<\/p>\n\n\n\n

            \n
          1. Press the Windows Key<\/strong> and type Environment Variables<\/code>, then select Edit the system environment variables<\/strong> (NL: omgevingsvariabelen van het systeem bewerken).<\/li>\n\n\n\n
          2. Click Environment Variables<\/strong> at the bottom right.<\/li>\n\n\n\n
          3. Check both the User variables<\/em> and System variables<\/em> sections for anything containing OPENSSL<\/code> or ia32cap<\/code>.<\/li>\n\n\n\n
          4. If found, back up the value, delete the variable, click OK<\/strong>, and restart your computer.<\/li>\n<\/ol>\n\n\n\n

            3. Delete prior corrupted 8.40 registry Keys<\/h3>\n\n\n\n

            The 9.10 installer will check old Wibu-Systems registry strings to evaluate prior configurations. If version 8.40 crashed constantly, it likely left behind a dirty registry configuration state.<\/p>\n\n\n\n

              \n
            1. Uninstall Codemeter.<\/li>\n\n\n\n
            2. Press Windows Key + R<\/strong>, type regedit<\/code>, and hit Enter.<\/li>\n\n\n\n
            3. Navigate to: HKEY_LOCAL_MACHINE\\SOFTWARE\\WIBU-SYSTEMS\\CodeMeter<\/code>.<\/li>\n\n\n\n
            4. Right-click the CodeMeter<\/strong> folder key and select Export<\/strong> (to save a backup just in case).<\/li>\n\n\n\n
            5. After exporting, right-click and Delete<\/strong> the CodeMeter<\/code> registry folder entirely.<\/li>\n\n\n\n
            6. Try executing the 9.10 installer again.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

              When installing Codemeter 9.10, you get the following error: EN: Codemeter cannot be installed on your system. It does not support the supplimentary instruction set for AES-NI. The installation will be aborted. Please enable this supplementary instruction or use either a newer system supporting this supplementary instruction. Cause AES-NI (Advanced…<\/p>\n","protected":false},"author":3,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":[],"ht-kb-category":[36],"ht-kb-tag":[],"_links":{"self":[{"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/ht-kb\/32203"}],"collection":[{"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/comments?post=32203"}],"version-history":[{"count":3,"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/ht-kb\/32203\/revisions"}],"predecessor-version":[{"id":32211,"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/ht-kb\/32203\/revisions\/32211"}],"wp:attachment":[{"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/media?parent=32203"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/ht-kb-category?post=32203"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/support.buildsoft.eu\/fr\/wp-json\/wp\/v2\/ht-kb-tag?post=32203"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}