Salta al contenuto principale

Bootmgr missing after restore

Thread needs solution

Does a chkdsk c: /f show no errors?

Was somthing else on the SSD before you installed Windows 7 to it? You mentioned in the first post that you got an NTLDR error.

If there was anything on it before it was what shipped with the ssd...which should have been nothing.

hmmm intersting, It made a correction, it discovered free space marked as allocated in the mft bitmap, and it made corrections. other than that i think it was fine.
the last thing it said was 'failed to transfer logged messages to the event log with satus 50'.

When you boot the DVD and it finds Windows 7, does it say anything is wrong? Does it offer to fix anything?

Is the SSD drive using the latest firmware available for it?

Did you try installing Windows 7 to the SSD before restoring the image? Just curious if a standard install would work.

When you have tried to boot the SSD and get the error, are any other drives connected (USB drives, flashdrive, etc.)? Does the other DVD drive have a disc in it?

It didnt try and fix anything in repair this time, and the firmware for the ssd im not sure since I just installed it. That is a possibility I can look into. I did not try installing windows on it before the restore. There are no other drives at all connected right now and the other dvd drive is empty.
There are some usb devices connected though, I have a 4 port usb hub connected with a headset connected to it as well as a wireless keyboard receiver. Not too much else is connected.

In searching the web, there appears to be some drives (Intel, mostly) that had/have firmware issues with booting Windows 7. What brand and model is your SSD?

If you don't mind having to restore your image again, you could try doing a standard Windows 7 install to the SSD. If you do, erase the existing partition in the installer and create a new one.

Do you know which mode the drive controller is using (AHCI, IDE Compatible, etc.)? You might try changing it in the BIOS and seeing if it makes a difference.

the drive is a kingston. If I cant get this to work I may as well forgo using the image and just do a fresh windows install and install everything on my own and not worry about bothering with acronis. Im pretty sure the mode is achi. Which should I change it to?

WOA! switched to achi and it started to boot windows. but then didnt make it all the way. haha.

Try IDE, IDE Compatible, Standard, or whatever any other non-RAID, non-AHCI setting is.

I'm really running out of ideas. If a clean install of Windows 7 doesn't boot, then the problem is deeper than TI and just fixing the booting. All the files are there and the error message means that the MBR is calling the boot sector (the error message is in the boot sector). The boot sector code just isn't correctly finding the bootmgr file.

If a clean install does boot properly, then the restore may also work at that point. The booting files would need to be moved back and repaired again, though.

Its getting a blue screen during windows startup now but at least its starting up windows or trying too

well, the problem with the ssd is that things are going to fast for me to actually follow them. So I was lucky to actually see the blue screen. The first time I didnt even see it. now that Its actually trying to boot im going to go back and see if the windows 7 disk startup repair will work.

The BSOD is probably because the image doesn't have the AHCI drivers installed.

Perhaps the SSD requires being run in AHCI mode. At least it's finding bootmgr now.

Try pressing F8 to get the Windows menu and see if you can start it in Safe Mode.

A startup repair won't help. That part is working fine now as Windows is booting. Try Safe Mode next.

On the Safe Mode menu, there's an option to turn off the automatic reboot on a BSOD. This will allow you to see the error message and code.

Before I got your message I had started an attempted startup recovery. Its attempting repairs right now, and taking longer than Im used to but once its done I'll go ahead and do that.

You could try doing a Repair/Upgrade install of Windows 7. It should be able to install the correct drivers. Otherwise, you'd need to use UR or some other method.

It should be on the F8 menu.

It's the Disable automatic restart on system failure option.

I'll try the repair upgrade install of windows 7 next, first I want to see what the BSOD is. Where is the setting to prevent auto reboot...bios?

It boots up so fast its hard to get to the f8 menu. I only get the safe mode menu after an unsuccessful startup. Can I get there from that menu?

I think it's on that menu too.

I usually just start pressing F8 over and over as soon as the BIOS screen passes. It is hard to get the timing right.

Alright here it is

it says remove any newly installed hard drives or drive controllers, check your hard drive to make sure it is properly ocnfigured and terminated, run ckdsk /f to check for hard drive corruption, and then restart....

technical info

stop 0x0000007b ....................................................................lots more codes.

That's what I thought it would be. It doesn't have the correct storage controller drivers installed.

hmm starting up with my old hd with AHCI i get the blue screen. Switch it back to IDE and it starts up =/ Is there a driver that allows it to boot with either? Im getting into territory im VERY unfamiliar with.

There are no drivers to download from the manufacturer website, windows says the driver is up to date. I can access the hd from windows with on the other hard disk. Im going to try messing around with different modes..

The storage driver is one of the most common ones to cause this sort of problem. Switching between them is often not possible with just Windows. It's like switching from RAID to non-RAID or non-RAID to RAID. It just doesn't usually work, especially if the driver isn't installed already. That's what UR is for (it's only in the Plus Pack for TI, though).

Are you still going to want to boot the other drive? If so, it would need to be setup to have the AHCI drivers installed since the new SSD drive won't boot in IDE mode.

If you want to do some testing, you could create an image of the new SSD drive as it is now (to return to this state easily) and then try the Repair Install and see if that allows you to boot into Windows in AHCI mode. You could also try a clean install in IDE mode and see if that works.

I've got to call it a night. I'll check the thread in the morning. Perhaps Mark will have some ideas.

Robert and Paul:

Wow - marathon thread! I see that you have fixed the BCD and have gotten Windows 7 to start booting. I agree that the current issue is that the boot process halts with a stop error because the original Windows 7 installation does not have the AHCI driver enabled. A default Windows 7 installation has the AHCI driver already installed but it is disabled in the registry. I'm pretty sure that you can fix this without reinstalling Windows.

This Microsoft KB article has instructions on how to enable AHCI mode:
http://support.microsoft.com/kb/922976

However, applying the fix will take a few extra steps because you can't boot in IDE mode to edit the registry. Instead you will have to edit the registry of the non-booting Windows 7 installation on the SSD from the Windows Recovery Environment. I'm a little rusty on this but I suspect you can do it while booted to the recovery environment on a Win 7 DVD by mounting the correct registry hive. Let me reboot and test this...

OK, here's how to make the registry edit.

1. Have only the SSD connected and boot into the Windows Recovery Environment (WinRE) on the W7 DVD
2. Log into the W7 installation on the SSD
3. Go to a command prompt
4. Type Regedit to start the registry editor
5. You will be viewing the registry of WinRE but you need to edit the registry of Windows 7. To do this you need to load the SYSTEM registry hive on the SSD.
6. Click on HKEY_Local_Machine to highlight this branch of the registry and choose File, then Load Hive
7. Navigate to the Windows 7 installation at C:\Windows\System32\config and open the hive named System
8. Give the hive a distinct name like W7Temp and click OK
9. In regedit, expand W7Temp and navigate to ControlSet001\Services\MSAHCI
10. Make the registry edit in the Microsoft KB article (change the value of Start to 0)
11. Click on W7Temp to highlight it
12. Choose File then Unload Hive
13. Close regedit and reboot.

Hopefully Windows 7 will now complete the boot process correctly.

OH MY. I BOOTED INTO WINDOWS! WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

Thanks guys so much! I wouldnt leave me just yet though, there are still chances Ill run into another issue, but right now It seems like success!

Robert:

Outstanding! I trust you are enjoying the speed of your new SSD.

To recap, the original issue was caused by imaging only the Win 7 partition while the boot files were on the other (Vista) partition. Copying the required bootmgr file and \boot folder and then rebuilding the BCD was the fix for that issue. An additional issue was that your SSD required operating in AHCI mode, but Windows would generate a stop error since it was expecting the boot disk to operate in IDE mode. The fix for that issue was to enable AHCI mode by editing the Windows 7 registry. It was quite a struggle but I'm glad that it all worked out.

I see two remaining issues you might want to resolve:

1. If you're going to continue using the HDD, editing the Vista and W7 registries so that they both will boot in AHCI mode.
2. Adding the Windows Recovery Environment (WinRE) to the SSD so that you don't need to boot to the DVD to do repairs. If you'd like to pursue either of these let us know. To prepare for item 2, go to an elevated command prompt on the SSD and type bcdedit /enum all. Post the output back here.

A fascinating thread and a great example of the power of user forums.

Two extremely knowledgeable members who freely give their time to help others.

Id actually like to do both of those. Ill be busy most of the day but ill be back later and Ill take a crack at it. Thanks again for the help both of you!

Here is the enum all output...

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
default                 {current}
displayorder            {current}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7 Home Premium
locale                  en-US
osdevice                partition=C:
systemroot              \Windows
resumeobject            {f0c02526-ffa0-11de-810d-806e6f6e6963}

Windows Boot Loader
-------------------
identifier              {12c261b0-ff47-11de-aa1f-f97d1cc20a4a}
device                  ramdisk=[C:]\Recovery\b0fe22bf-8517-11dd-b552-00044b0a47
05\Winre.wim,{12c261b1-ff47-11de-aa1f-f97d1cc20a4a}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (recovered)
locale
osdevice                ramdisk=[C:]\Recovery\b0fe22bf-8517-11dd-b552-00044b0a47
05\Winre.wim,{12c261b1-ff47-11de-aa1f-f97d1cc20a4a}
systemroot              \windows
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {f0c02526-ffa0-11de-810d-806e6f6e6963}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows 7 Home Premium
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=C:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US

Device options
--------------
identifier              {12c261b1-ff47-11de-aa1f-f97d1cc20a4a}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\b0fe22bf-8517-11dd-b552-00044b0a4705\boot.sdi

C:\Windows\system32>

Robert:

Well, I'll be. That looks perfectly correct. The third entry in the list is the recovery environment (WinRE). Have you tried it out? Reboot and just after the BIOS self-test completes, start hitting the F8 key repeatedly. This should make the boot manager stop at a menu screen. The first item on the screen should be "Repair your computer". Try it to see if it boots into WinRE. This should happen MUCH faster than booting to the DVD.

Ill give that a shot next chance i get.

now for the first 1, getting the other 2 hd ready to boot again in achi mode, do I follow the same steps as before?

Getting the HDD to work in AHCI mode should be easier since you can boot into the appropriate OS and edit the registry directly. I would do the following:

1. Disconnect the SDD and connect only the Vista/Win 7 HDD
2. Set the HDD controller back to IDE mode in the BIOS
3. Boot into Vista and start regedit
4. Use the directions in the MS KB article (link in reply #80) to change the AHCI mode setting in the Vista registry.
5. Reboot into Windows 7
6. Edit the registry to change the AHCI mode setting in the Windows 7 registry
7. Enter BIOS setup and now change the HDD controller setting to AHCI
8. Boot into Vista to test. You may be prompted for a reboot to install a device driver
9. Boot into Win 7 to test. Ditto.

Hopefully all of your disks can now work in AHCI mode. No changes are needed for non-booting (storage) hard drives.