If Windows Device Encryption is enabled, a VM restored using ActiveImage Protector to Proxmox VE or KVM may fail to boot

Details

We confirmed an issue where a restored guest OS does not boot when using ActiveImage Protector to restore to Proxmox VE or KVM in environments where Windows Device Encryption is enabled.

Conditions:

• ActiveImage Protector is installed in an environment with Windows Device Encryption enabled
• Windows Device Encryption (Windows 10 and Windows 11 only)

Related Topic: Device Encryption in Windows
 

Use one of the following ActiveImage Protector features:

- HyperRecovery (Restore Target: KVM or Proxmox)
- HyperStandby (Target Host: KVM or Proxmox)
- vStandby (Target Host: Linux KVM or Proxmox)
- Virtual Conversion (Conversion Type: for Linux KVM / Proxmox)

Causes

When restoring to Proxmox VE or KVM, ActiveImage Protector uses the Windows iSCSI Initiator to mount the target and installs the required storage/NIC drivers.

During post-mount processing, Windows Device Encryption is triggered on the iSCSI-mounted volume, causing it to become BitLocker-encrypted.

Although the restore completes normally after driver installation and unmount, the restored guest OS fails to boot.

This behavior is also reflected in the operating system task logs (UTC+09:00) and Windows System Event Logs, covering the iSCSI mount and unmount process.  

06/15/2026 04:11:58.010 Mount iSCSI target (10.123.1.190, iqn.2003-01.org:111.20260615-131157)
...
06/15/2026 04:14:47.079 [0] Disconnect iSCSI target return 0, 0

Windows Event Log (System)　BitLocker Event Log

Error    2026/06/15 13:13:57    BitLocker-Driver    24668    None

BitLocker write encryption failed on volume \?\Volume{8f749d12-380d-4875-b192-1e0cab6fd574} due to disk I/O error. Check the disk for bad sectors.

Information    2026/06/15 13:13:58    BitLocker-Driver    24660    None

BitLocker write encryption has started on volume \?\Volume{8f749d12-380d-4875-b192-1e0cab6fd574}.

Information    2026/06/15 13:13:59    BitLocker-Driver    24664    None

The final BitLocker sweep has started on volume \?\Volume{8f749d12-380d-4875-b192-1e0cab6fd574}.

Information    2026/06/15 13:13:59    BitLocker-Driver    24665    None

The final BitLocker sweep has been paused on volume \\?\Volume{8f749d12-380d-4875-b192-1e0cab6fd574}.

Information    2026/06/15 13:13:59    BitLocker-Driver    24666    None

The final BitLocker sweep has been resumed on volume \\?\Volume{8f749d12-380d-4875-b192-1e0cab6fd574}.

Information    2026/06/15 13:13:59    BitLocker-Driver    24665    None

The final BitLocker sweep has been suspended on volume \\?\Volume{8f749d12-380d-4875-b192-1e0cab6fd574}.

Symptoms when booting the restored guest OS:

1. Message: “Please attach the USB drive containing the BitLocker key.”
2. Blue screen error: UNMOUNTABLE_BOOT_VOLUME (0xED)
3. UEFI boot errors:
   • “BdsDxe: No bootable option or device was found.”
   • “BdsDxe: Press any key to enter the Boot Manager Menu.” 

Workaround

Please disable Device Encryption in the source environment before starting the restore operation.

We are currently investigating whether this issue can be prevented through a software fix.  

Target Product

- ActiveImage Protector 2022

59039369097881