If uninstalling CodeMeter is not possible, you should download and run the "Install and Uninstall troubleshooter". See: https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from- more
With CodeMeter version 7.10a Wibu-Systems has introduced signing of Linux installers. However, in order for the verification to be performed, the Wibu-Systems key must be imported as trusted. This key more
Especially for Linux systems without graphical user interface, it is necessary to configure CodeMeter runtime settings directly in the Server.ini file of CodeMeter. To make corresponding changes in th more
Information about the system requirements for CodeMeter Runtime Kit can be found in the "CodeMeter Runtime Data Sheet". This can be downloaded at https://www.wibu.com/support/data-sheets.html from our more
You are able to import the file using the "cmu" commandline tool. Copy the file to the system and import the file using the following command: cmu -i -f , for example, cmu -i -f CmFirm.wbc. The tool i more
There exist different options to lock licenses. Locking a CmContainer via blacklist maintained by Wibu-Systems This type locks the complete CmContainer (and not only your Firm Code). This requires tha more
The error occurs because you are still missing the invoicing entry for your Universal Firm Code. You will receive this when you purchase your Firm Code and must activate it online. You will find a tic more
To create a Context File (*.WibumRaC), proceed as follows: With graphical user interface: 1. Open CodeMeter Control Center. 2. Select on the left side the license from which you want to create the Con more
To use a WibuBox or a CmDongle on a system as a network server or via the network, a "standard" operating system (Windows, Linux, macOs or similar) is required. However, since NAS devices usually use more
There exist different Firm Codes for different CmContainer types. 1. 1xx.xxx = CmDongle Firm Code, only importable into CmDongles (Hardware) 2. 5.xxx.xxx = CmActLicense Firm Code, only valid as CmActL more
To start the CodeMeter daemon manually, please proceed as follows: 1. Open the System Settings - General LogIn Items. 2. you will find a CodeMeter Icon 3. Deactivate the CodeMeter Deamon via the swits more
To program the Firm Access Counter (FAC) using CodeMeter License Editor, you must first create a Context File (*.WibuCmRaC) of the affected CmContainer and Firm Code. As always, your Firm Security Box more
If the CodeMeter service does not start, this could also be the case for security reasons. In this case, an encrypted file in the format "LicenseLock .log" is stored in the CodeMeter logs directory, b more
The LicenseLock-*.log file The file LicenseLock-*.log is created, if the Firm Access Counter (FAC) has been modified according to AxProtector encryption settings and the Firm Access Counter has reache more
To create a CmDust.log, depending on your operating system, please proceed as follows: Windows 1. Connect CmDongle. This step is omitted if using CmActLicense. 2. Open CmDust using the "Start All Prog more
If the CodeMeter service (CodeMeter.exe) stops automatically after a few minutes, this indicates that the self-diagnosis of CodeMeter strikes because a process attached to CodeMeter is detected. For e more
You can also create the server search list of a WibuKey client "manually" in the registry (with regedit.exe). Here you have to differentiate between the settings for the users and for the computer. If more
How can one easily determine via console whether the WibuKey kernel drivers are running? Under Windows enter the command wku32.exe in the console at C:\Program Files (x86)\WIBUKEY\Bin. Under macOS and more
In general, it was examined which possibilities our driver software "offers" foreign code to potentially carry out manipulations on systems. Please note that the security of protected/encrypted applic more