Trailerman
New Member
Hi, new to the forum and wondered if I could beg some help.
Yesterday I create a clone of my Windows 7 partition for beta testing, using Norton Ghost to copy my existing Windows 7 partition onto a completely new and unformatted drive. Everything ran fine. I may have also ticked the box which instructed Ghost to copy the MBR to the new drive (I don't recall for sure), but for some reason I now have a completely messed up boot situation which I desperately need to try and resolve.
Basically, after I added the newly created Windows 7 partition to the BCD (using EasyBCD) I tried a reboot, and selected the old, original Windows 7 partition to boot into. The system got to the point where I would normally expect the login screen to appear, and I got a black screen with the error:
"autochk program not found, skipping autocheck"
Followed by a blue screen. This happened everytime I tried to boot into the old partition. As far as I was aware, nothing on this drive should have been changed, this is my original Windows 7 partition.
So, I rebooted and tried to boot into the newly created Windows 7 partition - this worked fine, except that, according to Explorer, I'd actually booted into my original Windows 7 partition! I could see that changes I was making on the desktop were appearing in my old system drive (Drive C) and not in the new one (Drive H). When I checked in Disk Manager, Drive H (the new partition) appears to be the active drive - it has 'Boot, Page File, Active, Crash Dump etc.' visible in the disk management GUI for that partition, but no changes are being made to that drive.
So, bottom line, I seem to have arrived at a situation where booting into my old partition doesn't work - I get the autochk error. Booting into the new partition seems to perhaps be using the MBR on the new drive, but actually loading the old OS. I can't delete either volume because they appear to be mutually dependant, and I can't find a way to straighten things out.
I've tried using the Windows 7 Startup Recovery, but this just results in only the new partition being bootable, which in turn appears to actually load the old OS, as described above.
Is there any way of fixing both MBR's on both drives and whatever else needs fixing, on both drives, so that I can at the very least boot into my original partition and delete the newly created one?
Sorry if the explanation above is confusing - I'm not sure I totally understand the situation myself.
Thanks in advance for any help.
Jules
Yesterday I create a clone of my Windows 7 partition for beta testing, using Norton Ghost to copy my existing Windows 7 partition onto a completely new and unformatted drive. Everything ran fine. I may have also ticked the box which instructed Ghost to copy the MBR to the new drive (I don't recall for sure), but for some reason I now have a completely messed up boot situation which I desperately need to try and resolve.
Basically, after I added the newly created Windows 7 partition to the BCD (using EasyBCD) I tried a reboot, and selected the old, original Windows 7 partition to boot into. The system got to the point where I would normally expect the login screen to appear, and I got a black screen with the error:
"autochk program not found, skipping autocheck"
Followed by a blue screen. This happened everytime I tried to boot into the old partition. As far as I was aware, nothing on this drive should have been changed, this is my original Windows 7 partition.
So, I rebooted and tried to boot into the newly created Windows 7 partition - this worked fine, except that, according to Explorer, I'd actually booted into my original Windows 7 partition! I could see that changes I was making on the desktop were appearing in my old system drive (Drive C) and not in the new one (Drive H). When I checked in Disk Manager, Drive H (the new partition) appears to be the active drive - it has 'Boot, Page File, Active, Crash Dump etc.' visible in the disk management GUI for that partition, but no changes are being made to that drive.
So, bottom line, I seem to have arrived at a situation where booting into my old partition doesn't work - I get the autochk error. Booting into the new partition seems to perhaps be using the MBR on the new drive, but actually loading the old OS. I can't delete either volume because they appear to be mutually dependant, and I can't find a way to straighten things out.
I've tried using the Windows 7 Startup Recovery, but this just results in only the new partition being bootable, which in turn appears to actually load the old OS, as described above.
Is there any way of fixing both MBR's on both drives and whatever else needs fixing, on both drives, so that I can at the very least boot into my original partition and delete the newly created one?
Sorry if the explanation above is confusing - I'm not sure I totally understand the situation myself.
Thanks in advance for any help.
Jules
