To top
Support & Downloads Support & Downloads

Frequently Asked Questions

Share:

Installation and Uninstallation

  •  

    InstallShield Professional returns an error, if the CodeMeter Runtime Merge Module x86 is added and a 32 bit setup is to be created.

    Background is that the 'CodeMeter.exe' is available as 32 bit only but the 'WibuCm.dll' is available as 32 bit and 64 bit partly using the same keys.

    All keys used are saved in the registry as HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CodeMeter. This for 32 bit and 64 bit operating systems.

     

    Apparently, in Install Shield Professional this leads to the fact that the CodeMeter Merge Module x86 is nevertheless recognized as 64 bit component and a 32 bit setup is refused. Install Shield returns error "-5008".

     

    So far, we do not know of any option, to deactivate this check performed by InstallShield or to successfully finalize the installation.

     

    Wibu-Systems recommends to forgo the Merge Module and instead to install 'CodeMeterRuntime.exe' or 'CodeMeterRuntime.msi'.

    Installing CodeMeterRuntime.exe|.msi can be performed in the InstallShield project, for example, using a "Custom Action" or a "Prerequisite".

     

    Other installer (Visual Studio, Wix) seem to skip such a check, allowing the use of CodeMeter Merge Module.

    In some cases, however, an ICE error occurs which on compile can be repressed.

  •  

    CodeMeter WebAdmin exists since CodeMeter v6.60 as an independent 32-bit and 64-bit Windows service (CmWebAdmin). On a 64-bit system, the 32-bit variant is not installed, only the 64-bit variant is installed here.

     

    To install the 64-bit version of CodeMeter WebAdmin, the CmRuntimeMerger64.msm module containing the 64-bit CmWebAdmin.exe must be included as well.

    Using CmRuntimeMerger.msm installs CmWebAdmin.exe only on 32-bit systems.

    If you want to have CodeMeter WebAdmin on a 64-bit system you have to use the modules CmRuntimeMerger.msm and CmRuntimeMerger64.msm.

     

    Note:

    As an alternative to using the merge modules, we recommend to use the CodeMeterRuntime.exe or the CodeMeterRuntime[32|64].msi installer package.

  •  

    On installing/uninstalling it may happen that the user is prompted to specify a MSI file.

     

    A MSI file (Microsoft Installation) holds a setup package and is commonly saved and provided in "C:\Windows\Installer". The directory "C:\Windows\Installer“ holds all software package installed via MSI. If via MSI a software is to be uninstalled, the respective MSI package is sought for in this directory and the uninstalling or updating process is performed.

     

    A Windows Microsoft compliant behavior of installation packages may be impaired, if on the respective computer a "cleaning tool" has been used which tweaks the directory to save space on the computer. However, this may interfere with installing/uninstalling routines.

     

    To remedy this error and to install/uninstall CodeMeter, the customer must use the exact same version of the MSI installer for the CodeMeter Runtime Software as used for the previous installation.

  •  

    For a manual installation, the following files must be copied to the target system:

    C:\Windows\System32\WibuCm*.*

    C:\Windows\SysWOW64\WibuCm*.*

    C:\Program Files (x86)\CodeMeter\Runtime\*.*

    C:\Program Files\CodeMeter\Runtime\*.*

     

    For Java application are additionally required:

    C:\Windows\System32\wibucmJNI64.dll

    C:\Windows\System32\WibuXpm4J64.dll

    C:\Windows\SysWOW64\wibucmJNI.dll

    C:\Windows\SysWOW64\WibuXpm4J32.dll

     

    Afterwards it is recommended to install CodeMeter as a service. For this you have to call the CodeMeter.exe accordingly:

    CodeMeter.exe /i

     

    Furthermore, it is recommended to register CodeMeter WebAdmin as a service. This must be done via the Windows services administration. Here you should also set a corresponding dependency on the CodeMeter service.

     

    Please note:

     - If CodeMeter does not run as a system service, it is not possible to use CmActLicenses.

     - With a manual installation there is no adapted behavior for *.WibuCmRaU Update Files (adapted context menu with right click, automatic import with double click, etc.).

     - In the case of a manual installation, no entries are created in the start menu.

     - If CodeMeter should not be started with administrator rights during manual installation, the CodeMeter.exe.manifest file must not be copied.

  •  

    You can uninstall CodeMeter from your computer at any time. For the various operating systems, please proceed as follows:

     

    Windows

    - Select the "Software" option in the Windows System control panel menu item.

    Note: If CodeMeter has been installed together with another software, CodeMeter is not displayed in "Control Panel | Software". In this case, you must uninstall all other software applications which have CodeMeter installed.

    - Select the "CodeMeter Runtime Kit" item and the "Remove" option.Please note that the files of the CodeMeter Runtime Kit are removed only after the final application that has installed or is using CodeMeter is also uninstalled.

     

    macOS

    - Re-open the CmRuntimeUser.dmg disk image.

    If, in the meantime you should have deleted the disk image file, advance to the Support&Downloads section of the Wibu-Systems website, and download the CodeMeter User Runtime file.

    - Advance to the directory CmRunTime and start the program CmUninstall.mpkg. Follow the instructions of the wizard.

    Alternatively, enter the following command in the commandline:

    $ sudo installer -pkg /Volumes/CmRuntimeUser/CmUninstall.mpkg -target

    Please note that path specification may vary.

     

    Linux

    Execute the shell command for uninstalling the CodeMeter Runtime Kit:

    - for RPM based distributions, such as, Suse/RedHat/Fedora [rpm -e CodeMeter]

    - for DEB based distributions, such as, Debian/Ubuntu [dpkg -r CodeMeter]