Will EasyBCD wipe out MBR ?

[Sdream]

Two physical HDDs in my machine.
One contains Vist.
The other contains XP.

First, EasyBCD established a dual-boot, WinXP & Vista.
Then, I fooled around with EasyBCD trying to change partition ID letters.
The next thing was that no partition ID letter was changed but boot.
1.
Dual-boot has disappeared.
2.
Can boot into WinXP only manually,by selecting boot disk in BIOS.
3.
If select manually the Vista disk to boot, does not boot. Windows boot manager says the file is either missing or corrupted.

Question
Is Vista MBR wiped out?
How can it be restored if it is still on the disk?

Thank you.

[Terry60]

You cannot change disk letters with EasyBCD. There are no disk letters in the BCD. EasyBCD just translates the UID of the BCD entry into a letter as seen by the booted system.
If you change those letters you are effectively lying to the bootmanager about where everything is. That's why they won't boot.
Put the letters back as they were.

[JustinW]

You can do that in XP, or startup repair may be able to help using our recovery disc following these instructions.

[Sdream]

You cannot change disk letters with EasyBCD. There are no disk letters in the BCD. EasyBCD just translates the UID of the BCD entry into a letter as seen by the booted system.
If you change those letters you are effectively lying to the bootmanager about where everything is. That's why they won't boot.
Put the letters back as they were.

Thank you very much, Terry !

The current are as the following:
HDD Hitachi SATA 2
Partition E containing Vista (This is the one that does not boot.)
Partition F storage
HDD WD Caviar SATA 1
Partition C containing XP (This is the one that boots now.)
Partition D storage
Partition G empty (Ubuntu was removed from this part.)

I tried to set partition E boot into Vista but it did not work
It is very possible that I did not set it right

A guide for setting partition E to boot will be deeply appreciated !

Thank you very much !

[Terry60]

Post DM and settings information as detailed in the sticky

[Sdream]

Post DM and settings information as detailed in the sticky

Thank you very much, Terry !
01.JPG

02.JPG

03.JPG

04.JPG

05.JPG

06.JPG

Do these pictures show the problem?

Thank you `!

[Terry60]

Just the first screen above in detailed mode. (no need to attach screenshot, just copy/paste the contents of the window), and a screenshot of the Disk Management screen like this

[Sdream]

Just the first screen above in detailed mode. (no need to attach screenshot, just copy/paste the contents of the window), and a screenshot of the Disk Management screen like this

Thank you very much, Mike !

Sorry for taking up so much of your precious time.

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=E:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {e8709fb6-fa5f-11db-be4d-e219ece5282e}
displayorder {e8709fb6-fa5f-11db-be4d-e219ece5282e}
{9760c0fe-2cc7-11df-a455-002197642222}
{9760c0ff-2cc7-11df-a455-002197642222}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 5
custom:45000001 1

Windows Boot Loader
-------------------
identifier {e8709fb6-fa5f-11db-be4d-e219ece5282e}
device partition=E:
path \Windows\system32\winload.exe
description Windows Vista
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=E:
systemroot \Windows
resumeobject {e8709fb7-fa5f-11db-be4d-e219ece5282e}
nx OptOut
custom:42000002 \system32\winload.exe
custom:45000001 2
custom:47000005 301989892
4

Windows Boot Loader
-------------------
identifier {9760c0fe-2cc7-11df-a455-002197642222}
path \Windows\system32\winload.exe
description Microsoft Windows
systemroot \Windows

Windows Boot Loader
-------------------
identifier {9760c0ff-2cc7-11df-a455-002197642222}
path \Windows\system32\winload.exe
description Microsoft Windows
systemroot \Windows

DiskManagement.JPG


Thank you !

[Terry60]

OK
I think your problem is quite simple (but hard to be sure for one unused to pictorial scripts. Your DM doesn't quite match either the Chinese or Korean here. Perhaps you could add an entry.)

You seem to be booting XP directly from the second HDD using native NTLDR, so while you're successfully modifying the BCD on E:\, you're never actually using it.

Change the BIOS boot sequence to boot from the other HDD, then from Vista, add an XP entry to the BCD, let it aut-configure and don't change the letter. You can remove the 2 redundant Vista entries.

[Sdream]

OK
I think your problem is quite simple (but hard to be sure for one unused to pictorial scripts. Your DM doesn't quite match either the Chinese or Korean here. Perhaps you could add an entry.)

You seem to be booting XP directly from the second HDD using native NTLDR, so while you're successfully modifying the BCD on E:\, you're never actually using it.

Change the BIOS boot sequence to boot from the other HDD, then from Vista, add an XP entry to the BCD, let it aut-configure and don't change the letter. You can remove the 2 redundant Vista entries.

Thank you, Terry!

As I posted before, boot the Vista would end up in a black&white screen.
But I tried it again in order to follow your instructions. Same thing happened.

Picture 1
Windows Boot Manager shows
Windows Vista
Microsoft Windows XP Pro.口x口口口x口口(Note)
Select & boot Vista
Picture 2 comes out
101 002.jpg
Picture 2
Windows Boot Manager shows thes message:
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem
1.Insert installation disk and restart
2.Choose your language and click next
3.Click REPAIR . . . .
If you do not have this disk . . . .
File: Windows\System32\Winload.exe
Status: 0xc000000e
Info: The selected entry . . . missing or corrupted
101 003.jpg

Note:
If this Win XP is selected to boot, it starts CDRom and
Win XP installation. This was caused by a mistake leaving the Win XP in the machine.

Is it possible that this is the cause of the problem?

[Sdream]

Thank you very much, Terry !

Sorry for taking up so much of your precious time.

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=E:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {e8709fb6-fa5f-11db-be4d-e219ece5282e}
displayorder {e8709fb6-fa5f-11db-be4d-e219ece5282e}
{9760c0fe-2cc7-11df-a455-002197642222}
{9760c0ff-2cc7-11df-a455-002197642222}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 5
custom:45000001 1

Windows Boot Loader
-------------------
identifier {e8709fb6-fa5f-11db-be4d-e219ece5282e}
device partition=E:
path \Windows\system32\winload.exe
description Windows Vista
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=E:
systemroot \Windows
resumeobject {e8709fb7-fa5f-11db-be4d-e219ece5282e}
nx OptOut
custom:42000002 \system32\winload.exe
custom:45000001 2
custom:47000005 301989892
4

Windows Boot Loader
-------------------
identifier {9760c0fe-2cc7-11df-a455-002197642222}
path \Windows\system32\winload.exe
description Microsoft Windows
systemroot \Windows

Windows Boot Loader
-------------------
identifier {9760c0ff-2cc7-11df-a455-002197642222}
path \Windows\system32\winload.exe
description Microsoft Windows
systemroot \Windows

Attachment 1381


Thank you !

000000000

[Terry60]

Try EasyBCD / Diagnostics / Reset BCD, then boot from the Vista HDD again.

[Sdream]

Try EasyBCD / Diagnostics / Reset BCD, then boot from the Vista HDD again.

Thank you very much, Terry!

I have just tried 4 times Reset BCD, Rescue my system, and designated manually the letter of the drive, and booted. It did not make any difference.

[Coolname007]

Sure you pointed the Vista entry in EasyBCD at the correct partition?
That error you got earlier about the winload.exe, when trying to boot Vista, is usually because your Vista entry is pointed at the wrong partition, not the one that has winload.exe on it. You need to point it at the drive letter of the Vista partition.
If you can confirm you already did that, and its still not booting, then winload.exe must be missing, and will need to be replaced.

[Sdream]

Sure you pointed the Vista entry in EasyBCD at the correct partition?
That error you got earlier about the winload.exe, when trying to boot Vista, is usually because your Vista entry is pointed at the wrong partition, not the one that has winload.exe on it. You need to point it at the drive letter of the Vista partition.
If you can confirm you already did that, and its still not booting, then winload.exe must be missing, and will need to be replaced.

Thank you very much for help!

Am I sure that I did point the right partition letter?
This is what I did in 5 steps:
01.JPG
02.JPG
Anything wrong in these steps?

Am I sure that Vista is on partition E:\ ?
Positive.

Am I sure that Vista's MBR is on partition E:\ ?
No. I am not sure.
Windows Boot Manager says that it might be missing or corrupted.

My question:
Could EasyBCD remove MBR from partition E:\ because of my mistake or move MBR from one partition or HDD to another?


******************************************************************************** ***************************
In addition, I have found this information as hereunder by use of VistabootPro.
This is posted in hope that this might provide correct information of the mistakes I have made.
I have not gone any further in VistabootPro. than finding this information.
******************************************************************************** ****************************
Windows Boot Manager
--------------------
identifier {bootmgr}
device boot
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 5

Windows Boot Loader
-------------------
identifier {default}
device partition=E:
path \Windows\system32\winload.exe
description Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice partition=E:
systemroot \Windows
resumeobject {e8709fb7-fa5f-11db-be4d-e219ece5282e}
nx OptOut

Resume from Hibernate
---------------------
identifier {e8709fb7-fa5f-11db-be4d-e219ece5282e}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
pae No
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \Boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device unknown
path \ntldr
description Earlier Version of Windows

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{7ff607e0-4395-11db-b0de-0800200c9a66}

Inherited Settings (20200003)
-----------------------------
identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
custom:250000f3 0
custom:250000f4 1
custom:250000f5 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}