eric_knapper
Member
I'm dual booting adding Windows 7 64bit to my existing XP Pro machine.
After installing Windows 7 home premium 64 bit and selecting it from the dual boot screen I get the following error.
Windows failed to start due to missing or corrupt application
File windows/system32/winload.exe
Error code : 0x000000f
I have two physical drives. On the First is partitions C and D then a DVD drive takes drive letter E and the second physical drive is letter F.
I am dual booting with my original installation of XP Pro on drive C. I booted from the install disk (Windows 7 64bit version) selecting custom install and to install on my second physical drive F. At the reboot I have the error above when I try to boot Win 7 the XP pro boot is fine.
So I ran the Windows 7 repair option and selected the repair startup and got the following error in the report:-
Boot manager failed to find OS loader
File repair failed Error code = 0xa
Repair action: data store repair failed error code = 0x490
So I ran the command prompt with BCDEDIT.EXE which shows this problem
Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=C:
path \ntldr
description Earlier Version of Windows
Windows Boot Loader
-------------------
identifier {e39d602d-c29a-11de-bc7a-db502fc7f629}
device partition=D:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=D:
systemroot \Windows
resumeobject {e39d602c-c29a-11de-bc7a-db502fc7f629}
nx OptIn
detecthal Yes
It looks like the BCD information for the Windows 7 install is pointing to the D: drive instead of the F: drive I installed it to. As I don’t know the syntax for the new BCDEdit application to change the entry I installed EasyBCD under my XP install to change the information for the store however EasyBCD reports the following information showing the Window 7 partition located on the F: drive which is correct???
Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=C:
path \ntldr
description Earlier Version of Windows
Windows Boot Loader
-------------------
identifier {e39d602d-c29a-11de-bc7a-db502fc7f629}
device partition=F:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=F:
systemroot \Windows
resumeobject {e39d602c-c29a-11de-bc7a-db502fc7f629}
nx OptIn
detecthal Yes
So what’s going on?. At a windows OS level EasyBCD shows the correct information for the store but at command level from the Windows 7 disk it shows it to be incorrect pointing at the D drive and I assume this is the one that matters.
Regards,
Eric.
After installing Windows 7 home premium 64 bit and selecting it from the dual boot screen I get the following error.
Windows failed to start due to missing or corrupt application
File windows/system32/winload.exe
Error code : 0x000000f
I have two physical drives. On the First is partitions C and D then a DVD drive takes drive letter E and the second physical drive is letter F.
I am dual booting with my original installation of XP Pro on drive C. I booted from the install disk (Windows 7 64bit version) selecting custom install and to install on my second physical drive F. At the reboot I have the error above when I try to boot Win 7 the XP pro boot is fine.
So I ran the Windows 7 repair option and selected the repair startup and got the following error in the report:-
Boot manager failed to find OS loader
File repair failed Error code = 0xa
Repair action: data store repair failed error code = 0x490
So I ran the command prompt with BCDEDIT.EXE which shows this problem
Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=C:
path \ntldr
description Earlier Version of Windows
Windows Boot Loader
-------------------
identifier {e39d602d-c29a-11de-bc7a-db502fc7f629}
device partition=D:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=D:
systemroot \Windows
resumeobject {e39d602c-c29a-11de-bc7a-db502fc7f629}
nx OptIn
detecthal Yes
It looks like the BCD information for the Windows 7 install is pointing to the D: drive instead of the F: drive I installed it to. As I don’t know the syntax for the new BCDEdit application to change the entry I installed EasyBCD under my XP install to change the information for the store however EasyBCD reports the following information showing the Window 7 partition located on the F: drive which is correct???
Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=C:
path \ntldr
description Earlier Version of Windows
Windows Boot Loader
-------------------
identifier {e39d602d-c29a-11de-bc7a-db502fc7f629}
device partition=F:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=F:
systemroot \Windows
resumeobject {e39d602c-c29a-11de-bc7a-db502fc7f629}
nx OptIn
detecthal Yes
So what’s going on?. At a windows OS level EasyBCD shows the correct information for the store but at command level from the Windows 7 disk it shows it to be incorrect pointing at the D drive and I assume this is the one that matters.
Regards,
Eric.