Product Advisory: Secure Boot Violation Error Following Windows Updates
Products Affected:
- Reboot Restore Enterprise / Standard
- RollBack Rx Pro
Issue Identified: Secure Boot Violation: Invalid signature detected error during software installation or deployment.
What Is Happening
Horizon DataSys support has received reports regarding a Secure Boot Violation error occurring during the installation or deployment of RollBack Rx and Reboot Restore.
This issue stems from recent changes introduced in Windows updates—specifically associated with KB5089549 (OS Builds 26200.8457 and 26100.8457). This Windows release updates the Secure Boot Forbidden Signature databases (DBX / SBAT policies), which inadvertently revokes or blocks the bootloader signatures used during our setup process.
Recommended Workaround
If you need to deploy or install our software immediately, you can bypass this error by temporarily disabling Secure Boot in your system's UEFI/BIOS settings:
- Reboot your system and enter the UEFI/BIOS setup menu (typically by pressing
F2,F12, orDELduring initial startup). - Navigate to the Security or Boot tab.
- Locate Secure Boot and change its status to Disabled.
- Save settings and restart into Windows.
- Resume normal boot: Disabling Secure Boot restores the proper function of the RollBack Rx or Reboot Restore bootloader, allowing your PC to boot into Windows normally and complete the software installation and activation process.
Important Security & BitLocker Notice:
- BitLocker: If BitLocker Drive Encryption is enabled on your drive, ensure you have your BitLocker Recovery Key backed up before modifying UEFI/BIOS settings. Changing Secure Boot states may trigger BitLocker recovery.
- Best Practice: Disabling Secure Boot is a temporary workaround. We recommend keeping Secure Boot managed in accordance with your organization's IT security guidelines until our patched installer is available.
Status & Next Steps
Please rest assured that our software remains completely safe to use. Horizon DataSys is actively working directly with Microsoft to update our bootloader signatures and align with the latest Windows Secure Boot policies.
We are working to publish an updated, fully compliant installer package as quickly as possible to resolve this issue permanently.
Need Assistance?
We sincerely apologize for any disruption this may cause to your workflow or deployments. If you require further guidance or run into issues during setup, please submit a ticket directly through the Horizon DataSys Support.