OpenText Server Backup
System Restore from
Bootable Media Creator version 9.40.1037
Release Notes, January 28, 2025
______________________________________________________________________
Contents
1	Overview
1.1	Release History
1.2	Supported Platforms
2	NEW FEATURES
3	INSTALLATION NOTES
3.1	Installation Requirements
3.2	Licensing
3.3	Installation Files
4	FIXES AND KNOWN ISSUES
4.1	Fixes
4.2	Known Issues
5	PRODUCT SUPPORT
5.1	Technical Support
5.2	Product Updates
5.3	Documentation
© Open Text 2025
The release notes are governed by the Terms of Service found here. The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
______________________________________________________________________
1	Overview
This document contains release notes for System Restore from Bootable Media Creator version 9.40. 
Using System Restore 9.40, you can restore a Windows computer from a BMR backup created using Windows Agent or Image Plug-in versions 8.30 to 9.40.
Note: BMR backups created using Windows Agent version 9.40 can only be restored using System Restore version 9.40 or later.
Before using System Restore, you must create recovery media using the Bootable Media Creator utility (BMC). Recovery media is a USB flash drive, CD, DVD or PXE boot server with a System Restore ISO image file. Beginning in version 9.40, you must create separate recovery media for restoring systems with Windows Server 2025, Windows Server 2022 or Windows 11, and for restoring systems with Windows Server 2019, Windows Server 2016 or Windows 10. For more information, see BMC Requirements.
You can restore from a backup in a vault. 
1.1	Release History
Version 9.40.1037, January 28, 2025
1.2	Supported Platforms
Bootable Media Creator (BMC) is supported on 64-bit versions of the following Microsoft platforms:
•	Windows Server 2025 1
•	Windows Server 2022
•	Windows Server 2019
•	Windows Server 2016
•	Windows 11 1
•	Windows 10
1 On Windows Server 2025 and Windows 11 24H2, BMC can only create recovery media for restoring systems with Windows Server 2025, Windows Server 2022 or Windows 11. 
Windows Assessment and Deployment Kit (Windows ADK) and the Windows Preinstallation Environment (Windows PE) must be installed before you can create recovery media using BMC. See BMC Requirements.
Note: BMC is only supported in English. 
1.2.1	Supported operating systems
System Restore can restore systems with the following 64-bit Microsoft operating systems:
Supported Operating System	Editions	Service Pack/Version	
Windows Server 2025	Standard, Datacenter, Server Core		
Windows Server 2022	Essentials, Standard, Datacenter, Server Core		
Windows Server 2019	Essentials, Standard, Datacenter, Server Core		
Windows Server 2016	Essentials, Standard, Datacenter, Server Core		
Windows 11	Home, Pro, Enterprise	Version 24H2	
Windows 10	Home, Pro, Enterprise	Version 22H2	
1.2.2	Supported file systems
This System Restore version supports NTFS for recovery of Windows and data volumes. The application also supports FAT and FAT32 for volumes that are required for the boot process.
1.2.3	Supported disk layouts
•	MBR 
•	GPT 
1.2.4	Supported storage type
This System Restore version can restore computers from backups saved in vaults.
1.2.5	Supported OEM partitions 
0x12 // EISA partition (Compaq) 
0x84 // Hibernation partition for laptops 
0xA0 // Diagnostic partition on some Hewlett-Packard notebooks  
0xDE // Dell partition  
0xFE // IBM IML partition 
1.2.6	Limitations
On Windows Server 2025 and Windows 11 24H2, BMC can only create recovery media for restoring systems with Windows Server 2025, Windows Server 2022 or Windows 11. 
System Restore is not supported with 32-bit hardware or operating systems.
To restore a volume from an Image backup, the disk on the destination machine must have the same sector size as the original disk. For example, if a volume is backed up on a disk with 512 byte sectors, it cannot be restored to a disk with 4 KB sectors.
System Restore can only restore encrypted volumes (e.g., encrypted by BitLocker) if they were unlocked at the time of backup.
System Restore is not supported on VMware ESX 4.x.
UEFI backups cannot be restored to Generation 1 Hyper-V virtual machines, which do not have support for UEFI.
2	NEW FEATURES
Automatically map volumes from backups to destination machines
System Restore can now automatically map volumes from a backup to a destination machine. This simplifies the restore process, as you do not have to manually drag volumes from the source system to the destination machine in the System Restore wizard.
If you click the AutoMap button during a restore, System Restore automatically maps all protected volumes from the source (protected) system to corresponding disks on the destination machine and clears any existing data from the destination disks. Data is not cleared from disks that are not destinations in the restore.
The AutoMap feature is available when the source and destination systems use the same firmware (either UEFI or BIOS), each system has a maximum of four disks, and corresponding disks on the destination machine are the same size or larger than disks on the source system. For complete system requirements, see the System Restore 9.4 User Guide.
CD boot entries created in Hyper-V environments
When you restore a system to a Hyper-V environment, a CD boot entry is now created on the restored system. 
Support for BMR backups created using Windows Agent 9.40
System Restore 9.40 can restore systems from BMR backups created using Windows Agent 9.40. BMR backups created using Windows Agent 9.40 cannot be restored using earlier System Restore versions.
3	INSTALLATION NOTES
Before restoring systems using System Restore, you must create recovery media using the Bootable Media Creator utility (BMC). For instructions, see the System Restore User Guide. 
3.1	Installation Requirements 
3.1.1	BMC Requirements 
Windows Assessment and Deployment Kit (Windows ADK) and the Windows Preinstallation Environment (Windows PE) must be installed on a system before you can create recovery media using BMC. 
Beginning in version 9.40, you must create separate recovery media for restoring systems with Windows Server 2025, Windows Server 2022 or Windows 11, and for restoring systems with Windows Server 2019, Windows Server 2016 or Windows 10. As shown in the following table, the required Windows ADK and Windows PE version depends on the operating system versions that you want to restore. Before creating recovery media, you must uninstall any other Windows ADK and PE version and install the required version.
Operating systems to restore	Required Windows ADK and PE version	
Windows Server 2025, Windows Server 2022 or Windows 11	10.1.26100.1	
Windows Server 2019, Windows Server 2016 or Windows 10	10.1.17134	
You can download Windows ADK and Windows PE from Microsoft and install them before running BMC, or when you run BMC.
General requirements for BMC: 
•	A computer running one of the supported operating systems listed in section 1.2 
•	CPU and RAM to meet the basic requirements of your operating system, as prescribed by Microsoft 
•	16-bit (or greater) video properties for optimal GUI display
•	A TCP/IP stack (for downloading Windows ADK and Windows PE, if they are not already installed on the computer) 
•	.NET Framework 4.8. If .NET Framework 4.8 is not present on the machine where you install BMC, you will be prompted to install it.
•	At least 100 MB of free disk space for BMC installation 
•	At least 7 GB of free disk space for installing Windows ADK and Windows PE 
•	At least 500 MB of free disk space for creating an ISO file 
The system drive requires free space to uncompress the packages (regardless of which drive the installation targets) for installation. The environment variables TEMP and TMP use %USERPROFILE% by default. Make sure that %USERPROFILE% points to a drive that has sufficient temporary space. 
3.1.2	System Restore Requirements
System Restore requires the following (minimum) hardware: 
•	AMD64/Intel 64 processors (No support for Itanium processors)
•	1 GB of RAM 
•	CD/DVD drive
•	800 x 600 minimum screen resolution
•	Network interface card for connecting to vaults
3.2	Licensing
System Restore does not require a license to restore. To back up to a vault, a valid license is required. 
For more information, contact your service provider.
3.3	Installation Files
Bootable Media Creator is available in a self-extracting installation kit: BootableMediaCreator-9-40-1037.exe
BMC produces bootable images with the following file names: 
•	System-Restore_win2022_11-9-40-1037.iso
•	System-Restore_win2019_10-9-40-1037.iso
To see instructions for using BMC to create the bootable image, refer to the System Restore User Guide. 
4	FIXES AND KNOWN ISSUES
4.1	Fixes
An issue has been addressed where, in rare cases when restoring from Local System backups, volumes could not be formatted. (2453805)
After you restore a Windows Server 2025, Windows Server 2022 or Windows 11 Hyper-V VM with three or more disks to a Hyper-V environment, the VM now boots successfully. (4232417/3243943)
4.2	Known Issues 
When you try to create recovery media using BMC, the process sometimes fails with an "Error code:1" message. This can occur due to the antivirus program on the computer where you are running BMC.
WORKAROUND: Either run BMC on a computer with a different antivirus program, or uninstall and then reinstall Windows ADK, disable the antivirus program, and run BMC again. (4358201)
When you start a restored computer, ReFS volumes might be offline. This can occur if the ReFS version used by Windows PE is not compatible with the Windows version of the restored computer. 
WORKAROUND: Use System Restore to restore the system without ReFS volumes, and then restore the ReFS volumes to the system using the Windows Agent. (2453667)
When restoring a system to a Hyper-V destination machine, the order of the destination machine disks in the System Restore wizard is sometimes different than the order of the disks in the virtual machine settings. (3061217)
Removable USB drives on the source or destination system are counted in the number of disks on the system and could prevent the AutoMap feature from being available— even though removable USB drives are not backed up and cannot be used as restore destinations. 
WORKAROUND: If the AutoMap feature is not available, manually create a restore plan by dragging volumes from the source to the destination system. If the removable drive is on the destination system, remove the drive before the restore. (3156832)
If you restore a system from an Image backup, synchronize an existing Image backup job, and then run the backup job, the agent cannot find volumes to back up on the restored system. 
WORKAROUND: After restoring a system from an Image backup, edit the existing backup job and select the volumes again. The next backup will be a re-read. (2457765/EV-67024)
When creating recovery media using the Bootable Media Creator, an Insufficient memory error can occur if you try to add a driver with a long path and file name. (2459898/EV-56397)
If you try to restore a volume that is formatted with a 2K block size to a disk that has a 4K cluster size, the restore fails with the following error message: Cluster must be multiplication of the physical sector size. For more information, see the knowledge base article for this issue. (2466345/EV-32435)
When you try to restore to a destination disk with an OEM volume, the restore may fail with the following message: BMR is not able to get drive letter for mapped volume. Restore cannot proceed further. Please cancel and try again.
WORKAROUND: Delete all partitions from the destination disk. Change the disk format to GPT and then back to MBR, and then try the restore again. (2473919/EV-16204)
When mapping a volume from an Image backup using System Restore, even if you drag and drop the volume to a larger size destination, you may get the following message: Volume cannot be mapped. The destination is not of the same size. 
WORKAROUND: Right-click the volume, delete the partition on the destination disk, and try again. (26822)
If you seed BMR backups using a Quick Ship Vault, direct-attached storage, or disk, after your data is successfully imported into the vault, run a backup to the vault. Failure to do so may result in you not being able to restore your system. (26829)
Due to a Windows PE limitation, System Restore restores cannot run for longer than 72 hours. The Windows PE overview site states, "To prevent its use as a production operating system, Windows PE automatically stops running the shell and restarts after 72 hours of continuous use." (25803) 
If backup data is reformatted to an unsupported file system (e.g., FAT32), dragging and merging of an NTFS safeset to the reformatted volume may appear to preserve the destination format (e.g., FAT32). Associated restores, however, may fail. (25631)
Disk B may not be selectable for backup (Local System/Data Files). When an NTFS disk B is created in Windows Disk Management, it may not be selectable when you create a BMR-type backup job. (20867) 
System Restore may not retrieve the drive letter for a mapped volume if you drag and drop a large number of partitions (20 partitions, for example) to a GPT disk. The restore may not proceed further. 
WORKAROUND: Cancel and try again, selecting fewer partitions. (20854) 
System Restore may not preserve Quota Settings (user hard-disk space settings) for NTFS partitions.
WORKAROUND: Use the Image Plug-in instead of System Restore. The Image Plug-in preserves quota settings. (20669)
5	PRODUCT SUPPORT
5.1	Technical Support
Contact information is available from your provider. 
5.2	Product Updates
Product updates are available from your provider. 
5.3	Documentation
The following documentation is available for System Restore: 
•	System Restore User Guide 
•	System Restore release notes (this document)
All documentation is available from your service provider.