Free appointment

Documentation
Back to

Installation not possible

If you get a license error installing ActiveImage Protector 2022 and previously had ActiveImage Protector 2018 installed

  1. Uninstall the old software, you can keep the tasks/settings. Then start the setup for ActiveImage Protector 2022 again.
  2. If the error message remains unchanged, delete this registry key on the system: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\7BC49C2F-160D-4EDB-A430-B98F39268281
  3. Then start the setup for ActiveImage Protector 2022 and install the software.


You install ActiveImage Protector 2022, but in the end there is no software installed that you can start. 

  1. Uninstall ActiveImage Protector from the system (if installed).
  2. In the Windows Registry, go to the path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete the key cbfilter20 if present.
  3. Restart the system.
  4. In the path C:\Windows\System32\drivers\ delete the file cbfilter20.sys if it exists.
  5. Start the setup for ActiveImage Protector 2022 and install the software.

 

Other main causes

  • Make sure you are using the correct setup for your product license.
  • Check that you have entered the correct product license for the selected system.
  • Check whether the operating system used is supported by the software.
  • If a 30-day trial license has already been used on the system, no further 30-day trial license can be used again.

 

If you want to perform an agent-based installation on virtual VMware guests and you use OEM/ROK Windows licenses

  1. Login to the vSphere Client or vSphere WebClient and then select the virtual machine and right-click and select "Edit Settings". Then select the "VM Options" tab and then select "Advanced".
  2. In the "Configuration parameters" section you will find the "Edit configuration" button where you can then add the following lines.
  3. Click on "Add parameters" and then enter smbios.addHostVendor in "Key" and enter true as "Value".
  4. In the search field for "Key" enter SMBIOS.reflectHost and then SMBIOS.noOEMstrings. These two parameters must not be used. If they are present, remove the parameters.