How can we help?
Table of Contents

Old License Archive Info

< All Topics

Old License Archive FAQ

 

Below are some problems with solutions for very old licenses!

It’s is extremely recommended to ‘Extend’ you Maintenance Period and to be able to use to more modern Licensing System as 4.x is no longer Supported but these pages were left here to hopefully help a few people out.  😉

--- Frequently asked questions ---

How do I manually Remove or Install an old version 4.x USB/ILok bound plugin?

The document explains where we install the License Apply plugin for version 4.x so you can either remove it or in some case have to install it manually.

Version 5.x users, none of this applies to you cuz we re-did this system completely in version 5.x.

Manual Plugin Removal Process

First up is the manual removal process.
The Windows plugin location is here:

C:\Program Files (x86)\Common Files\WIBU Shared\Plugins\5000538

For macOS the location is here:

<System Drive>/Library/Application Support/CodeMeter/Plugins/5000538

The plugin is two grouped files…..One .dll and  one .wbc

both will have the same serial number embedded in the name of your USB Flash drive or iLok.
If you can’t find these files then your are probably in <user>/Library instead of the System Library folder.

Locate the plugin pair you no longer need and delete it.  If you have multiples installed and are unsure what serial numbers to delete then use License Request to help figure that out or look at the XML files inside the License Apply package you want to kill off.

TIP: If you are getting a file locking error then you’ll need to kill the CodeMeter process located in the CM Control Center on PC.

On macOS it’s in System Preferences:

Now that you have the files deleted….Restart the CM Process and then look at the CM Control Center and you will see the old license with a red broken symbol like this.

This won’t hurt anything, but if it annoys you to look at do the below steps….

PC:
Open up a command prompt and enter this (Replacing the container number the one you want to remove)

“C:\Program Files (x86)\CodeMeter\Runtime\bin\CMU32” –delete-cmact-license –serial 128-12747072

Mac and Linux:

Open terminal and enter this (Replacing the container number the one you want to remove)

Cmu –delete-cmact-license –serial 128-9827899

It should all be cleaned up now…..Done and Done!   8)

===================================================================================

Manual Plugin Install Process

To do a manual Medieval style install cuz maybe something is not working with the License Apply package you were sent…

PC:

Open the License Apply package and go to the ‘files’ folder

Copy the two plugin files that begin with 5000538 to here

C:\Program Files (x86)\Common Files\WIBU Shared\Plugins\5000538

The last step is to manually drag the CustomBinding.WibuCmRaU file from the ‘files’ folder to the CodeMeter Control Center.

Hopefully you don’t get an error and see the license appear after.  If not, create a support ticket to resolve this.

Done and Done!

————————————————————-

Mac:

For macOS the two plugin files can either be in a subfolder named “‘files’ like here….

But if you have a newer version, you won’t have this folder there and instead you’ll need to right click License Apply.app select “Show Package Contents” and go to Contents/Resources/files

Then locate and copy the two files that begin with 5000538 to this location

/Library/Application Support/CodeMeter/Plugins/5000538

The last step is to manually drag the CustomBinding.WibuCmRaU file from the ‘files’ folder to the CodeMeter Control Center.

Hopefully you don’t get an error and see the license appear after.  If not, Create a support ticket to resolve this.

Done and Done!

Having a version 4.x USB Device Locking Issue or System Drive locking issues?

(This Includes iLok2/3 binding …. For CmSticks THIS PAGE*)

First…. do you see your License appear in the CodeMeter Control Center?
If it’s Red and says “Activation Invalid” like the below image you are definitely having a CodeMeter Runtime Issue.

Always the first thing to try is a FULL Un-install and Re-Install of the CM Runtime in this case.

Instructions to do this can be found at the very bottom of this page for you platform.
This also insures you have the latest version and are up to date.

I'm getting an error message like the below. What does this error mean?

This is saying that your license a 4.x Ultra license is missing with the number 420 in it.

Maybe you launched the wrong version to match your license?

420 is 4.x Ultra

410 is 4.x Standard

400 is 4.x Lite

300 license is for 3.x and a 200 license is for BaseHead 2.x

Make sure you installed the correct software version for the license you purchased.
I can’t tell you how many time I have been emailed about a 420 error when the user purchased only version 2.x and never upgraded to 4.x….8)
 

Below are other error message and solutions you may see after running License Apply…..

My License is Red in the CM Runtime after a System Restore or Hard Drive Clone.  

I can’t repair it and getting a 262 Error also.

 

 

This mean you probably have an older license that wasn’t written with the ability to re-import.

Contact BaseHead Support for a new Custom Binding Plugin Package for your USB Flash Drive or iLok2.

I'm getting an error with License Apply saying is damaged and can't be opened?

This is super poor error message by Apple cuz it just doesn’t recognize this version of License Apply you have.

Two ways to fix this….

  • Use an unzip utility like Keka to unzip the package instead of the built in macOS can resolve this OR…
  • Go to your System Prefs/Security Privacy and in ‘Allow apps downloaded from:’ check ‘Anywhere’. See this PAGE for step by step instructions

I just ran License Apply and get a 263 or 264 error. How to Fix?

This is usually  caused if you are using a Cloned Drive or a System Restore that was just done using something like Time Machine. (TimeMachine)

The fix is to do a full Un-install Re-Install of the CM Runtime to fix that.  See below how to do that.

I'm getting a 266 error on macOS when I try to bind to my system drive and drag the .wbb file to the Control Center to create a context file.

 


This is probably caused cuz you dragged the .wbb in once already, but it’s just invisible so it’s impossible to use the UI to create a context file.  The fix is to open terminal on OSX and run this command to create a context file manually.
cmu –context 5000538 –file BHRequestFile.WibuCmRaC

Then send us this file named BHRequestFile.WibuCmRaC that was just created in the location where terminal is currently set to.

On Windows I'm getting a 101 or 102 Error when trying to install on a fresh System?

This usually means you are missing some key C++ runtime components that now in included in the newer License Apply Packages.
Email us for the fix and mention this page where you read this so we can get you a newer package to use.

On Mac I'm trying to install my custom plugin installer with License Apply on a new system, but I see a bunch of Red X's and files are missing.

Apple broke the older plugin installer in 10.12. Contact BaseHead Support to get an updated installer.
Make sure to add  a screenshot like above so we know what the problem you are speaking of.

How do I do a proper un-install re-install of the CM Runtime?

PC users:

  • Remove the CodeMeter runtime through the operating system control panel
  • If you find more than one installation of the CodeMeter runtime, remove them too.
  • Reboot!!
  • Go HEREand download the latest executable installer for the CodeMeter Runtime for your system.
  • Right-click the executable installer and select “run as admin”

If this procedure doesn’t fix your problem, then you need to create a diagnostic file to send to Codemeter
go to Start->CodeMeter->Tools-> CmDust to generate a Dust diagnostic file.
Grab that dust file created from your user folder and attach it to us in a Support Ticket.

Mac users:

  • Download and run the DMG installer from HERE, Run It and Choose the Un-install option
  • Make sure it deleted the CodeMeter Control Center, otherwise do it manually.
  • Reboot!!
  • Then Re-Run that same DMG and do a new install

If this procedure doesn’t fix your problem, then you need to create a diagnostic file to send to CodeMeter
Open a terminal and type: cmu –cmdust –file CmDust-Result.log to generate a Dust diagnostic file.
Grab that dust file created from your user folder and attach it to us in a Support Ticket.

How to Remove a v5.0 USB Window License

This information is for version 5.0 ONLY for Windows PC’s (Non-CmStick users)
5.1 and higher uses a new .key file system

To manually remove a USB Device bound license, from the CodeMeter Control Center, follow the steps below:

PC:
Open up a command prompt and enter this (Replacing the container number with the one you want to remove)

“C:\Program Files (x86)\CodeMeter\Runtime\bin\CMU32” –delete-cmact-license –serial 130-304400587

 

Mac and Linux:
Open terminal and enter this (Replacing the container number with the one you want to remove)

Cmu –delete-cmact-license –serial 130-304400587