Think you are having a Codemeter issue?

Make sure to try the simple things first like plugin it into another USB port or hub and on try on another PC or Mac if you have one.
CmSticks like a solid 5 volts of power so make sure it's not it a low budget USB hub.
Mac users might want to cold boot their mac a few times also.
(I know this sounds crazy, but it has fixed 4 systems in the past)
Also make sure the runtime is started when your Mac or PC is booted and if not set it to auto-start in your OS.

Next let's check the the stick is being seen and your license is in tact...

First.... do you see your CmStick appear in the Control Center?

Next....click the Webadmin button and go to Content/.Licenses
do you see your license there?

 

Note: a 300 license is for 3.x and a 200 license is for BaseHead 2.x and 400, 410 and 420 will be for version 4.x.
Make sure you installed the correct software version for the license you have on your CmStick
I can't tell you how many time I have been emailed about an error saying it's looking for a 300 license when the user purchased only has version 2.x (200) and never upgraded to 3.x....8)

If your stick and license seem to be correct and your software still isn't launching and your still getting a Codemeter error then follow the below steps for the best practices to re-install the Codemeter runtime. 

-Remove the CodeMeter CmStick from your USB port.
Make sure you have top level system admin access to the computer. 
If on a domain, and in a domain admin group, make sure the particular system is granting system admin status to domain admin group. 

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 Here and download the latest executable installer for the CodeMeter runtime for your system.

-Right-click the executable installer and select "run as admin"

-Plug the CmStick back in.

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 email to Codemeter support at  support@wibu.us

Make sure to put "BaseHead CmStick Problem" in the subject line with as much info as your can supply about your system


Mac users:
-Download and run the DMG installer from Here and choose the un-install option

- Reboot!!

- Then Re-Run that same DMG and do a new install

- Plug the CmStick back in.

- 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 email  to Codemeter support at  support@wibu.us

Make sure to put "BaseHead CmStick Problem" in the subject line with as much info as your can supply about your system