[FIXED] [EBCD-417] Advanced settings not saved w/system BCD on Windows 7 Ultimate

#1
Hello,

I am encountering the following problem - unless I am completly missing something:

Using "Add New Entry" I wanted to create a SafeMode Network enabled boot option.
Once the new entry was created, I used "Advanced Settings" to change the newly created entry to
Safe Mode: "Safe Mode w/Networking"
NoExecute: "Always Off".
Then I hit "Save Settings".

When I close the application and reopen or simply click on "File" - "Load system BCD", the Advanced options are default (and modified settings are lost) for the new Boot entry.

Am I doing something wrong, or did I just discover a bug?

Windows 7 Ultimate 64bit
EasyBCD 2.0.1

Thank you,
Wolfgang
 

mqudsi

Mostly Harmless
Staff member
#2
Hi Wolfgang,

Thanks for your bug report. I'll look into this and let you know!
 
#3
I have exactly the same issue.
When I tell it to change my boot login time to 5 seconds instead of 30 seconds, it says it is saved, but it isn't. Same with the boot order. I tell it to load Ubuntu as the default, but Windows 7 is always the default.
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#4
@Wolfgang: Yes, there's a bug. You *did* create a safemode entry, and Nx IS disabled - but the advanced settings dialog is not updating for some reason. I just confirmed this - the entry and its properties are set, but EasyBCD doesn't show it.

@donald: screenshots, please?

Addendum:

This issue is fixed in the next build. Case [EBCD-391]
 
Last edited:
#5
I tried it again this morning and it actually worked !!!!!!! Did it exactly like I did several times yesterday when it didn't save, but it worked today. Go figure. Thanks anyways for the great program.
 

mqudsi

Mostly Harmless
Staff member
#6
You're welcome :smile:
 

emm

New Member
#8
I am having the exact same problem as ixquisite (Wolfgang) did, but with version 2.0.2.117, so i am not sure the linked beta build would solve that problem?

There is a workaround though. If you go to system configuration in the admin tools of Win7 (Control Panel ---> System and Security ---> Administrative Tools ----> System Configuration), and then select "Selective Startup" instead of "Normal Startup" it will work. Then again you can select the safe boot from right there, so EasyBCD becomes superflous.

I'd really like to see this work.

For the record, i am on Win7 Ultimate 64bit.
 

mqudsi

Mostly Harmless
Staff member
#9
Hi emm, welcome to NST.

Please post the contents of "Detailed Mode" on the main EasyBCD page.
 

emm

New Member
#10
Here you go:
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {4a2ed645-7bdd-11de-a24e-002215f9015e}
resumeobject {20992daa-7034-11df-908d-806e6f6e6963}
displayorder {4a2ed645-7bdd-11de-a24e-002215f9015e}
{4a2ed648-7bdd-11de-a24e-002215f9015e}
{4a2ed649-7bdd-11de-a24e-002215f9015e}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 10
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {4a2ed645-7bdd-11de-a24e-002215f9015e}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Ultimate
locale en-US
recoverysequence {4a2ed633-7bdd-11de-a24e-002215f9015e}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {20992daa-7034-11df-908d-806e6f6e6963}
sos No
debug No

Windows Boot Loader
-------------------
identifier {4a2ed648-7bdd-11de-a24e-002215f9015e}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows 7 Safe
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {c9034446-9f1b-11df-86ca-806e6f6e6963}
sos No
debug No

Windows Boot Loader
-------------------
identifier {4a2ed649-7bdd-11de-a24e-002215f9015e}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows 7 Unsigned
locale en-US
loadoptions DDISABLE_INTEGRITY_CHECKS
osdevice partition=C:
systemroot \Windows
sos No
debug No

-------------------
As you can see the settings for safe mode do not get saved. When i use the manual method over the Win7 admin tools the BCD gets updated correctly (and EasyBCD also shows it correctly).

Also the "displaybootmenu" option did not get activated until i did so manually in the admin tools. I can now change the seconds to wait though. So that works. I can also add or remove entries, and obviously adding the Unsigned Drivers check also worked (although i have not yet tested that, as i have no unsigned drivers needed for this computer).

Just adding the safe options (and presumably the other options as well, except for the VGA option, which strangely does get added) does not work.

Thanks for the quick response. I hope we can get this resolved.
 

mqudsi

Mostly Harmless
Staff member
#11
and does EasyBCD automatically load your BCD, or does it prompt you to dos manually?
 
#13
Just wanted to mention that I too still have this problem -
specifically - EasyBCD 2.02 - build 117 - will
not save the value for "safeboot" (should you try to
add an entry with this parameter).

And if you already have an entry with this parameter - it will not display
it as being set within the GUI (even though it is set).

I had also tried resetting,re-creating, and repairing - and I still can't create
a boot entry that saves the value for safeboot.

My only workaround - was to use an older build (for me build 99 ) -
to create the boot entries - then I upgraded to build 117. (still doesn't display properly - but the entry is still set).

Let me know if you want me to test a beta build - should you develop a fix. (Build 118 still has the problem)


Thanks and Regards,

Doug

Windows® Vista® Ultimate SP2 64-bit {EN}
Intel® Core™2 Quad Q9400 / Memory: 4GB
NVIDIA GeForce 9400 GT (v.258.96)

PS - FYI: Same behavior - Different Server - running WIN 7 x64 Ultimate
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#14
Hi MrFreeze, welcome to NeoSmart Technologies! :smile:

Thanks for your bug report - I'll look into it right now.
 

mqudsi

Mostly Harmless
Staff member
#15
Fixed in build 120 and up.