There are cases when Acronis Disk Director may require you to reboot the machine to perform an operation
Reboot
How to proceed with the issue when after successful deployment, the target system is being system patched on every reboot
After applying Try&Decide changes reboot the computer before creating Acronis Secure Zone with allocating space for it from system partition
Reboots the system
Restoring system partition requires the system to reboot before restoration starts
Acronis Backup & Recovery 10 asks for a reboot to increase, decrease or create Acronis Secure Zone, or to restore partitions
This has been fixed
This article applies to:
Restore the partition from Acronis Bootable Media
This has been fixed.
Reconfigure the virtual machine to solve the issue
Acronis Disk Director reboots in Windows Native Mode to commit pending changes, but the operation either fails with an error or completes with no result
Doing a hard reboot during a Try&Decide session can make the system unbootable
Acronis True Image inadvertently reboots the machine when run if there is File Securer installed
This is an issue in the Windows powrprof.dll library. Download the fix and replace Scheduler2 files
Acronis product reboots in Windows Native Mode, but the cloning or restore process finishes in a few seconds with no result
Restart the machine to solve the issue
While Restoring LVM volume created with Acronis Backup & Recovery 10 in Sector-by-Sector mode ask for reboot before restore is finished
As a workaround, recover from Acronis Bootable Media
Fixed in build 540
Do a hard reset of the machine
Symptoms
- You create a deployment task with the default option "Shut down" enabled for an Agent on Windows 8;
- After you perform a successful deployment, the Agent reboots instead of shutting down.
Cause
This is an irregular known issue.
Solution
As a workaround, please shut down the Agent machine manually (or through Remote Desktop).
Symptom
You try to perform an operation in Acronis Disk Director and the software requests a PC reboot.
After the computer is rebooted as requested, nothing happens. The operation is not performed.
Cause
One of the known causes of the above described behavior is an issue with scheduling the requested operation in the Windows registry.
List of recommendations on how to avoid system reboot after installing, uninstalling, updating or upgrading Acronis Backup & Recovery components in Windows
Acronis Backup & Recovery 11 shows Error "System is about to be shut down". Reboot your machine to solve this issue
Symptoms
Acronis True Image installed on macOS 11 Big Sur Beta causes kernel panic during boot that leads to cyclic reboots.
Kernel panic is a situation when Mac encounters a system error and keeps restarting unexpectedly with a warning message "You need to restart your computer".
Cause
Lack of compatibility due to a major shift in macOS architecture.
Symptoms
- You activate Try&Decide on a computer with Intel RAID (created with Intel Rapid Storage Technology)
- Try & Decide starts without errors, but on reboot, the dialog for selecting Continue or Discard does not appear. When you boot into Windows, Try&Decide is not active.
OR
After installation of Acronis Backup onto Windows XP a reboot is mandatory.
Symptoms
- You have an HP computer in UEFI mode
- You try to restore a system backup or perform a different operation with Acronis True Image that requires reboot
- After reboot, the system boots directly to Windows. Acronis True Image does not start in boot mode and the recovery/other operation is not performed
Cause
HP computers in UEFI mode use a specific boot order that overrides Acronis Loader.
Solution
As a workaround, change the boot order manually:
Description
The M1 is Apple’s new silicon system on a chip using ARM64 architecture. The new chip was designed to work with macOS Big Sur and it is used inside MacBook Air with M1, Apple Silicon MacBook Pro and Mac mini with M1.
Acronis Cyber Protect Home Office supports Macs running on Apple silicon processors.
Acronis True Image 2021 supports Macs running on Apple silicon processor starting from Update 5 (Build 39229).