Hi eveoryone,

yesterday I have try to install OpenSUSE linux as a second OS for my PC. I have maybe done something wrong, so I have had to recreate the BCD (on primary OS Win 8.1 Pro) using EasyBCD app from second instalation of Widnows. Than I have made 4 disc backups (2 per backup app). Then I have finally installed the linux, but I have not installed its bootloader because there was some error and I thought that Windows loader can correct it for me. That was bad idea. The Win 8.1 OS starts to crashes during loading even if I repeated the step with recreation its BCD via EasyBCD. So I have restored the backup and for some reason I have to start OS first under native IDE mode instead of AHCI (Win 8.1 is runnig on SSD drive).

Now I have found that original restoration points for Win 8.1 was not matched with the drive. I see in the system security tab original drive with correct name and drive letter with directory icon and normally the actual drive with normal icon.

I have issued many time bootrect, bcdboot and bootsect on drive before first BCD recreation via app has been done, but the most significant command options has been always unsuccessful (that is the reason for using EasyBCD). I am almost sure that than I have made one restore point of drive with no problems noticed. So this is probably issue of restoration from disc backup.

The first crash I think is maybe caused by installing linux on HDD drive on ASCI BIOS mode without Win 8.1 bootloader assistaion - from scratch via ODD. The second as I have written is caused by not applied the linux own bootloader.

Please can anyone tell me how to rematch these restore points with the corrent drive?

Thank you a lot.

• Edited by Uzivatel 919 1 hour 16 minutes ago

Hi,

I see in the system security tab original drive with correct name and drive letter with directory icon and normally the actual drive with normal icon.

To be better understanding your issues, we need more details on this, what do you mean by dont match the drive?

Do you mean after disk image back up restoration, the old restore points are in the wrong drive? And please keep reading.

I guess you also cannot see these restore points, because I did same thing on my test machine. These restore points are useless after system image restoration or clone. Because Windows Restore Points are maps of changed sectors on the disk, and they refer to the sectors by absolute location on the disk. If you clone a disk the files are not necessarily restored to the exact same sector locations on the cloned disk as they were on the source disk. When Windows boots, it detects this and deletes the restore points since they now are invalid. You will find an error entry in the Windows System log saying something like "The shadow copies of volume C: were aborted upon detection" when this happens.

As far as I know, the only way that you can preserve the restore points and shadow copies is to create an image of the disk in sector-by-sector mode and then restore that image to the target disk in sector-by-sector mode, which forces the sectors to end up in the same absolute locations on the target disk.

Regards,

D. Wu