I upgraded my CurrentWare to the latest version, do I need a new license key?

I upgraded my CurrentWare to the latest version, do I need a new license key?

The transition from an older version of CurrentWare to a newer one is smooth as the key remains valid and there’s no need for users to re-register.

It’s important to note that subscription keys are specific to each version at the time you register your licenses and will only function with that version. For example, v12.0 subscription keys can only be used with v12.0 and v11.0 subscription keys can only be used with v11.0. They are not compatible with other versions.


    • Related Articles

    • How to Upgrade CurrentWare to the Latest Version

      First time installing CurrentWare? Follow this deployment guide instead. Already have CurrentWare deployed and need to upgrade to the latest version? Here’s what you need to do: Back up your CurrentWare database Download the latest version of ...
    • Release Notes

      Version 12.0.1 Feb 12, 2026 PC & Users Search Option: Within various selection menus, additional support for a search bar has been added Updated Manage Page Column: Identify Last Logged-in User from Manage Page Alerting for Offline Clients: Setup an ...
    • How to find your CurrentWare Version

      This article will help you quickly identify your Currentware version. You may need this information for the Support team. Otherwise, it can help you to verify if you are up-to-date. When providing the version to support for any reason, make sure to ...
    • Move the CurrentWare server to another computer with network SQL database

      When moving your CurrentWare software to a new server/PC you need to make sure you do not have both consoles connecting to the same networked database. Here are the steps to take. #1 Back up your existing cwServer Database Before you migrate your ...
    • Renamed The CurrentWare Server PC

      If you renamed your CurrentWare server PC and find yourself having issues opening your web console, it’s likely due to the backend SQL connection properties. The easiest way to fix this issue is to do a quick uninstall and reinstall of the server ...