Thanks -- and good point about using the same tools. I've run EasyBCD and Dual-boot Repair, this time making screenshots of both. Attaching 3 shots of my settings in EasyBCD and two -before/after- the Dual-boot Repair.
Once again, the dual-boot repair did not work. The ghost boot remains, and remains set as default. As you can see, in EasyBCD, there is only one boot option.
The command line attempt still results in the same message as before.
Definitely a ghost boot...!
Thanks again...
[/QUOTE]
1. It is not possible that "Dual-boot Repair" does not fix the problem if no errors are reported - it uses "bcdboot.exe" from MICROSOFT as working horse.
bcdboot, I suppose, has been used by millions if not more.
2. The default boot-menu choice is stored in element "DefaultObject" of {bootmgr} object.
In Visual BCD Editor to set a loader as default you do this:
a) Select loader in left pane.
b) click on Object tab in right pane
c) click on button "Set as default loader" in Object tab
3. ReAgentC is the utility from Microsoft for dealing with recovery environment.
It needs the file "\Windows\System32\Repair\boot.wim" for setting recovery environment. It is there by default.
If "boot.wim" missing see
here how to get "boot.wim" for Windows 7 32-bit or 64-bit
If the utility fails you should check the parameter you supply:
ReagentC /disable - here the command again. ---------------------------------------------------------------------
@gregrocker
If you do not know about Visual BCD Editor just search for "bcd editor" on Google. Google knows it.[/QUOTE]