The list of reasons why a 1C license may stop working:

Problem: The 1C license fails regularly, approximately every 2-3 months.

Solution: Check your computer according to the following list of possible reasons, in the end of the list there is a table with recommendations for each case.

Below is an example of an error message that a program may generate (License not found. Software protection key or acquired software license not found ; Error linking program license to the computer; Software licensing error) : 

Here’s the list of reasons why a 1C license may stop working:

1. Technical reasons (hardware-related)
1.1. Replacing or failing hard drive / SSD where the license was installed.
1.2.Replacing the motherboard (hardware ID changes and the license becomes invalid).
1.3. Replacing the network card (MAC address is used for license identification).
1.4. Changing hardware configuration (e.g., adding/removing network interfaces or virtual adapters).
1.5. Using virtual machine images — cloning a VM breaks the hardware binding.
1.6. BIOS reset or motherboard firmware update.
1.7. Hardware failures (bad sectors, power surges, disk controller errors) damaging license data.

2. Software-related reasons
2.1. Reinstalling or upgrading the operating system (especially changing editions or architecture).
2.2. Restoring the system from a backup image that doesn’t include license data.
2.3. Using registry cleaners (CCleaner, Reg Organizer, etc.) that may remove license keys.
2.4. Deleting the license folder manually (typically `C:\ProgramData\1C\licenses`).
2.5. Failed 1C or configuration update corrupting license files.
2.6. Antivirus or Windows Defender interference, blocking or deleting license data.
2.7. 1C services or RLM server malfunction (for network licenses) — service not running or can’t detect the license.

3. Network and server-related reasons (for server/network licenses)
3.1. Connection problems with the license server (RLM server - Reprise License Manager, a server that manages software licenses).
3.2. IP address change of the license server.
3.3. License service (RlmService / HASP License Manager) failure.
3.4. Server reboot or crash without proper service shutdown.
3.5. Firewall or antivirus blocking required ports.
3.6. Multiple RLM servers running in the same network.

4. Hardware key (If you are using a physical license key, which is inserted into the USB port in the form of a flash drive - HASP, Sentinel, etc.)
4.1. Physical damage to the USB dongle.
4.2. HASP / Sentinel driver issues.
4.3. Key inserted into a different USB port or not detected by the system.
4.4. USB power or connection instability, improper system shutdown.
4.5. Unplugging the dongle while 1C is running (“hot removal”).

5. Virtualization-related reasons
5.1. Changing hypervisors (e.g., VirtualBox → VMware).
5.2. Moving a virtual machine to a different host.
5.3. Changing the VM’s UUID, MAC address, or hardware parameters.
5.4. Using snapshots or rollbacks that don’t include the license state.

6. Other reasons
6.1. License expiration (temporary license).
6.2. Incorrect system date or time.
6.3. Activation errors — e.g., 1C activation server unavailable.
6.4. Administrative mistakes — license data accidentally deleted.
6.5. Corrupted registry or system files.

7. What to do if the license stops working:
7.1. Check if the license appears in 1C → Help → About → Licenses.
7.2. Check the folder `C:\ProgramData\1C\licenses`.
7.3. Verify that Sentinel / Rlm / 1C Licensing Service is running.
7.4. Try to reactivate the license using the 1C Licensing Center.
7.5. If using a hardware key — check the dongle and drivers.
7.6. If necessary — contact FirstBit Hotline for recovery assistance.

8. Here’s a structured table summarizing all the main reasons why a 1C license might stop working and recommended recovery actions:

Thanks for being a Firstbit Customer! 

 #License #Recovery