I think I have a couple of options. I'm looking at the eBCD Repair tab, and it lists a backup file that I had created. Or I could use eBCD to either "Reset" or "Recreate" the configuration - I'm looking into that now to see what it means. Or I could use the Windows Restore function you mention.
The System Restore - does that cover the boot files as well? I thought that was just within Windows.
I ran Restore because I wanted to see how it worked. It seems to be a good tool, but it found no problem. I booted back into Windows with no problem, via the easyBCD boot screen. Yet easy still reports the missing data store. I don't know what to make of this. Presumably the Windows Restore checks the MBL as well as the PBL?
Using EasyBCD to create a Dual Boot menu with Safe Mode is suspect, so I would remove the non-Win7 listing in EasyBCD Edit Boot Menu tab.
If this doesn't help I would use the EasyBCD backup or rebuild the MBR:
bootrec /FixMbr
Another method:
Using your Windows 7 installation disc or Repair CD, boot to the command prompt at startup. Type in these comands below, and press enter after each one.
bootrec /FixBoot
bootrec /RebuildBcd
Greg, I'm not clear on what would be wrong with using easyBCD to add Safe Mode options to the boot menu. IAC, last night I did run its Write MBR function, and was surprised to find that it left intact the boot screen it had created. Obviously I'm not clear on what protocols are involved here, and I need to read up on it. The Repair CD sounds like a good idea, and easy bcd offers a couple of heavier-duty options itself, but I'm going to study up first.
Thanks for that information,
p.
What could be wrong is some boot corruption which needs to be sorted by repairing or rebuilding the MBR (if you're lucky) or ultimately wiping the HD to get a fresh slate for a clean install.
Can I please get feedback from anyone who has a default Win7 installation, where a small Active System partition was created before the main Win7 partition, who has not altered the BCD, as to whether the options on the Boot tab of MSCONFIG are active or not? We're trying to ascertain whether changing the BCD turns off the Boot tab options.
Thanks,
p.
Thanks for that feedback. We've been pursuing this over at easyBCD, and it seems that something has commandeered the BCD. I tried Greg's BootRec commands, above, and when I ran the /scanos switch it found no windows installations. I thought I had bricked the install, but when I rebooted the old boot options screen came up again, impervious. I looked into the system partition and found a file, EASEUSLD.LDR, which looks suspicious. I've got a query in to Easeus on it.
It turns out that Easeus Partition Master rebuilds the BCD in a "nondestructive" way. Evidently this means it constructs its own BCD alongside the original, and then direct the boot stream to it. Thus, I could edit the original BCD all day long, and nothing would change with the way the machine booted up.
I believe in being safe, but sometimes playing it too safe creates more problems than it's worth. And that's what happened here. There seemed to be no way to reinitialize the boot process, and that's a frustrating place to be. I doubt I'll use Easeus to perform that function again.
Thankfully, EasyBCD came to the rescue, with its "Change boot drive" function. I simply recreated the boot process in a "new" drive, which actually was the original EFI drive, and I regained perfect control over the boot process with its BCD.
I think the sluggishness I've been experiencing is due to the MS parental controls I've been experimenting with. I believe they grab a hold of the machine in a pretty significant way, and that takes boot time.
The hibernation issue has been more perplexing. I thought the boot thing would solve it, but as soon as I call for hibernation the machine presents the log in screen. Something fundamentally wrong there.
I wanted to update this thread. The root of the problem was that the system reserve partition had somehow had its drive letter removed. I probably did that in an attempt to re-hide the partition after exploring it. It turns out there is a functional difference between removing a drive letter and merely Hiding a partition. Windows was having a hard time accessing the partition without its drive letter.
The Windows Disk Manager allows only one way to hide a partition - by removing its drive label. But in many cases that is not the best way. I used Partition Wizard to hide the drive without removing its letter.
Once I restored the letter, the Boot tab of MSCONFIG became alive again. I could access the BCD stores in the system reserve partition. The ability to hibernate returned, and my boot-ups became fast again.
It would be fascinating to know how all these things interplay, but for now at least I found the root cause.
Quote