How can we help?
Table of Contents
< All Topics

Codemeter CmStick Troubleshooting

If you are a new CmStick user or need to get setup initially see the New User Setup info Here

Think you are Having a Codemeter CmStick 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.
  • Mac users might want to cold boot their mac a few times also
    (I know this sounds strange but has fixed 4 systems in the past)
  • Also make sure the runtime is starting when your Mac or PC is booted
  • A CmStick stick requires a “good healthy 5 volts” so try plugging in direct to you PC/Mac next.
  • So if it’s plugged into a hub, make sure it a good quality one.
  • Next let’s check the stick is being seen and your license is in tact…

So first…. do you see your CmStick appear in the Control Center?

If so….make sure you have the most recent firmware.  Press the hooked arrow to update the firmware.

  • 2nd, do you have the most recent CodeMeter Runtime Installed?
    See the bottom of this page for how to do a proper un-install re-install of the CM Runtime with links.
  • 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 are for 4.x and 500-530 are for 5.x  etc….

  • Make sure you installed the correct software version for the license you have on your CmStick. I can’t tell you how many times I have been emailed about a 300 error when the user purchased only version 2.x and never upgraded to 3.x….8)
  • If your stick or 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.

 

macOS 10.15 (Catalina OR Higher) users:
If your CmStick is no longer showing up in the CodeMeter Control Center after upgrading your OS, then in macOS Preferences/Privacy&Security, Privacy tab…
Select Full Disk Access, and then check “CodeMeter” ON to resolve this issue. 

 

BaseHead CMStick Troubleshooting
Click a box below to see the answer
How to do a full Codemeter runtime reinstall

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 CmDust diagnostic file to send to us, (see below)


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 us. (see below)

How to create CMDUST diagnostic file for your CMStick for us to look at

How to Create a CmDust for for PC:
Go to Start->CodeMeter->Tools-> CmDust to generate a Dust diagnostic file.
Grab that dust file created from your user folder and send that to us in a Support Ticket
Never email us direct for support issues.  

Always create a Support Ticket.  Thx!


How to Create a CmDust for for Mac:
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/home  folder and email  to  us in a Support Ticket.
Never email us direct for support issues.  

Always create a Support Ticket.  Thx!

CMStick appears as a device on macOS but is not detected by CM Management software

Solution provided by Wibu

The Problem is that the CmDongles are configured as massStorage Devices.
Because of Changes in the MacOS handling of Kernel Extensions_
As of version 7.10, CodeMeter Runtime no longer contains a Kernel Extension (kext). If you use a CmDongle, it is recommended to check the communication mode prior to upgrading.
If your CmDongle is already configured as HID, nothing has to be changed. Otherwise please contact Wibu support to learn how to reconfigure your CmDongle before upgrading.

To check:
– Open a terminal (“cmd” + “Space”)
– Run “cmu -s<serial number> –show-config-disk”.
– Check the line “Communication”
—

So you need to reconfigure this CmDongle to the HID communication mode if this is possible for the CmDongle.

CmDongles without real flash memory, i.e. devices with a memory of less than 128 MB, can be configured to be detected as a local disk or removable disk. Depending on how your system is configured and interacts with the CmDongle, it might be helpful to change the configuration. For reconfiguring a CmDongle, please proceed as follows:

1. Open a CodeMeter Command Prompt using “Start | All Programs | CodeMeter | Tools | CodeMeter Command Prompt”.
2. Read the current configuration.
Execute the following command, replacing the <serial> with your CmDongle serial number, e.g. “3-4567890”:
cmu32 -s <serial> –show-config-disk
3. Reconfigure your CmDongle to be detected as removable device.
Execute: cmu32 -s <serial> –set-config-disk RemovableDisk
4. Reconfigure your CmDongle to be detected as local disk.
Execute: cmu32 -s <serial> –set-config-disk LocalDisk
5. Reconfigure your CmDongle to HID Communication. Please note the technical requirements. Details see KB-0111
Execute: cmu32 -s <serial> –set-config-disk HidCommunication
6. Remove and replug the CmDongle.