Recovery fails after synching
Hello
I have created a backup of an SSD drive that contains 6 volumes including the main partition that had Windows 10 Pro on it. The SSD was only 128GB and I purchased a Samsung one to replace it (both are NVMe, M.2 drives). I created a backup of the PC using True Image 2019 to a USB drive, replaced the disk and installed basic windows 10 on it. I booted from the USB and selected recovery and marked the original 128GB SSD drive and selected that it should install on top of the 512GB installed drive. The process works fine, going through 8 steps (step 4, 5, 6 and 7 at least say "recovering partition sector by sector") and it gets to the end. Eventually it says it got to step 8 "updating the MBR" and then it says it is synching the OS. After that, it just sends a message that states that the recover operation failed.
The log says format size error and resize is impossible.
If I boot with a bootable USB I see the files and partitions, but it won't boot. If I try to boot it says it can't find a device that is needed or something like that.
Can anyone help? Thanks in advance.


- Log in to post comments
In reply to Carlos, welcome to these… by truwrikodrorow…

Thank you Steve. Unfortunately the Windows disk that was backed up and that I am trying to recover is the one that would have the original backup log. But I did do a verification of the restore before and it said it was successful. What do I need to do to save the recovery log using the bootable media option? The log I see using the button on the left menu just showed like I said the errors that it mentioned. But nothing specific.
How can I check what the recovery media boot mode is?
Thanks again. Sorry about all the questions. I had hoped that this would be a simple process.
- Log in to post comments

Carlos, see screen image for saving the log when using the Rescue Media (right-click for the menu).
- Log in to post comments

Thanks Steve. Today I checked both BIOS modes (PC and recovery media) and both were using UEFI. I tried one more time to restore (from recovery boot media) and this time I made sure I was looking at it the whole time and moving the mouse around the whole time. This time it stated that the recovery was successful.
I proceeded to reboot, but the machine still would not boot. However, this time, unlike the others, I was able to boot into SAFE MODE and saw that the auto recover from windows was stating that the booloader.dll was corrupt. The actual location that the log was pointing at (the path contained a folder named CUSTOM on the UEFI folder) that did not exist.
Browsing around on the web I found out that one of the ways to correct this error was from SAFE MODE to run the windows update troubleshooter. I do not know what that did, but afterwards the machine now boots without a problem.
Thanks again for all your help and for the wonderful software.
- Log in to post comments

Carlos, thank you for the update and sharing the information of how you resolved this issue which will be of value for other users.
- Log in to post comments