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
Did you change the size of your partition C?
Try Startup Repair:
Troubleshoot Startup Problems with Startup Repair Tool in Windows 7
If startup repair doesn't fix it, choose command line and type bootsect /nt60 C:/.
~~~~~~~~~~~~
( http://www.sevenforums.com/crashes-d...tructions.html )
Try Startup Repair:
Troubleshoot Startup Problems with Startup Repair Tool in Windows 7
If startup repair doesn't fix it, choose command line and type bootsect /nt60 C:/.
~~~~~~~~~~~~
( http://www.sevenforums.com/crashes-d...tructions.html )
Hi Cybercore - many thanks for your response.
Can you perhaps explain what the bootsect command does?
Do the symptoms I describe suggest that the new OS volume is somehow linked to the original volume?
Thanks again for your help.
Jules
Can you perhaps explain what the bootsect command does?
Do the symptoms I describe suggest that the new OS volume is somehow linked to the original volume?
Thanks again for your help.
Jules
I understand you resized C (?), created another partition from it, and now you can't boot - correct?
Not quite. I cloned C: onto a new physical drive which was unformated (H).
When I try and boot to C: I get 'autochk program not found'. When I try and boot to H: it appears to use the MBR on that drive, but actually loads the OS on C:. I'm guessing slightly here, but that's what it looks like - C: shows changes made on the desktop, whereas H doesn't, even though H appears to be the active drive in Disk Management.
It looks to me like I need to completely rebuild the boot strucure for the whole machine so that I can then boot into one OS cleanly.
Thanks for your hlep.
Jules
When I try and boot to C: I get 'autochk program not found'. When I try and boot to H: it appears to use the MBR on that drive, but actually loads the OS on C:. I'm guessing slightly here, but that's what it looks like - C: shows changes made on the desktop, whereas H doesn't, even though H appears to be the active drive in Disk Management.
It looks to me like I need to completely rebuild the boot strucure for the whole machine so that I can then boot into one OS cleanly.
Thanks for your hlep.
Jules
See you cloned your C:, not backed up, but cloned. So your MBR was on C:, and now it is the same MBR on 2 partitions.
Hi Cybercore - I suspect you're right.
Is there any way of remedying the situation? Also, why would this mean that I am no longer able to boot into C:?
If I just wipe the new partition (H), will I be back to where I was?
I'm reluctant to do this whilst I can't boot into my original partition, because of the 'autochk program not found' error
Thanks again
Jules
Is there any way of remedying the situation? Also, why would this mean that I am no longer able to boot into C:?
If I just wipe the new partition (H), will I be back to where I was?
I'm reluctant to do this whilst I can't boot into my original partition, because of the 'autochk program not found' error
Thanks again
Jules
First run Startup Repair.
If it doesn't fix, have 7 DVD in drive -> cmd -> sfc /scannow.
If it doesn't fix, have 7 DVD in drive -> cmd -> sfc /scannow.
If none of that works.
Turn off PC and unplug power and data cable to cloned HD.
The main HD may boot then.
If not use this. Bootmgr is missing - Fix
That should get you back into the main HD since it can't boot into the clone.
You will be back where you started before cloning.
You can reformat or reinstall from the main OS.
If you plug in the clone with PC off it will possibly try to boot to clone again.
Then I'll find some tutorials if you need to use a system image using Macrium for your dual system if needed.
For later after we get you back into the main HD and OS if your interested.
Imaging with free Macrium
I asked for some help with getting the cloned drive working.
Mike
Turn off PC and unplug power and data cable to cloned HD.
The main HD may boot then.
If not use this. Bootmgr is missing - Fix
That should get you back into the main HD since it can't boot into the clone.
You will be back where you started before cloning.
You can reformat or reinstall from the main OS.
If you plug in the clone with PC off it will possibly try to boot to clone again.
Then I'll find some tutorials if you need to use a system image using Macrium for your dual system if needed.
For later after we get you back into the main HD and OS if your interested.
Imaging with free Macrium
I asked for some help with getting the cloned drive working.
Mike
Many thanks for the helpful suggestions.
So far, I have run startup repair from the Win7 install DVD, and have run Bootsect and Bootrec.exe with various MBR suffixes as suggested here and elsewhere. None of these processes have made any difference.
The Startup Repair DVD only sees the new Win7 install (H), and although the system boots into this drive ok, it then appears to run the actual OS from drive C. I've confirmed this by umounting C whilst booted into drive by running chkdsk, which causes all desktop icons disappear, and all programs to become unavailable. I guess it's booting into H but because the MBR was copied, it's referencing C for all OS files and data.
I'll try the scannow command now and will try disconnecting the drive tomorrow and see if Windows is able to find the old system volume and boot into that, if it can't I guess I'm stuffed. Your offer of help setting up a dual system is appreciated Hopalong X. At this stage I'd just like to get one partition working properly and go from there.
Thanks again.
Jules
So far, I have run startup repair from the Win7 install DVD, and have run Bootsect and Bootrec.exe with various MBR suffixes as suggested here and elsewhere. None of these processes have made any difference.
The Startup Repair DVD only sees the new Win7 install (H), and although the system boots into this drive ok, it then appears to run the actual OS from drive C. I've confirmed this by umounting C whilst booted into drive by running chkdsk, which causes all desktop icons disappear, and all programs to become unavailable. I guess it's booting into H but because the MBR was copied, it's referencing C for all OS files and data.
I'll try the scannow command now and will try disconnecting the drive tomorrow and see if Windows is able to find the old system volume and boot into that, if it can't I guess I'm stuffed. Your offer of help setting up a dual system is appreciated Hopalong X. At this stage I'd just like to get one partition working properly and go from there.
Thanks again.
Jules
�� Quote: Originally Posted by Trailerman 
Many thanks for the helpful suggestions.
So far, I have run startup repair from the Win7 install DVD, and have run Bootsect and Bootrec.exe with various MBR suffixes as suggested here and elsewhere. None of these processes have made any difference.
The Startup Repair DVD only sees the new Win7 install (H), and although the system boots into this drive ok, it then appears to run the actual OS from drive C. I've confirmed this by umounting C whilst booted into drive by running chkdsk, which causes all desktop icons disappear, and all programs to become unavailable. I guess it's booting into H but because the MBR was copied, it's referencing C for all OS files and data.
I'll try the scannow command now and will try disconnecting the drive tomorrow and see if Windows is able to find the old system volume and boot into that, if it can't I guess I'm stuffed. Your offer of help setting up a dual system is appreciated Hopalong X. At this stage I'd just like to get one partition working properly and go from there.
Thanks again.
Jules
So far, I have run startup repair from the Win7 install DVD, and have run Bootsect and Bootrec.exe with various MBR suffixes as suggested here and elsewhere. None of these processes have made any difference.
The Startup Repair DVD only sees the new Win7 install (H), and although the system boots into this drive ok, it then appears to run the actual OS from drive C. I've confirmed this by umounting C whilst booted into drive by running chkdsk, which causes all desktop icons disappear, and all programs to become unavailable. I guess it's booting into H but because the MBR was copied, it's referencing C for all OS files and data.
I'll try the scannow command now and will try disconnecting the drive tomorrow and see if Windows is able to find the old system volume and boot into that, if it can't I guess I'm stuffed. Your offer of help setting up a dual system is appreciated Hopalong X. At this stage I'd just like to get one partition working properly and go from there.
Thanks again.
Jules
That I thought was your goal at this point.
Sorry I missed the 'Bootmanager is missing fix' you referenced on first reading. Is that what you're referring to, or do you mean I should go stright to the hardware disconnection approach?
Sorry if I'm being dense here, and thanks again.
Jules
Sorry if I'm being dense here, and thanks again.
Jules
Disconnect the cloned drive. PC offf!!!!
Restart it may boot properly into main OS.
If not then do the boot is missing fix .
You already tried it with both HD's running and it only boots the clone.
This will not get the clone working right necessarily but it will get you back into your main OS and HD.
We can go from there on the cloned drive.
I hopefully have some help coming to assist with that.
Mike
Help coming I think.
Restart it may boot properly into main OS.
If not then do the boot is missing fix .
You already tried it with both HD's running and it only boots the clone.
This will not get the clone working right necessarily but it will get you back into your main OS and HD.
We can go from there on the cloned drive.
I hopefully have some help coming to assist with that.
Mike
Help coming I think.
Please post back a screenshot of your maximized full Disk Management drive map with listings, with all drives attached. Use Snipping Tool in Start Menu.
If you wrote the MBR to the new clone you should be able to boot either via the BIOS boot order or BIOS Boot Menu key. Test this.
Bootsect and bootrec are automated in Win7 Startup Repair. If either Win7 is not marked System now, mark it Active and run Startup Repair x3 while the other drives are unplugged.
Startup Repair - Run 3 Separate Times
Partition - Mark as Active
If you have any questions or are unsure wait until we read the screenshot. There may be other complications which will become clear once we see it. Going surfing til 7 pm PST.
If you wrote the MBR to the new clone you should be able to boot either via the BIOS boot order or BIOS Boot Menu key. Test this.
Bootsect and bootrec are automated in Win7 Startup Repair. If either Win7 is not marked System now, mark it Active and run Startup Repair x3 while the other drives are unplugged.
Startup Repair - Run 3 Separate Times
Partition - Mark as Active
If you have any questions or are unsure wait until we read the screenshot. There may be other complications which will become clear once we see it. Going surfing til 7 pm PST.
I removed all drives except the original Windows 7 drive and booted up.
As before, it got to the point where I would normally get the login screen and then I got the 'autochk program not found - skipping autocheck' message followed by a blue screen.
I'm trying the boot is missing fix now, but it doesn't sound like the MBR is missing on this drive.
Jules
As before, it got to the point where I would normally get the login screen and then I got the 'autochk program not found - skipping autocheck' message followed by a blue screen.
I'm trying the boot is missing fix now, but it doesn't sound like the MBR is missing on this drive.
Jules
Sorry Greg - missed you post.
Is it ok to try and troubleshoot this with just the single drive in place? Seems to make more sense. I'll run startup repair on this drive and see if that helps. Maybe previous runs were actually runnig it on the clone ...
Jules
Is it ok to try and troubleshoot this with just the single drive in place? Seems to make more sense. I'll run startup repair on this drive and see if that helps. Maybe previous runs were actually runnig it on the clone ...
Jules
PS. Sorry - should have mentioned this before, but I also had an old WinXp partition on the system, again on a separate drive. Not been used for ages, but maybe it's MBR was also contributing to the mess. Now removed.
Greg
He is following my instructions before you got here.
Let him know what you want and I'll just watch.
Just got the surfing reference. Go.
Trailerman can be working on your posted cures.
Mike
He is following my instructions before you got here.
Let him know what you want and I'll just watch.
Just got the surfing reference. Go.
Trailerman can be working on your posted cures.
Mike
Trailer
Try Gregs suggestion Startup Repair - Run 3 Separate Times on the single HD you have operating.
Mike
Greg will be back or someone else may give us a hand by then.
Try Gregs suggestion Startup Repair - Run 3 Separate Times on the single HD you have operating.
Mike
Greg will be back or someone else may give us a hand by then.
OK - Startup Repair sees the drive fine. First run through went fine - found some boot related stuff and did it's thing.
Second run through I get:
Startup Repair cannot repair this computer automatically.
Details show:
Problem event name : StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: Unknown
Problem Signature 04: 157
Problem Signature 05: ExternalMedia
Problem Signature 06: 1
Problem Signature 07: BadDriver
etc.etc
Will rerun and then see where we are with booting.
Jules
PS. Massively appreciate all the help.
Second run through I get:
Startup Repair cannot repair this computer automatically.
Details show:
Problem event name : StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: Unknown
Problem Signature 04: 157
Problem Signature 05: ExternalMedia
Problem Signature 06: 1
Problem Signature 07: BadDriver
etc.etc
Will rerun and then see where we are with booting.
Jules
PS. Massively appreciate all the help.
It would really help to see a snip of disk management.
In the Windows start menu right click computer and click manage, in the left pane of the "Computer Management" window that opens click disk management and post a snip of that, it should look similar to this.
How to Upload and Post a Screenshot and File in Seven Forums
In the Windows start menu right click computer and click manage, in the left pane of the "Computer Management" window that opens click disk management and post a snip of that, it should look similar to this.
How to Upload and Post a Screenshot and File in Seven Forums
Barefoot
It won't boot.
It won't boot.
Maybe that'll teach me to skim a long thread to help.
Your suggestion to try to only boot the original HDD sounded the best idea, did he try that?
Your suggestion to try to only boot the original HDD sounded the best idea, did he try that?
Bare Foot Kid
More than happy to post a snap of Disk Manager, but only have one drive in the system at the moment, which only has one partition on it (original Windows 7).
Plus, despite running all the suggested fixes I unfortunately still can't boot into it - no luck: after 3 Startup Repairs I'm still getting:
'autochk program not found - skipping autocheck'
I'm crashing for the night (I'm in the UK). Back in a few hours to tear my last few remaining hairs out.
Thanks again
Jules
More than happy to post a snap of Disk Manager, but only have one drive in the system at the moment, which only has one partition on it (original Windows 7).
Plus, despite running all the suggested fixes I unfortunately still can't boot into it - no luck: after 3 Startup Repairs I'm still getting:
'autochk program not found - skipping autocheck'
I'm crashing for the night (I'm in the UK). Back in a few hours to tear my last few remaining hairs out.
Thanks again
Jules
He is trying to get the main HD booted so the clone is disconnected.
Mike
Mike
Hello again Jules, we'll be here; just come back to this same thread so we'll know where to start.
Did you mark the Win7 partitions Active first as suggested earlier?
Without the Disk Management screenshot, you'll need to plug in a Win7 HD, mark it's partition Active using Diskpart from DVD or Repair CD Command Line, then run Startup Repair repeatedly.
Startup Repair - Run 3 Separate Times
Start by booting the Install DVD or Repair CD, press Shift F10 at first screen to open a Command Line, then use these Diskpart commands given here: Mark as Active
Once you bring the Win7 partition into focus you can "Detail Partition" to see if it's already marked Active, or just write "active" to do it again. Then run the Repair.
When one starts up, do the next one with the first one unplugged.
Once you get one Win7 HD started up, plug the others in and post back a screenshot of your full Disk mgmt drive map with listings. They may already be able to individuall boot via BIOS Boot Order or BIOS one-time Boot Screen.
Without the Disk Management screenshot, you'll need to plug in a Win7 HD, mark it's partition Active using Diskpart from DVD or Repair CD Command Line, then run Startup Repair repeatedly.
Startup Repair - Run 3 Separate Times
Start by booting the Install DVD or Repair CD, press Shift F10 at first screen to open a Command Line, then use these Diskpart commands given here: Mark as Active
Once you bring the Win7 partition into focus you can "Detail Partition" to see if it's already marked Active, or just write "active" to do it again. Then run the Repair.
When one starts up, do the next one with the first one unplugged.
Once you get one Win7 HD started up, plug the others in and post back a screenshot of your full Disk mgmt drive map with listings. They may already be able to individuall boot via BIOS Boot Order or BIOS one-time Boot Screen.
Greg
OP ran the Startup Repair - Run 3 Separate Times
Still wouldn't boot in to Windows.
OP ran the Startup Repair - Run 3 Separate Times
Still wouldn't boot in to Windows.
Quote:
Plus, despite running all the suggested fixes I unfortunately still can't boot into it - no luck: after 3 Startup Repairs I'm still getting:
'autochk program not found - skipping autocheck'
I'm crashing for the night (I'm in the UK). Back in a few hours to tear my last few remaining hairs out.
Thanks again
'autochk program not found - skipping autocheck'
I'm crashing for the night (I'm in the UK). Back in a few hours to tear my last few remaining hairs out.
Thanks again
Hi Mike -
Did he mark the partitions active first? I clearly stated that had to be done first and provided the link which shows how to do it from the Install DVD or Repair CD Command line.
Ted was told that OP couldn't boot to post the screenshot but in Post #1 he says he could boot into one Win7, so a screenshot with all disks connected would have allowed us to sort it out quickly.
I've just asked again. I'll ask again later if it will help. There are other steps if these fail but knowing if the steps already given were completed or providing a screenshot we can't proceed.
Did he mark the partitions active first? I clearly stated that had to be done first and provided the link which shows how to do it from the Install DVD or Repair CD Command line.
Ted was told that OP couldn't boot to post the screenshot but in Post #1 he says he could boot into one Win7, so a screenshot with all disks connected would have allowed us to sort it out quickly.
I've just asked again. I'll ask again later if it will help. There are other steps if these fail but knowing if the steps already given were completed or providing a screenshot we can't proceed.
�� Quote: Originally Posted by gregrocker Did you mark the Win7 partitions Active first as suggested earlier?
Without the Disk Management screenshot, you'll need to plug in a Win7 HD, mark it's partition Active using Diskpart from DVD or Repair CD Command Line, then run Startup Repair repeatedly.
Startup Repair - Run 3 Separate Times
Start by booting the Install DVD or Repair CD, press Shift F10 at first screen to open a Command Line, then use these Diskpart commands given here: Mark as Active
Once you bring the Win7 partition into focus you can "Detail Partition" to see if it's already marked Active, or just write "active" to do it again. Then run the Repair.
When one starts up, do the next one with the first one unplugged.
Once you get one Win7 HD started up, plug the others in and post back a screenshot of your full Disk mgmt drive map with listings. They may already be able to individuall boot via BIOS Boot Order or BIOS one-time Boot Screen.
Without the Disk Management screenshot, you'll need to plug in a Win7 HD, mark it's partition Active using Diskpart from DVD or Repair CD Command Line, then run Startup Repair repeatedly.
Startup Repair - Run 3 Separate Times
Start by booting the Install DVD or Repair CD, press Shift F10 at first screen to open a Command Line, then use these Diskpart commands given here: Mark as Active
Once you bring the Win7 partition into focus you can "Detail Partition" to see if it's already marked Active, or just write "active" to do it again. Then run the Repair.
When one starts up, do the next one with the first one unplugged.
Once you get one Win7 HD started up, plug the others in and post back a screenshot of your full Disk mgmt drive map with listings. They may already be able to individuall boot via BIOS Boot Order or BIOS one-time Boot Screen.
I'm just going through the first stage of your fix - marking the OS partition Active. I've done that, and have also checked using Detail Partition, but I'm not seeing an active flag at all - can you tell me where/how it would be marked active when I detail it? It does have an asterisk in the far left of the list, but no mention of active anywhere else.
I will then re-run the startup repair 3 times again, and see where that leaves us. As you probably saw, last time I did that, the first run was fine, the second/third found driver errors, but I will retry.
Sorry if this process has been more complicated than it should have been - I'll take full responsibility for not being systematic. I'm now down to one drive and will stick with tests on this until I get this OS up and running, then move from there.
Jules
TRAILERMEN Home - Film, Commercial, Trailer, Game Music and TV Composers
First run through of Startup Repair I get the same issue as before:
Problem event name : StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: Unknown
Problem Signature 04: 157
Problem Signature 05: ExternalMedia
Problem Signature 06: 1
Problem Signature 07: BadDriver
When I check the Startup Repair log, all tests completed successfully (including Boot status etc.) except for:
Root Cause Found:
------------------
A recent driver installation or upgrade may be preventing the system from starting.
Repair action: System files integrity check and repair
Result: Failed. Error code = 0x57
I'll try and rerun after reboot and will then try the 'bootmgr is missing' fix mentioned previously, unless I should try asomething else. I'm starting to wonder if, on this particular disk the issue might not be boot/MBR related, but I'm no expert.
Jules
Problem event name : StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: Unknown
Problem Signature 04: 157
Problem Signature 05: ExternalMedia
Problem Signature 06: 1
Problem Signature 07: BadDriver
When I check the Startup Repair log, all tests completed successfully (including Boot status etc.) except for:
Root Cause Found:
------------------
A recent driver installation or upgrade may be preventing the system from starting.
Repair action: System files integrity check and repair
Result: Failed. Error code = 0x57
I'll try and rerun after reboot and will then try the 'bootmgr is missing' fix mentioned previously, unless I should try asomething else. I'm starting to wonder if, on this particular disk the issue might not be boot/MBR related, but I'm no expert.
Jules
OK - after 2nd and 3rd run throughs of Startup Repair, it tells me Startup Repair could not detect a problem.
However, when I then try and boot into Windows the situation is exactly as before: I get the Windows logo, short wait and where I would normally get my login screen I get:
'autochk program not found - skipping autocheck'
Followed by a blue screen.
Will try the bootmanager is missing fix, and then perhaps a system restore from the Windows boot page, I'll also try booting in safe mode, but I doubt any of these things will make a difference.
Wondering if I should give up on this volume for now, and see if I can get my clone to work properly on its own.
Jules
However, when I then try and boot into Windows the situation is exactly as before: I get the Windows logo, short wait and where I would normally get my login screen I get:
'autochk program not found - skipping autocheck'
Followed by a blue screen.
Will try the bootmanager is missing fix, and then perhaps a system restore from the Windows boot page, I'll also try booting in safe mode, but I doubt any of these things will make a difference.
Wondering if I should give up on this volume for now, and see if I can get my clone to work properly on its own.
Jules
If you can get to safe mode see what this turns up, sometime if it funds integrity errors it takes a couple runs to fix them all.
How to Repair Windows 7 System Files with System File Checker
How to Repair Windows 7 System Files with System File Checker
Thanks Bare Foot
A couple of things:
1. When I run Bootrec /RebuildBcd, it says:
'Total identified windows installations: 0'
Does this mean it's still not seeing my Windows volume propery?
2. When I run sfc /scannow (using the command prompt from the recovery environment), I get:
'There is a system repair pending which requires a reboot ....'
And the same message reappears after each reboot. Should I keep running it?
Thanks again
Jules
A couple of things:
1. When I run Bootrec /RebuildBcd, it says:
'Total identified windows installations: 0'
Does this mean it's still not seeing my Windows volume propery?
2. When I run sfc /scannow (using the command prompt from the recovery environment), I get:
'There is a system repair pending which requires a reboot ....'
And the same message reappears after each reboot. Should I keep running it?
Thanks again
Jules
No I don't think the sfc is helping; I'm at a loss for now and have to go to work, be back later.
No worries Bare Foot - appreciate all your help.
Safe mode doesn't help - same blue screen, with classpnp.sys the last thing on screen. 'Last known good configuration' gives me the same autochk error.
Time to try the other disk I guess.
Jules
Safe mode doesn't help - same blue screen, with classpnp.sys the last thing on screen. 'Last known good configuration' gives me the same autochk error.
Time to try the other disk I guess.
Jules
I removed my original Windows 7 drive and replaced it with the drive which has the clone on it.
After running Startup Repair 3 times I was able to boot into Windows (prior to that I got a Boot mgr missing error). However, it looks like my Windows 7 clone volume is corrupt. I get 'preparing desktop' for an age, and then a blank blue desktop with no taskbar and no icons. Maybe Norton's 'copy disk' function doesn't create a proper bootable OS volume.
I suppose I'm pretty much hosed, but if anybody thought it was worth me trying to clone my original Windows volume again, to replace the new volume which is corrupt but does at least boot, it would save me about 4 days of installation work. Then again, maybe the original volume is broken too.
None of it makes much sense to my addled brain.
Thanks for any help.
Jules
After running Startup Repair 3 times I was able to boot into Windows (prior to that I got a Boot mgr missing error). However, it looks like my Windows 7 clone volume is corrupt. I get 'preparing desktop' for an age, and then a blank blue desktop with no taskbar and no icons. Maybe Norton's 'copy disk' function doesn't create a proper bootable OS volume.
I suppose I'm pretty much hosed, but if anybody thought it was worth me trying to clone my original Windows volume again, to replace the new volume which is corrupt but does at least boot, it would save me about 4 days of installation work. Then again, maybe the original volume is broken too.
None of it makes much sense to my addled brain.
Thanks for any help.
Jules
Hold on - looks like the new volume has called itself Drive H - that's probably why it's not working.
Is there an easy way to change the drive letter back to C in the recovery environment?
Thanks
Jules
Is there an easy way to change the drive letter back to C in the recovery environment?
Thanks
Jules
Mmm ... used diskpart in the startup recovery environment and it was already set to C, yet when it boots into windows it's set to H. So I reset it using 'assign letter=' but it's still booting up as H.
Also tried changing it from the command prompt which I can just about get to in my dodgy windows volume, but it won't let me change drive letters on the current boot volume.
Please forgive my ongoing ramblings.
Jules
Also tried changing it from the command prompt which I can just about get to in my dodgy windows volume, but it won't let me change drive letters on the current boot volume.
Please forgive my ongoing ramblings.
Jules
OK - found a registry hack which changed Drive H to Drive C. Windows on this cloned volume now appears to boot correctly. Not totally confident about how robust it is as an OS but will try and give it a spin.
Now need to replace my other drives and make sure this doesn't screw up the boot sequence. Presumably if I leave the other drives out of the BIOS boot list for now, I should be safe. Feel like I'm in partial solution wilderness, but I guess a seemingly working clone is better than nothing at all.
Jules
PS. Any tips on absolute failsafe cloneing of the OS volume, to use as an alternate boot partition?
Now need to replace my other drives and make sure this doesn't screw up the boot sequence. Presumably if I leave the other drives out of the BIOS boot list for now, I should be safe. Feel like I'm in partial solution wilderness, but I guess a seemingly working clone is better than nothing at all.
Jules
PS. Any tips on absolute failsafe cloneing of the OS volume, to use as an alternate boot partition?
OK - all drives are now back in the machine. Cloned OS volume seems to be running fine from what I can tell.
Below is a screen-grab of my Disk Management window, as requested previously:
- Drive C is my cloned OS volume which I'm booting into.
- Drive Z is my original Windows 7 volume, which I can no longer boot into because of the autochk errors listed ad nauseam above
- Drive L is my old Windows XP volume which I no longer use.
Currently no dual booting is enabled - the system boots into drive C by default.
If anybody had any advice on how to reliably clone Drive C, into the unallocated space on Disk 0 (or even replace the old Win7 volume), and set things up to safely dual-boot I'd be hugely grateful. I'm still unclear on whether the autochk error which prevents me from booting into that volume is a boot issue, or something at an OS level, so I could do with some guidance on how to make that partition safely bootable again. I still need a second Windows 7 partition for some software testing I've been asked to do, but I need to be sure I can create a clone and not have the boot issues detailed in this thread.
Thanks again to all for the help.
Jules
Below is a screen-grab of my Disk Management window, as requested previously:
- Drive C is my cloned OS volume which I'm booting into.
- Drive Z is my original Windows 7 volume, which I can no longer boot into because of the autochk errors listed ad nauseam above
- Drive L is my old Windows XP volume which I no longer use.
Currently no dual booting is enabled - the system boots into drive C by default.
If anybody had any advice on how to reliably clone Drive C, into the unallocated space on Disk 0 (or even replace the old Win7 volume), and set things up to safely dual-boot I'd be hugely grateful. I'm still unclear on whether the autochk error which prevents me from booting into that volume is a boot issue, or something at an OS level, so I could do with some guidance on how to make that partition safely bootable again. I still need a second Windows 7 partition for some software testing I've been asked to do, but I need to be sure I can create a clone and not have the boot issues detailed in this thread.
Thanks again to all for the help.
Jules
I don't have time to think right now, have alook at this one.
Copy & Paste - in Windows Recovery Console
Though you could safely move stuff from old to new with this one in Windows Explorer.
Context Menu - Add Copy To Folder and Move To Folder
Copy & Paste - in Windows Recovery Console
Though you could safely move stuff from old to new with this one in Windows Explorer.
Context Menu - Add Copy To Folder and Move To Folder
Thanks Bare Foot - no hurry on this one as I at least have a working system for now.
Out of interest, are you saying that you can create a complete clone of an OS using copy and paste in the recovery console? I would have thought you'd need something more specialist for this kind of operation, like Acronis or whatever Drive Image became.
I'll try and look into it further myslef. I just want to make sure I avoid the issues I've had this time around.
Jules
Out of interest, are you saying that you can create a complete clone of an OS using copy and paste in the recovery console? I would have thought you'd need something more specialist for this kind of operation, like Acronis or whatever Drive Image became.
I'll try and look into it further myslef. I just want to make sure I avoid the issues I've had this time around.
Jules
Hello Jules, no those were to recover data from the old HDD if needed.
You really ought to have a look at this, you can't beat the price.
You really ought to have a look at this, you can't beat the price.
Partition Manager 11 Personal
Quote:Advanced Backup FeaturesCreate backup images without leaving Windows with Paragon Hot Backup� technology.
Restore system and data even from bare-metal state.
Restore partition with resize.
Restore separate files and folders.
Power Shield� technology - resumes critical partitioning operations after a power failure.
Use Paragon Rescue CD to change back drive letters which slip during cloning or repair: Moving Win7 Partition to Another Drive
If you have any WD or Seagate HD's involved then you can use their free Acronis cloning apps which are the best. Find them on the support Downloads webpage for your WD/Seagate or we have links. Ifnnot, us free Macrium Reflect to save externally an image and reimage onto the target HD. Then boot via BIOS boot order or BIOS Boot Menu key which is the preferred method rather than interlocking HD's using Windows dual boot manager.
As I stated earlier all bootrec and bootsect commands are automated in Win7 Startup Repair so it is the random commands run which likely borked the OS.
Does an installation still appear to repair when you boot into Recovery console? If so, it should repair. If not, then it is sometimes useful to then run bootrec /fixboot and bootrec /fixmbr to goose them to be seen by Repair.
If you have any WD or Seagate HD's involved then you can use their free Acronis cloning apps which are the best. Find them on the support Downloads webpage for your WD/Seagate or we have links. Ifnnot, us free Macrium Reflect to save externally an image and reimage onto the target HD. Then boot via BIOS boot order or BIOS Boot Menu key which is the preferred method rather than interlocking HD's using Windows dual boot manager.
As I stated earlier all bootrec and bootsect commands are automated in Win7 Startup Repair so it is the random commands run which likely borked the OS.
Does an installation still appear to repair when you boot into Recovery console? If so, it should repair. If not, then it is sometimes useful to then run bootrec /fixboot and bootrec /fixmbr to goose them to be seen by Repair.
Không có nhận xét nào:
Đăng nhận xét