Direkt zum Inhalt

This PC/Device needs to be repaired

Thread needs solution

I got this error message booting immediately after a clone operation: “This PC/Device needs to be repaired”.

 

From what I’ve read, this error means the Boot Configuration Data “BCD” file is corrupt.

 

How can this happen during a Clone operation?

 

Computer: HP desktop recently purchased with Win 10 Pro.

Hard Drives: Disk0 = Internal SATA 2TB Intel Optane+1.8TBHDD 17.5; Disk1 = Internal SATA 2TB WD Blue.

Acronis True Image 2020

Bit Locker Off

 

I booted from an ATI 2020 Rescue Disk (USB thumb drive) and performed a clone operation where my “From” disk is my internal primary Disk <0> and my “To” disk is an internal clean single partition Disk <1>.

 

Except during the clone operation, the two disks were never connected at the same time.

 

As soon as the clone operation finished and the PC shut down I disconnected the primary disk so I could test the boot from the cloned drive.  I immediately got this error.  I thought “No Problem, I’ll just go back and reconnect my primary drive.”  To my HORROR it too got the needs repair error message.  I was able to perform an ATI Restore so I’m up and running again.  Thank goodness for ATI backup.

 

Since then I’ve been reading up on how to fix this error but I’m in no mood to put myself in a position where I need to follow those instructions, even to test it.

 

Have any of you experienced this error after a clone?  Any thoughts on when or how the BCD got corrupted?  Any thoughts on what inside the BCD might be corrupted?  Any thoughts on exactly what the word “corrupted” means?  Does Acronis change the BCD or is it Windows?  Any thoughts on how to avoid this error?

 

Additionally, I put the cloned disk into an external USB drive case, plugged it in and deleted the partitions and reformatted the disk.  I then went to shut down my PC using Start>Shutdown and it restarted instead of shutting down.  I tried it again and it restarted again.  I had to run the Shutdown /P /F command to get the PC to actually shut down.  This was weird behavior.  When I started the PC I got the same error again using my primary disk and I had to restore again.  Yikes!

 

I need a simpler solution other than restoring.

 

There must be some type of behavior changing the BCD.  I wish I knew more about it.

 

Needless to say, I won’t be running any more clone operations until I understand what happened.

 

Any suggestions will be greatly appreciated.

 

0 Users found this helpful

Bill, welcome to these public User Forums.

Cloning will make changes to the BCD because that is a part of its purpose in order to try to make the target drive bootable, but there may be other factors involved that can upset those changes.

What BIOS boot mode does your Windows 10 Pro OS use to boot to the desktop?
Is this UEFI / GPT, or is it using Legacy / MBR?

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media for how to check the above.

What BIOS boot mode did you use for the Acronis USB rescue media? 
Was this the same boot mode as used by Windows 10?

For this particular situation, I would recommend not using cloning so as to avoid any changes being made to either of your disk drives, and in particular, the possibility that when you clone from Disk 0 to Disk 1, the BCD is still being written / updated on Disk 0, so was 'missing' when you removed Disk 0 to boot from Disk 1..!

As you already have a full Disk backup of Disk 0, then shutdown the computer fully by holding down the Shift key while clicking on Shutdown (else use the command:  shutdown /s /f /t 0 ).

Remove Disk 0, and replace it with Disk 1 using the same SATA controller cable if possible (so that Disk 1 becomes Disk 0).  Set aside the original Disk 0 disconnected and in a static proof bag or case.

Boot the computer in the correct BIOS boot mode from the Acronis rescue USB media, along with your backup drive connected.

Recover your backup of the original Disk 0 from the backup drive to the new disk 0 drive.

When finished, shutdown, disconnect the backup drive, remove the USB boot media, then try booting normally into Windows 10 with just the new drive installed.

Thanks Steve!

Both Win 10 boot and Rescue Media boot are UEFI.

 

I'm going to follow your advice, abandon disk cloning.  I've already used Recovery a couple of times and it works great.