Where are option DISABLE_INTEGRITY_CHECKS and TESTSIGNING ON ?

#1
As far as I understand EasyBCD is a GUI wrapper around bcdedit.

Does EasyBCD cover ALL options/functionality of bcdedit?

Where are the corresponding EasyBCD button/menu/option for the bcdedit commands:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKSbcdedit -set TESTSIGNING ON

Thank you
Peter
 

mqudsi

Mostly Harmless
Staff member
#2
EasyBCD | Advanced Settings | Disable Driver Verification
 

Terry60

Knows where his towel is.
Staff member
#4
"allow......unsigned drivers.."
 
#5
"allow......unsigned drivers.."
Ok thank you. Does this checkbox cover both commands:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
AND
bcdedit -set TESTSIGNING ON

or only the first?
If only the first: Where can I switch to TESTSIGNING in EasyBCD?

Peter
 

Mak 2.0

Mod...WAFFLES!?!?
Staff member
#6
It is only for the first. There is no option to turn on testsigning in EasyBCD. There is never really a reason to put Windows into Test Mode. If you must, you will still have to do it manually.
 
#7
Ok, thank you.

But I have one more important problem:

When I type (on 64bit WIn7 pro) at the command prompt

bcdedit

then I get all the current BCD settings. Among others it shows:

loadoptions DISABLE_INTEGRITY_CHECKS

So that means that the installation of unsigned drivers is allowed. Fine so far.

Now I start EasyBCD and go to the tab you suggested.
Here the checkbox before "Allow installation of unsigned drivers on 64bit Windows"
is UNCHECKED/empty. That means the opposite of what bcdedit shows.

I would have expected that EasyBCD reads immediately after start at first the current local settings and adjusts automatically all options in its GUI according to the real current world.

But this seems not the case. This is confusing.

Is there an option in EasyBCD to force it to do this?

Peter
 

Terry60

Knows where his towel is.
Staff member
#8
"View Settings" is the output screen.
All others are input screens and none of them reflect current status.
 

mqudsi

Mostly Harmless
Staff member
#9
Actually Terry, they should all reflect the current settings (memory limit, cpu limit, SOS, Safe Mode, Debugging, Drivers, etc.).

Peter, I'll look into this.

Addendum:

That's because the correct option is DDISABLE_INTEGRITY_CHECKS with an extra 'D' at the front.
 
Last edited: