I’m trying to migrate my system from a small M2 NVME SSD to a larger and faster one, but I’ve had no luck using various disk cloning/imaging apps (True Image, Macrium Reflect, AOMEI Backupper, Paragon Backup & Recovery) to clone the old SSD to the new one. All of the OEM partitions on the destination SSD become “normal” primary partitions instead of OEM partitions, even when using sector-by-sector copy and no resizing options. This may be why the OEM recovery is no longer functioning, although the Windows system itself is still working fine. It’s possible that the BCD information has been affected, but I’m not sure how that could happen as a result of the cloning process. Is there a way to properly clone these OEM partitions to the new SSD?
Note: Recovery works again if I connect the old SSD through an M.2 to USB enclosure. This suggests that the BCD information is somehow pointing to the partition on the old SSD.
3 Answers
Introduction
When migrating your system to a new and larger SSD, it can be challenging to clone the OEM recovery partitions. OEM recovery partitions are crucial as they contain the factory settings of your device, and they can be used to reset your device in case of any issues. However, when cloning the old SSD to the new one, the OEM partitions on the new SSD can become “normal” primary partitions instead of OEM partitions. This can cause the OEM recovery not to function correctly, even though the Windows system is still working fine. In this blog post, we will discuss how to make a clone of OEM recovery partitions.
Understanding OEM Recovery Partitions
OEM recovery partitions are created by the device manufacturer to provide a way to restore the device to its original state. These partitions contain the factory settings of your device, including the operating system, drivers, and pre-installed software. The recovery partition is typically hidden and can only be accessed by specific key combinations during startup or through the device’s BIOS menu.
When you purchase a new device, the recovery partition is already installed, and you do not need to create one. However, if you upgrade your device’s hardware or reinstall the operating system, you may need to recreate the recovery partition. This is where cloning the OEM recovery partition becomes essential.
Why Cloning OEM Recovery Partitions is Important
Cloning OEM recovery partitions is essential when migrating your system to a new and larger SSD. When you clone the old SSD to the new one, you want the new SSD to have the exact same settings as the old one. This includes the OEM recovery partitions. If the OEM recovery partitions are not cloned correctly, the recovery may not function correctly, and you may lose the ability to restore your device to its original state.
How to Clone OEM Recovery Partitions
To clone OEM recovery partitions, you will need a disk cloning software that supports cloning OEM partitions. Here are the steps to follow:
1. Download and install a disk cloning software that supports cloning OEM partitions. Some of the popular disk cloning software that supports cloning OEM partitions include Clonezilla, EaseUS Todo Backup, and Macrium Reflect.
2. Connect the old SSD to your device using an M.2 to USB enclosure.
3. Launch the disk cloning software and select the old SSD as the source disk.
4. Select the new SSD as the destination disk.
5. Select the option to clone all partitions, including the OEM recovery partitions.
6. Start the cloning process.
7. Once the cloning process is complete, shut down your device and remove the old SSD.
8. Install the new SSD and turn on your device.
9. Verify that the OEM recovery partitions have been cloned correctly.
Troubleshooting
If the cloning process did not clone the OEM recovery partitions correctly, you may need to troubleshoot the issue. Here are some troubleshooting steps to follow:
1. Check if your device’s BIOS is set to UEFI or Legacy mode. If it is set to Legacy mode, change it to UEFI mode and try cloning the OEM recovery partitions again.
2. Check if the disk cloning software you are using supports cloning OEM recovery partitions. If it does not, try using a different disk cloning software.
3. Check if the new SSD is compatible with your device. If it is not compatible, try using a different SSD.
4. Check if the BCD information has been affected. If it has, you may need to repair the BCD information using the Windows Recovery Environment.
Conclusion
Cloning OEM recovery partitions is essential when migrating your system to a new and larger SSD. Without cloning the OEM recovery partitions, you may lose the ability to restore your device to its original state. By following the steps outlined in this blog post, you should be able to clone the OEM recovery partitions correctly. If you encounter any issues, you can follow the troubleshooting steps outlined in this post to resolve them.
It sounds like you are trying to clone the OEM recovery partition from your old M2 NVME SSD to the new one and the OEM recovery is no longer functioning on the new SSD. It’s possible that the BCD information has been affected during the cloning process, which could explain why the OEM recovery is no longer functioning on the new SSD.
To properly clone the OEM recovery partitions to the new SSD, you will need to use a specialized tool that is designed to clone these types of partitions. Some options that you might consider include EaseUS Todo Backup, AOMEI Partition Assistant, or Clonezilla. These tools should be able to clone the OEM recovery partitions to the new SSD while preserving the BCD information and other important data.
Before you start the cloning process, it’s important to make sure that both the old and new SSDs are connected to your computer and that you have a reliable backup of your important data. This will ensure that you can recover your system in case something goes wrong during the cloning process.
I hope this information helps! Let me know if you have any other questions.
There are times when cloning or partitioning apps fail to copy the partition type ID and GPT attributes, which can cause some recovery partitions to become “normal” partitions. This issue can be fixed by following the instructions in the article “Setting WinRE (Windows Recovery Environment) Flag On Partitions.” It’s worth noting that this same procedure can also be used to move recovery partitions to a different disk or free up space on an SSD. Just keep in mind that I have not tested this scenario myself.
This procedure is for UEFI boot with GPT disks. To begin, you’ll need to locate the small recovery partition (which is usually around 839MB) next to the Windows partition (C:) and mount it. Dell OS Recovery relies on this partition, so you’ll need to edit a file called \Recovery\Logs\Reload.xml on it. Before proceeding, I recommend backing up all recovery partitions using a program like Clonezilla.
To mount the recovery partition, you’ll need to run the following commands in diskpart:
list disk
select disk X [select the OS disk in question]
uniqueid disk [note down/copy the GUID of the disk, you will need it]
list partition [note down the partition offsets, you might need it later]
list volume
select volume Y [select the recovery volume as stated above]
assign letter=W [choose a drive letter to assign this partition to]
exit
Next, you’ll need to obtain the disk GUID. You can do this by running the following command in the command prompt:
wmic partition get BlockSize, StartingOffset, Name, Index
Using the starting offsets listed, you can determine which partition is the recovery partition you need (it will be the one with the largest gap between it and the Windows partition). If you have trouble figuring out which partition it is, you can calculate the offset in KB, MB, or GB by dividing it by the appropriate power of 1024. Once you’ve identified the correct offset, make note of it.
Warning: Mounting the recovery partition may reveal that it is mostly empty, which is unusual. Some BCD elements may point to non-existent files on this partition (for example, in the Device object ‘Windows Recovery’, there is an element called SdiPath with the value ‘\Recovery\WindowsRE\boot.sdi’). It’s possible that this is an image partition, in which case editing a file with a text editor could corrupt it. To prevent this, it may be necessary to use a disk/sector editor like Sector Edit from BootIce or Runtime’s DiskExplorer for NTFS (which requires a license). Currently, I have not had any issues using Notepad++, but I will update this answer if necessary.
To edit \Recovery\Logs\Reload.xml, you’ll need to mount the recovery partition and obtain the disk GUID and partition offset. You can do this inside Windows by running the following command in the command prompt (running as administrator):
C:\Program Files (x86)\Notepad++\notepad++.exe W:\Recovery\Logs\Reload.xml
Alternatively, you can use Hiren’s Boot PE, which contains everything you need. It’s recommended to use Notepad++ rather than the default Notepad. However, keep in mind that Hiren’s Boot PE may not detect your M.2 NVME SSD in RAID SATA mode, so you’ll need to temporarily set the SATA mode to AHCI in the BIOS.
In the <Disk> tag of the Reload.xml file, replace the offset and guid attributes with the values you obtained earlier. It’s a good idea to convert the guid to lowercase, just in case it is case sensitive. Save the file when you are done.
Next, you’ll need to set the WinRE flag on the recovery partition. This can be done by running the following command in the command prompt:
reagentc /setreimage /path W:\Recovery\WindowsRE /target C:\
This will set the WinRE flag on the recovery partition and point it to the Windows installation on the C: drive.
Finally, you’ll need to update the BCD store to reflect the changes you just made. You can do this by running the following commands in the command prompt:
bcdboot C:\Windows /s W:
bootrec /rebuildbcd
This will update the BCD store and add the Windows installation on the C: drive to the boot list.
After completing these steps, the OEM recovery should be working properly. If you encounter any issues or have any questions, feel free to ask.