Salta al contenuto principale

Boot Drive Locked After Backup

Thread needs solution

I've seen posts similar to this, but not this exact issue.

My PC with Acronis 14 is running the current Win 10. I wanted to clone a HDD from a laptop to another blank drive, so I installed both drives in the PC, setup the clone and started it. After a few minutes, it said that I needed to reboot the machine tgo complete the clone job. I thought this was a little strange since it wasn't cloning the boot/OS drive, but not unheard of, so I allowed it to restart the machine.

The clone workied fine, but when I removed the two extra drives from my PC, I could no  longer boot into Windows. I tried the Windows 10 startup repair, but that failed, then when I tried to reset the system, it said that it couldn't proceed because the drive is locked.

I have taken this OS drive out of that PC and installed it into another computer and all of the files on the drive seem to be in tact, so I am guessing that if I can get the drive unlocked it will boot up like normal. Does anybody know how I can unlock this drive?

jO

0 Users found this helpful

Hello Jason,

Do you have a full disk backup of your Windows 10 system drive? You may need this in order to restore the hidden System Reserved partition that holds the BCD information that has probably been corrupted.

ATIH 2014 is not supported to work with Windows 10 systems despite the fact that you appear to have it working - only 2015 or 2016 are supported for Windows 10 systems.

Cloning will always require a reboot into a dedicated system boot environment using Linux unless you boot directly from Windows PE Rescue Media, this is regardless of which source & target drives are being cloned, as the assumption is that one of the drives is an OS drive and cannot be 'copied' in a normal Windows environment.

See KB document: https://kb.acronis.com/content/45831 for further help with this problem, including the link to the Microsoft guidance for using Bootrec - https://support.microsoft.com/en-us/kb/927392

Thanks for the reply, Steve. I tried all sorts of bootrec, sfc, bcdedit, gparted, etc. today. Nothing worked. Finally, I went into my BIOS (mobo is an Asus Z170-Deluxe) and checked the boot order. When I changed the option from "P3 Samsung SSD" to "Windows Boot Manager (P3 Samsung SSD)", it suddenly boots into Windows fine. I'm not sure why just selecting the drive like normal doesn't work, but this does, so problem solved (I guess)

Hello Jason, that seems to be something that came in with Windows 10 & probably 8 / 8.1 before it, that you need to select Windows Boot Manager rather than the actual drive - it is also more associated with UEFI systems than MBR.

Glad to hear you have got this going again!