Automated Startup Repair fails. Cannot find OS Loader.
On installation of 'Windows 7', after installing needed drivers, some of which were designed for XP or Vista, on a Toshiba Portege M200 (Tablet PC from 2003) and Windows 7 automatically downloading and installing updates:
Windows 7 can't boot.
It goes directly to the Automated System Recovery and no matter which option I choose it fails to fix the problem.
1. Sometimes it says it did fix the problem and didn't.
2. Sometimes it says it failed to fixed the problem and in those cases the Diagnosis and Repair details says as:
Root cause found:
Boot manager failed to find OS loader.
Repair action: File Repair
Result: Failed. Error code = 0x490
Time Taken = 4767 ms
Repair action: Boot configuration data store repair
Result: Failed. Error code = 0x490
Time Taken = 150ms
Repair action: System Restore
Result: Failed. Error code = 0x1f
Time taken = 68489 ms
What is the cause of this? And how do I fix it?
The harddrive is brand new and a full memory check said the RAM was good.
I had the same problem on one of our laptops. This has 2GB of memory so it appears to be related to that and Windows updates. I did the following from the following Microsoft article which resolved the issue for me http://support.microsoft.com/kb/927392/en-gb.
To run the Bootrec.exe tool, you must start Windows RE. To do this, follow these steps:
Put the Windows Vista or Windows 7 installation disc in the disc drive, and then start the computer.
Press a key when you are prompted.
Select a language, a time, a currency, a keyboard or an input method, and then clickNext.
Click Repair your computer.
Click the operating system that you want to repair, and then click Next.
In the System Recovery Options dialog box, click Command Prompt.
Type Bootrec.exe, and then press ENTER.
Note To start the computer from the Windows Vista or Windows 7 DVD, the computer must be configured to start from the DVD drive. For more information about how to configure the computer to start from the DVD drive, see the documentation that
is included with the computer or contact the computer manufacturer.
Bootrec.exe options The Bootrec.exe tool supports the following options. Use the option that is appropriate for your situation.
Note If rebuilding the BCD does not resolve the startup issue, you can export and delete the BCD, and then run this option again. By doing this, you make sure that the BCD is completely rebuilt. To do this, type the following commands at the
Windows RE command prompt:
bcdedit /export C:\BCD_Backup
attrib bcd -s -h -r
ren c:\boot\bcd bcd.old
/FixMbr The /FixMbr option writes a Windows 7 or Windows Vista-compatible MBR to the system partition. This option does not overwrite the existing partition table. Use this option when you must resolve MBR corruption issues, or when you have
to remove non-standard code from the MBR. /FixBoot The /FixBoot option writes a new boot sector to the system partition by using a boot sector that is compatible with Windows Vista or Windows 7. Use this option if one of the following conditions
The boot sector has been replaced with a non-standard Windows Vista or Windows 7 boot sector.
The boot sector is damaged.
An earlier Windows operating system has been installed after Windows Vista or Windows 7 was installed. In this scenario, the computer starts by using Windows NT Loader (NTLDR) instead of Windows Boot Manager (Bootmgr.exe).
/ScanOs The /ScanOs option scans all disks for installations that are compatible with Windows Vista or Windows 7. Additionally, this option displays the entries that are currently not in the BCD store. Use this option when there are Windows
Vista or Windows 7 installations that the Boot Manager menu does not list. /RebuildBcd
The /RebuildBcd option scans all disks for installations that are compatible with Windows Vista or Windows 7. Additionally, this option lets you select the installations that you want to add to the BCD store. Use this option when you must
completely rebuild the BCD.
After following the above i then ran the following from command prompt:
This resolved the issue for me and allowed me to log on to the PC in its previous working state. Great stuff.