Knowledge Base
- BSOD during HyperBack task
- Notes for performing a cold backup on an ftServer
- When booting boot environment by using ISO file created with BE Builder, AIP console fails to start
- Some backup schedules may be skipped
- After deploying a source image to multiple client computers using multicast, choose whether the computers should shut down when the data distribution is complete
- When Secure Boot is enabled, DVD boot may fail in a Windows-based boot environment
- Create boot environment by using ActiveImage Deploy USB 3
- The mouse and keyboard stop working during boot
- After restoring a hot-backup image of RHEL7.x, later backup tasks fail with Exit -314 error
- Updating the Retention Policy also updates the default setting
- When using HyperRecovery or restoring to another PC, existing schedules switch the tracking driver mode to CBC
- Middleware services won’t run unless installed on the C drive
- Volume Letters in Linux Boot Environment
- In CBC mode, disabling a schedule prevents incremental backups from running in the AIP console.
- HyperBack task failed with error: Exit Code -701
- When restoring an agent-based backup with some volumes excluded using HyperRecovery or Virtualization, the excluded volumes will appear as RAW (unformatted)
- HyperBack fails to back up a Hyper-V VM with Exit Code: 28677
- Backups of volumes on the second and later MBR disks with low space are done without VSS
- Creating a WinPE-based boot environment fails with ADK 10.1.26100.2454 if WinRE is missing or disabled
- Task failed due to invalid character (not a hex digit).
- Closing may fail if the backup task fails
- When running an offline backup with Deduplication Compression, temporary files might be saved to the local drive
- Boot environment creation fails on Windows Server 2016
- ActiveImage Protector Service isn’t compatible with Windows Server 2025
- Restoring a backup image may cause the system to restart or freeze
- Change the retry interval and count for agentless backup when snapshot creation fails
- Consolidation fail. Exit Code: -999
- Closed the console window using Alt+F4 during boot
- Linux-based boot environment fails to start after Windows Update
- Check the details of the USB device made with Deploy Media Creator