Cloning - Works fine on first boot - then problems on restart
Hello. I am hoping to get help with a cloning problem. I have a Lenovo Desktop k430 which has been working fine until lately. About 4 weeks ago I had some problems with the C drive and after cleaning the drive, Hardware Sentinel revealed there were sector problems. The problems were corrected by Windows 7 by reallocation of sectors to available areas. I purchased a new 2TB Seagate Drive and tried to use a recent backup and a backup from last April. For some reason the backup(s) which were installed would not boot, When I tried to boot, I only saw a blank screen with a blinking cursor. I tried to correct the situation with a Windows 7 boot disk and Windows failed to automatically correct the situation. I downloaded Neosmart Easy Recovery 7. This program did not resolve the boot problems. either but I believe it added a MBR partition. The original Hard drive has one partition only and when I backed up previously I did not know whether I should check ( MBR 0 ). or not. I finally backed up the drive yesterday to an Older WD 'MY Book drive which I formatted before the backup. When I did the backup yesterday, i validated the backup off the old drive and it was perfect. I also validated the previous backups and they were fine. The problem with the WD MY Book was that I could not reinstall the backup because it was locked and Acronis boot disk could not reveal it. I communicated with Acronis for Technical help and since I was using Acronis 2017, they confined their remarks to the backup situation. I sent my log and everything they wanted. The tech was concerned but only provided information that I already read. The ticket was closed yesterday as I asked about a cloning question and they advised me to purchase Acronis 2019 which I did. Using the 2019 software, I tried to make a bootable disk from the 2019 software but when I tried the computer would not boot from it. I was told to use the Windows 7 boot disk. I used the 2017 Acronis Bootable disk to perform the re-installations.
All of the above has taken weeks of trying this and that to make the new drive bootable. In frustration, I tried cloning the old drive on to the new drive using the 2017 Acronis bootable disk and alas it worked fine on which I used the new Disk. Hard disk Sentinel said the new drive is perfect and100% While booting, I noted that Windows installed a new driver for the hard drive for the new hard drive and asked for a reboot. When I finally did a shutdown and reboot,Windows booted in to whiat I would call a basic safe mode.. large Icons, no drivers to talk about and a non-workable situation. I did not understand what happened at first so I re-cloned the old drive on to the new drive for a 2nd time and again the same situation occurred..I finally realized the problem was (is) the new driver. The old driver seemed to work fine. I checked Disk management this am after cloning for the third time and all is working well. BUT Windows installed the 'new driver' again once booted. How can I prevent the new driver from being installed?? Can I used Disk Management.. I do not want Windows to install a new driver each time I boot the drive.
Any help is appreciated.. Thanks Arnold


- Log in to post comments

Steve, Thank you for your request. The boot system is legacy.
At this moment all seems fine and all ok. I realized after cloning, the computer worked fine. BUT when I tried to reboot the computer it did not recognize the hard drive and advised there was no Windows to boot. The real problem is (was) that when I installed the new Seagate Drive, I used a different model than the previous. The old hard drive model was ST2000M001. The new Seagate Drive is ST2000DM008. Thus at the initial boot, Windows installed a new driver for the new hard drive which apparently did not work on the reboot.. It did not allow me to boot in to the drive.SO I resolved the problem by going on to the old hard drive ( which was still working) and stopped Windows from installing new drivers, re-backed up the drive and installed the new backup version and that worked. The crux of the problem was I used a new and 'better' hard drive and the new installed driver did not work until I prevented Windows 7 from installing a 'new driver'.. The old 'legacy' driver dows work on the new drive.
Acronis tech support adsied the same and sent me this llink
https://support.microsoft.com/en-ca/help/2500967/how-to-stop-windows-7-…
The other problem I had at first was the older backups when restored to the new drive would not boot at all. My old drive has only one partition for the C drive.I was confused when I went to restore and did not check MBR 0 as I thought that meant it was going to add a partition for the boot. When I restored that last time, I checked on restore to include MBR 0 and it worked.
I also downloaded Group Policy editor as I have Windows 7 Home Premium and it did not include GPE., The download I got from the net did not include 'Disk Management' so instead I was able to stop the hard drive driver search through Disk Management itself and confirmed it through the Registry.
All of the above took me weeks to resolve but I learned much through the exercise. I now have Acronis 2019 and have backed up the drive and have the back up bootable DVD. I hope the above scenario will help others .
- Log in to post comments

Arnold, thank you for your update and for sharing your resolution to this issue, glad that all is well now!
- Log in to post comments