02-23-2019, 10:00 PM
Thanks for hanging in there with me, firenice03.
On your second point - about Fastboot - my understanding is that this is part of Windows10, but is not a feature of Win7. I have seen how it works, and read various websites including the Lifehacker one, as my wife has a Win10 laptop. As far as I can tell it does not exist on this 'problematic' Lenovo laptop whose only (visible!) OS is Win7.
I can't claim to be an expert on EasyBCD although it works successfully on the dual boot arrangement I have on my regular daily laptop. Unfortunately the EasyBCD support website and forum offer little help. In a nutshell, it is a program, with a GUI, which does what would otherwise only be possible by using the bcdedit command prompt in a Windows terminal. This is what the other article - marcofranssen - to which you linked describes (although the stuff about hyper-V and virtual box is all gobbledegook to me).
However, the fact that I have EasyBCD on this problematic laptop does mean that I can indeed look at the configuration of the BCD in the way that article describes, without having to go into the terminal, make backups, and all that stuff.
So..... I went and had a look. This is what I found
Unfortunately I do not understand, and cannot interpret, this information. I wonder if anyone else can explain what it says about the current boot arrangements?
One interesting point is that it does differ, in some respects, from the equivalent BCD info on my main laptop (which boots quite happily, using EasyBCD, into either Win7 or Linux). The main difference(s) appear to be in the line about "device". On this problematic Lenovo computer (above) it says
On my other - normal - dual boot computer, the equivalent BCD entries in the "device" line are, in the Windows Boot Manager
I could try and guess what this signifies: that in the problematic Lenovo computer the Windows boot arrangements are somehow in a "custom" location or configuration. But maybe someone who understands BCD and BCD editing can offer a more detailed explanation?
On your second point - about Fastboot - my understanding is that this is part of Windows10, but is not a feature of Win7. I have seen how it works, and read various websites including the Lifehacker one, as my wife has a Win10 laptop. As far as I can tell it does not exist on this 'problematic' Lenovo laptop whose only (visible!) OS is Win7.
I can't claim to be an expert on EasyBCD although it works successfully on the dual boot arrangement I have on my regular daily laptop. Unfortunately the EasyBCD support website and forum offer little help. In a nutshell, it is a program, with a GUI, which does what would otherwise only be possible by using the bcdedit command prompt in a Windows terminal. This is what the other article - marcofranssen - to which you linked describes (although the stuff about hyper-V and virtual box is all gobbledegook to me).
However, the fact that I have EasyBCD on this problematic laptop does mean that I can indeed look at the configuration of the BCD in the way that article describes, without having to go into the terminal, make backups, and all that stuff.
So..... I went and had a look. This is what I found
Quote:Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device locate=custom:12000002
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {a6ea9bab-24b4-11e9-8e96-f82fa8e876d9}
resumeobject {06f87eb3-4038-11e0-aecc-c1f066e6c02a}
displayorder {06f87eb4-4038-11e0-aecc-c1f066e6c02a}
{a6ea9bab-24b4-11e9-8e96-f82fa8e876d9}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 20
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {06f87eb4-4038-11e0-aecc-c1f066e6c02a}
device locate=custom:12000002
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice locate=custom:22000002
systemroot \Windows
resumeobject {06f87eb3-4038-11e0-aecc-c1f066e6c02a}
nx OptIn
Real-mode Boot Sector
---------------------
identifier {a6ea9bab-24b4-11e9-8e96-f82fa8e876d9}
device partition=C:
path \NST\AutoNeoGrub0.mbr
description Linux Mint
locale en-US
custom:250000c2 0
Unfortunately I do not understand, and cannot interpret, this information. I wonder if anyone else can explain what it says about the current boot arrangements?
One interesting point is that it does differ, in some respects, from the equivalent BCD info on my main laptop (which boots quite happily, using EasyBCD, into either Win7 or Linux). The main difference(s) appear to be in the line about "device". On this problematic Lenovo computer (above) it says
Quote:locate=custom:12000002in both the Windows Boot Manager and the Windows Boot Loader, and
Quote:partition=C:in the Real-mode Boot Sector - whatever that is, but it evidently relates to Linux Mint!
On my other - normal - dual boot computer, the equivalent BCD entries in the "device" line are, in the Windows Boot Manager
Quote:partition=\Device\HarddiskVolume1, and in the Windows Boot Loader
Quote:partition=C:. The entry in the real-mode Boot Sector for the Linux OS is also
Quote:partition=C:
I could try and guess what this signifies: that in the problematic Lenovo computer the Windows boot arrangements are somehow in a "custom" location or configuration. But maybe someone who understands BCD and BCD editing can offer a more detailed explanation?