کوردیالعربيةEnglish

Mikrotik Change Software Id Link (99% LIMITED)

Changing a MikroTik Software ID (SoftID) is not possible through standard settings because it is a unique identifier generated based on your hardware's storage media (NAND or HDD).

Because licenses are bound to this specific ID, changing it would immediately invalidate your current license. Common Scenarios for "Changing" the ID

While you cannot manually edit the ID, you may need to manage it in these specific situations:

Replacing Hardware (HDD/Flash): If you replace the drive on an x86 system, the SoftID will change. You can request a one-time "License Replacement" key from MikroTik support or through your account on mikrotik.com.

Virtual Machines (CHR): In Cloud Hosted Router (CHR) environments, the System ID is tied to the VM's UUID. You can transfer a CHR license to a new instance by logging into your account and using the Transfer button.

Typing Mistakes (x86): If you made a mistake while manually entering a SoftID on the website to generate a key, MikroTik allows a free correction of up to 2 characters before the key is upgraded. mikrotik change software id link

Generating a New ID (CHR): You can use the command /system/license/generate-new-id, but be warned: this wipes your current license and puts the device into free mode. Do You Actually Mean "Identity"?

Users often confuse the Software ID (for licensing) with the System Identity (the router's name). If you just want to change how your router identifies itself on the network: RouterOS license keys - MikroTik

In MikroTik RouterOS, the Software ID is a unique identifier generated based on the storage medium (HDD, SSD, or USB) and cannot be manually edited or "changed" like a setting.

If you need to link a license to a new Software ID due to hardware failure or a system migration, use the following procedures: 1. Cloud Hosted Router (CHR) License Transfer

CHR licenses are the most flexible and can be transferred between virtual instances via your MikroTik account. Changing a MikroTik Software ID (SoftID) is not

Step 1: Register the new CHR. Log into the new instance and run: /system license renew. Enter your MikroTik account credentials to add it to your account.

Step 2: Transfer the license. Log into the MikroTik Account Portal, navigate to All CHR keys, find the old license, and click Transfer.

Step 3: Select target. Choose the new Software ID from the dropdown menu to link the license. 2. x86 License "Replacement Key"

For traditional x86 installations, the license is permanently tied to the storage drive. If the drive fails, you cannot "move" the key yourself and must request a Replacement Key.

Cloud Hosted Router, CHR - RouterOS - MikroTik Documentation The System Identity: This is the name of the router (e

  1. The System Identity: This is the name of the router (e.g., "MikroTik-Router-01").
  2. The RouterBOARD License "Software-ID": This is a unique hexadecimal ID tied to the hardware itself (e.g., ABCD-EFGH), used to register a license key.

Most users asking to "change software id link" are usually trying to rename the router so it shows up correctly in network scans or management links (like WinBox or Dude).

However, if you are trying to change the actual License Software ID, that is impossible via software commands.

Here is the guide for both scenarios.

RouterBoard / CCR (Physical MikroTik Hardware)

You rarely need to change the Software ID here. The license is embedded in the RouterBOOT. If you buy a used RouterBoard, the license stays with the board. If you need to transfer a license to a RouterBoard, you must use the "Sell" command on the old device first.

Method 1: Via WinBox (GUI)

  1. Open WinBox and connect to your router.
  2. On the left menu, click System.
  3. Click Identity.
  4. In the Name field, enter your desired name (e.g., Office-Floor-1).
  5. Click Apply or OK.
    • Note: If you are connected via MAC address (Layer 2), the "Name" column in the Neighbor Discovery list might take a moment to update.

Part 4: Special Cases: CHR (Cloud Hosted Router) vs. x86 vs. ARM

The "linking" process varies slightly depending on your platform.