To top
Support & Downloads Support & Downloads

Frequently Asked Questions

Share:

Miscellaneous

  •  

    Crash dumps must be explicitly activated in the registry starting with versions Windows 7 and later.

    You can use the attached .reg file to do this and then change the path.

     

    Please proceed as follows:

    1. Open the Windows registry editor, e.g. key combination (Win+R and enter 'regedit').

    2. Navigate to the key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDump.

    Here you can adjust the value of "DumpFolder".

     

    More information at: https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps

  •  

    Two options exist to delete a reserved Firm Code from a CmDongle, i.e. to defragment a CmDongle. One directly via CodeMeter Control Center and one via CodeMeter WebAdmin.

     

    1. CodeMeter Control Center:

    a) Open CodeMeter Control Center

    b) Open menu item "Action

    c) Select the menu item "Defragment license memory".

    The license memory of the CmDongle is defragmented.

    d) Unplug the CmDongle once for a few seconds and reconnect it.

    Now the reserved Firm Code should be deleted.

     

    2. CodeMeter WebAdmin:

    a) Open CodeMeter WebAdmin

    b) Navigate to menu item " WebAdmin | Container ".Container

    c) Click "Container Info". The container information displays.

    d) Click button "Defragment" in the "Free space" column behind the memory display.

    The license memory of the CmDongle is defragmented.

    e) Unplug the CmDongle once for a few seconds and plug it in again.

    Now the reserved Firm Code should be deleted.

  •  

    CmEmbedded libraries for VxWorks are all UP configured (Uniprocessor). If SMP (Symmetric Multiprocessing) images are to be used, the CmEmbedded source code is required and the libraries must be built specifically with SMP support.

  •  

    If the CodeMeter service on Windows 7 takes a long time to start after system startup, this may be due to the automatic detection of the system proxy.

     

    There are two ways to disable the automatic detection of the system proxy. You can find them described below:

     

    CodeMeter WebAdmin

    1. Open CodeMeter WebAdmin via the button in CodeMeter Control Center (bottom right).

    Alternatively open directly in the browser via localhost/configuration/proxy.html.

    2. Navigate to the proxy settings: Configuration | Basic | Proxy.

    3. Select an option other than "Use proxy system settings".

    4. Confirm with the "Apply" button.

     

    Windows Registry

    1. Press Win+R

    2. Type regedit

    3. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CodeMeter\Server\CurrentVersion

    4. Set the parameter: UseSystemProxy = 0

     

    Now the CodeMeter service should start normal after the system start.

  •  

    To create a complete memory dump, please proceed as follows:

    - Open the Windows Start menu.

    - Enter "Advanced system settings".

    - In "Startup and Recovery" click on the "Settings" button.

    - In "Writing debugging information" select the "Complete memory dump" setting.

    - Open Windows Task Manager and navigate to the Processes tab.

    - Select "CodeMeter Runtime Server (32 Bit)".

    - Right mouse click on the selection, the context menu opens.

    - Select "Create Image".

    An image is created and then displayed in the info box where the file was stored.

  •  

    Since CmEmbedded 2.40 the SPI Linux implementation is disabled by default and must be enabled using the environment variable SPI_ENABLE:

    export SPI_ENABLE=1

  •  

    This error occurred because the CodeMeter context file contains a Box Time greater than 2099-12-31 23:59:59 UTC.

     

    To resolve the error, the Box Time, and therefore the current time, must be updated. This is possible on the client side via CodeMeter WebAdmin.

     

    Please navigate in CodeMeter WebAdmin to "Container | CmContainer Infos" and click the icon next to the field 'Certified Time (CmContainer)' to get a certified current time.

  •  

    If you do not need the CodeMeter .NET components for executing .NET assemblies, you are able to install CodeMeter from a command line without installing the .NET components. Please proceed as follows:

     

    1. Press Win+R and type "cmd" to open a command prompt.

    2. Navigate to the directory containing the installer, using the ‘cd' command.

    Example: cd C:\Downloads\wibu

    3. Enter the following command:

    CodeMeterRuntime.exe /log /logfile "CmRuntime.log" /componentargs "*":"/qn /l*v ""CmRuntimeMSI.log"" ADDLOCAL=Complete,WibuShellExtension,User_Help REMOVE=DotNET_Modules"

  •  

    We regret to inform you that CodeMeter Password Manager has been discontinued. The high maintenance effort due to changes in the browsers and also new mechanisms in the operating systems has led us to this decision.

     

    In the appendix you find a version of Password Manager, with which you can export the passwords into a readable csv file.

    Simply copy the *.exe into your CmPasswordManager directory, the program will then search for the passwords on the CmStick and export them to a csv file. Then you can manage the passwords with another program.

     

    If you have any questions, please do not hesitate to contact us.

  •  

    The following minimum versions are required for CmEmbedded for Linux:

     - Linux ≥ 2.4.10

     - glibc ≥ 2.4

  •  

    Since CmBoxPgm ignores Firm Security Boxes by default, the FSB must be explicitly specified.

    This can be done either by the serial number, e.g. CmBoxPgm /qs3-4377687 /f6000010 /p1004 /phd0,820:0x123456 /ca.

    Or via the index in the list of recognized CmContainers, e.g. CmBoxPgm /qb1 /f6000010 /p1004 /phd0,820:0x123456 /ca.

  •  

    Starting with macOS 10.13 (High Sierra) Apple introduces the feature "Secure Kernel Extension Loading" restricting the use of third-party kernel extensions as described in Technical Note TN2459: developer.apple.com/library/content/technotes/tn2459/_index.html.

     

    This new feature may eventually require some action by the CodeMeter user.

     

    In general, the following holds:

     

    - All CmDongle devices support USB class compliant standard MSD=Mass Storage Device.

    - Newer generations of CmDongle additionally support HID=Human Interface Device.

    CmDongle supporting HID require a Minimum CodeMeter Runtime version of 5.0 and must meet at least one of the following specifications::

    * Item 1001-02-xxx (serial “2-xxxxxx” with Minimum Firmware 2.02)

    * Item 1001-03-xxx (serial “3-xxxxxx” without additional flash memory)

    * Item 1011-03-xxx (serial “3-xxxxxx” with additional flash memory and Minimum CodeMeter Runtime version of 5.20)

    - If your CmDongle supports HID, you are able to switch the USB communication standard from MSD to

    HID using the following command of CodeMeter Universal Support Tool (cmu):

    - call cmu.

    For macOS this command is provided by the usual search path parameter.

    - Enter the following commandline:

    cmu /s [Box mask-Serial number] --set-config-disk HidCommunication

     

    USB class compliant standards and Kernel extension

    HID=Human Interface Device

    Communication via HID does not need a third-party kernel extension and can be used also on macOS 10.13 without any need of interaction.

    MSD=Mass Storage Device

    Communication via MSD requires the CodeMeter Kernel Extension.

    This covers two different scenarios:

    I. CodeMeter with Kernel Extension already installed on macOS 10.12.

    The operating system is now upgraded to macOS 10.13. CodeMeter Kernel Extension is loaded

    requires no interaction and everything should work as expected.

    II. CodeMeter is installed for the first time after either via new system installation of or via an upgrade to macOS 10.13

    After successful installation or eventual reboot you will receive the notification "System Extension Blocked". Then proceed as follows:

    1. Click OK.

    2. Click the System Preferences icon in the Dock ※ or navigate to the Apple menu ※ and select System Preferences.

    3. Click Security & Privacy.

    4. Click the Lock icon in the bottom left to allow changes.

    This approval interface is only present in the Security & Privacy preferences pane for 30 minutes after

    it was tried to load the Kernel extension, i.e., in any case, the interface displays for

    30 minutes after a system restart.

    5. Click Allow next to System software from developer "WIBU-SYSTEMS AG" was blocked from loading.

    6. Restart the computer.

  •  

    In order to use the CodeMeter API in a 64-bit based Delphi application, please follow the following steps:

    1. Copy the CodeMeter.pas from C:\Program Files (x86)\CodeMeter\DevKit\include next to your 64-bit project

    2. Include the CodeMeter.pas in your project and open the CodeMeter.pas

    3. Edit line 64 and change the constant "LIB" from WibuCm32.dll to WibuCm64.dll

     

    You are now able to use all the CodeMeter API functions in your 64-bit application. Please note that the Programming API HipApi is not available for 64-bit applications.

  •  

    Differentiation of the vulnerabilities CVE-2018-3989/3990/3991

     

    Wibu-Systems offers two different licensing systems, which can be used as a basis for software protection. These are WibuKey, which has been on the market since 1989, and CodeMeter, which has been available since 2003.

    The security vulnerabilities reported and fixed as CVE-2018-3989, CVE-2018-3990, and CVE-2018-3991 relate exclusively to the product WibuKey.

    We have also conducted an intensive check of CodeMeter Runtime in response to this situation but identified no vulnerabilities. The reported vulnerabilities do NOT affect CodeMeter technology.