To top
Support & Downloads Support & Downloads

Frequently Asked Questions

Share:

Installation

  •  

    You can trigger a silent installation of CodeMeter using the command line parameter "/ComponentArgs "*":"/qn".

    example command line:

    CodeMeterRuntime.exe /ComponentArgs "*":"/qn"

     

    Note:

    If the CodeMeter installation is executed using the PowerShell, double quotation marks must be used for the arguments:

    e.g: CodeMeterRuntime.exe /ComponentArgs ""*""":""/qn"""

     

    Additionally calling

    CodeMeterRuntime.exe /ComponentArgs "*":"/qn /norestart"

    prevents an automatic reboot of the system. Please note that you will then need to manually reboot to complete the installation.

     

    If you use CodeMeterRuntime32|64.msi directly, you can omit the specification of ComponentArgs and specify the parameters directly. It is recommended to always write a log file, which you can specify with /L*V <log file> e.g: CodeMeterRuntime64.msi /qn /norestart /L*V CodeMeterRuntime64msi.log

     

    Further examples and help can also be found in the CodeMeter Developer Guide in the section "Deployment options | Delivery for Windows operating systems | Customization option for installation packages".

  •  

    The reason for this could be that CodeMeter Control Center is stored several times in the Autostart folder: once in the Autostart folder for all users and once for the current user. This can happen, if the CodeMeter Installer has been installed once for the current user and once for all users.

     

    On first start, CodeMeter Control Center is stored in the Windows Systray. The next time you start CodeMeter, it will be minimized and displayed.

    Therefore, the simple solution is to remove the link to CodeMeter Control Center from the Autostart folder once.

     

    For Windows 10 please proceed as follows:

    1. Press the key combination [Windows key] + [R] and type "shell:startup" into the open line.

    2. A Windows Explorer window will open with the subfolder "AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Autostart". This is the autostart folder of the currently logged in user.

    3. If you want to delete the entry, click on it with the right mouse button and select "Delete" in the context menu.

     

    For earlier Windows versions, select the Autostart folder from the Start menu and right-click '(All) user' to open it. You will then see the respective entries in the Windows Explorer window that appears. Here you can select and delete the CodeMeter Control Center entry to be deleted.

  •  

    The minimum requirement for deploying your protected software is the CodeMeter Runtime License Server.

    Wibu-Systems recommends the installation of the existing installation packages for different operating systems.

    As a software manufacturer, you are entitled to pass these complete packages on to your end customers free of charge.

    Alternatively, your customers can download the packages directly from the user area of the Wibu-Systems website (https://www.wibu.com/support/user/downloads-user-software.html) free of charge, without password and without obligation to register for the installation.

     

    The following installation packages are available for non-Windows operating systems:

    Linux

    RPM packages, e.g. SuSe, Red Hat, etc.

    - CodeMeter Runtime 64-Bit - for PC on AMD64 basis

    - AxProtector/Java Runtime - Java applications protected for AxProtector

    - CodeMeter Runtime - contains all required files for the end user.

    - CodeMeter Lite - driver installer for systems without GUI

     

    DEB packages, e.g. for Debian, Ubuntu, etc.

    - CodeMeter Runtime 64-Bit - for PC on AMD64 basis

    - AxProtector/Java Runtime - Java applications protected for AxProtector

    - CodeMeter Runtime - contains all required files for the end user.

    - CodeMeter Lite - driver installer for systems without GUI

  •  

    In the CmDust log file the entry "Run as system service: no" informs that the CodeMeter service is not registered with the operating system with administrative privileges.

    This means the CodeMeter service (CodeMeter.exe) runs not as user "SYSTEM" but only with local user privileges. This may involve problems with the communication or with reading licenses.

     

    That the CodeMeter service has only local user privileges can be seen in the CmDust log file with the following entry: "Currently running CodeMeter () started from C:\Program Files (x86)\CodeMeter\Runtime\bin\CodeMeter.exe"

     

    A solution to this problems for you customer is to re-register the CodeMeter service with the system and thus check for errors on installing the CodeMeter runtime.

    For re-register please proceed as follows:

     

    1. Open CodeMeter Command Prompt via "Start | All Programms | CodeMeter | Tools | CodeMeter Command Prompt" (alternatively click on Windows symbol and typing 'CodeMeter Command Prompt')

    2. Execute the command: "CodeMeter.exe /u" to delete registering the CodeMeter service with the system

    3. Execute the command: "CodeMeter.exe /i" to register the CodeMeter service with the system

     

    After this process has been performed using the Task Manager it can be checked whether the CodeMeter service (CodeMeter.exe) runs with user SYSTEM.

  •  

    When using the CodeMeter Merge Modules in a WiX setup, it is necessary and recommended to suppress the following ICE errors when compiling: ICE03;ICE80;ICE82;ICE30

     

    You can specify them in your Visual Studio project at "Properties | Tool Settings | Suppress specific ICE validation".

     

    Please also note that Wibu-Systems recommends the use of our EXE/MSI installers instead of the Merge Modules.

  •  

    The CodeMeter settings in the Windows registry are retained by default when uninstalling the CodeMeter Runtime under Windows.

    The reason for this is that often only a newer CodeMeter software version is to be installed and the previous CodeMeter software is uninstalled first. Here it would be annoying if all CodeMeter settings had to be reset again.

     

    To completely remove the CodeMeter registry entries and all your settings, you can call the CodeMeter installer, e.g. CodeMeterRuntime.exe, as follows:

    CodeMeterRuntime.exe /x /ComponentArgs "*": "REMOVECMREG.A961A077_4BD0_4C98_86BC_EE4A98CE550D=1"

  •  

    Starting with CodeMeter version 6.90, the system no longer automatically tries to create firewall rules for CodeMeter WebAdmin during installation. You can reactivate them by activating the component "Remote Access to WebAdmin" during installation (custom setup).

    If CodeMeter is already installed, you can also make changes to the installed components via the system control panel or by running the installer again.

  •  

    To Install the CodeMeter Runtime without the .NET Framework components, please proceed as follows:

    1. Open commandline (DOS-Box) as administrator.

    Type "cmd" in Windows search and right-click on the executable. Then select "Run as administrator".

    2. Use the command "cd" to change the directory to where the CodeMeter Runtime installer is saved to.

    3. Execute the following command:

    CodeMeterRuntime.exe /log /logfile "CmRuntime.log" /componentargs "*":"/qn /l*v ""CmRuntimeMSI.log""

    ADDLOCAL=Complete,WibuShellExtension,User_Help REMOVE=DotNET_Modules"

     

    This will install the CodeMeter Runtime without the .NET modules.

  •  

    By default, the logging file install.log is located at /var/log/.

     

    To copy the logging file to the desktop, please use the following command:

    cp /var/log/install.log ~/Desktop/install.log

     

    To make the log file easier to read, reproduce the installer error again and then copy the log file.

    It is also helpful to know the exact time when the installer was started.

  •  

    No matter, if you want to install or uninstall, the first step is to mount the CodeMeter Installer.

    You can use the following command for this:

    hdiutil attach CmRuntimeUser_...dmg

    The installer is now mounted, for example, as /dev/disk4.

     

    Subsequently, the installer can be run either for installing or uninstalling:

    Installing: sudo installer -pkg /Volumes/CM-Install/CmInstall.pkg -target /Applications

    Uninstalling: /Volumes/CM-Install/CmUninstall.app/Contents/MacOS/CmUninstall -q

     

    After successful uninstalling/installing, the installer should be unmounted again with the following command:

    hdiutil detach /dev/disk4

    Note: Here you must replace /dev/disk4 correctly with the path where the installer was initially mounted.

     

    Finally, you should inform the user that the Mac computer must be rebooted to complete the installation.

  •  

    When installing the CodeMeter Runtime v6.90a/b on 32-bit and 64-bit systems it was observed that the server search list is deleted. This happens, if a CodeMeter version lower than or equal to 6.70 was previously installed and updated to version higher than or equal to 6.70a and lower than or equal to 6.90. If CodeMeter Runtime version 6.90a/b is then installed, calling the previous CodeMeter installer for uninstalling causes the server search list to be deleted. Since the cause is the old installer, we cannot change anything here.

     

    To avoid this, we recommend to uninstall CodeMeter via "Control Panel | Programs" and then reinstall the current version instead of performing an update installation.

    If you update directly from CodeMeter Runtime version X to CodeMeter v6.90a/b and newer, the server search list will be preserved.

  •  

    You can uninstall CodeMeter using the command line command msiexec /x CodeMeterRuntime64.msi. However, the specified MSI must be installed for this.

     

    Alternatively, you can also uninstall an installed product by entering the ProductCode.

    How to determine the Product Code is described here: www.techn1k-blog.de/batchsoftwaredeinstallation/.

    IMPORTANT: Please note that these are internal Windows processes and that Wibu-Systems neither assumes support nor warranty.

  •  

    Microsoft does not recommend including merge modules from other manufacturers in your own installer:

    docs.microsoft.com/de-de/windows/win32/msi/windows-installer-best-practices

     

    As an alternative to the merge modules, you should use the CodeMeter Runtime.exe or CodeMeterRuntime[32|64].msi installer provided by Wibu-Systems for installing CodeMeter.

  •  

    The package can only be verified with the debsig tool. Verification with dpkg-sig is not possible because the two tools are not compatible.

    This process covers 5 steps:

     

    Step 1: install debsig

    Enter the following command line:

    $ (sudo) apt install debsig

     

    Step 2: create policy and keyring directories:

    Enter the following command lines:

    $ (sudo) mkdir -p /etc/debsig/policies/5FCB7AB40CC62A25

    $ (sudo) mkdir -p /usr/share/debsig/keyrings/5FCB7AB40CC62A25

     

    Step 3: create and fill policy file:

    At /etc/debsig/policies/5FCB7AB40CC62A25 create a policy.pol file (the extension must be .pol).

     

    <?xml version="1.0"?>

    <!DOCTYPE Policy SYSTEM "http://www.debian.org/debsig/1.0/policy.dtd">

    <Policy xmlns="https://www.debian.org/debsig/1.0/">

     

    <Origin Name="codemeter" id="5FCB7Ab40CC62A25" Description="CodeMeter"/>

     

    <Selection>

    <Required Type="origin" File="debsig.gpg" id="5FCB7AB40CC62A25"/>

    </Selection>

     

    <Verification MinOptional="0">

    <Required Type="origin" File="debsig.gpg" id="5FCB7AB40CC62A25"/>

    </Verification>

    </Policy>

     

    Step 4: copy the public key (not import it!)

    Enter the following command lines:

    $ gpg --dearmor wibu_pub.gpg

    $ (sudo) cp wibu_pub_dearmored.gpg /usr/share/debsig/keyrings/5FCB7AB40CC62A25/debsig.gpg

     

    Step 5: verify signature

    Enter the following command line:

    $ debsig-verify codemeter*.deb

    Expected output is:

    >> debsig: verified package from 'CodeMeter' (codemeter)

  •  

    In case of difficulties during CodeMeter installation or uninstallation, the installer logs are required for further investigation.

    These logs are located in the temp directory of the user who performed the installation.

    You can easily find them in Windows Explorer by entering %temp% in the address bar.

     

    For each installation two log files are created, which have the following structure:

    CodeMeter_v<Version of CodeMeter>_{key value}.log

    CodeMeter_v<Version of CodeMeter>_{key value}_CodeMeterRuntime64.msi

     

    Example: The CodeMeter-Msi-log of version 6.70 is:

    CodeMeter_v6.70.3152.500_{F49D7631-3323-4361-A0A3 CD9D00F154AC}_CodeMeterRuntime64.msi