Skip to main content

Windows 8 Recovery with Secure Boot enabled

Thread needs solution

I am using a Windows 8 64-bit system with UEFI and Secure Boot enabled.

Having used Acronis TIH through several versions to backup and restore my systems, I needed to use a recent backup to overcome an issue whereby several programs were not opening although they did 2-3 days ago. The Recovery process was started as normal and the system rebooted as expected but it booted into Windows without actually doing anything more. Nothing was restored.

I am using build 6514 and have read something that suggests that there is a patch that overcomes this problem but cannot actually find it or a link to it. Can anyone help?

0 Users found this helpful

Andy,

If you have not yet created your 2013 build 6514 Rescue Media, do so from within the application, or go to your Acronis account online and download the ISO (image file for use in creating the bootable CD/DVD) and do so.

Boot to the Rescue Media and do your restore from there.

The Secure Boot patch was for build 5551, and in not needed for build 6514.

If your system will not boot correctly to the Rescue Media, it also will not boot properly (to the pre-Windows Acronis rescue environment) when attempting a restore or recovery from Acronis in Windows that requires the Acronis rescue environment to be able to do the restore/recovery.

In addition, the 6514 build of True Image Rescue Media will not see GPT disks properly for certain operations.

If your system will not boot to the CD/DVD/USB on your system initially, you can temporarily disable Secure Boot as well as choose a legacy BIOS mode (non-UEFI) if possible on your hardware. Perform the restore, and be sure to change the system firmware settings back before starting Windows.

If you have a previous build (5551) version of the Rescue Media, use it instead with Secure Boot and Legacy BIOS enabled to get around the GPT disk issues in build 6514.

I would also suggest that you open a case with Acronis support and report this issue to them (no charge for restore/recovery issues).