 
|
 |
|
|
 |
| Posts
:
4 |
| Level
:
|
| Tech Points
:
1 |
| From:
United States |
|
Posted:4/18/2013 12:29:00 AM |
|
Hi. I'm running Windows 7 x64 on my P8Z77-V (BIOS 1708) and when I tried to use TrueCrypt FDE the system can't boot as it normally does. On TrueCrypt forum they say the culprit is Secure Boot, which it should be disable. Problem is BIOS just says "enabled" and gives two options to set: "Windows UEFI mode" or "Other OS". Neither fixed my problem. So, is there a way to stop Secure Boot from being enable? Thanks for your help.
PS: By the way, if somebody had this TC FDE problem before and found a workaround, I will appreciate your input.
|
|
|
|
Moderator |
 |
| Posts
:
97630 |
| Level
:
|
| Tech Points
:
21157 |
| From:
United States |
|
| There are 10 kinds of people in the World...Those who understand binary, and those who dont! |
|
|
|
| Posts
:
4 |
| Level
:
|
| Tech Points
:
1 |
| From:
United States |
|
|
Posted:4/18/2013 4:52:00 PM |
|
Hi Ulrich. Thanks for your reply.
I thought the same thing, that "Other OS" would disable it, but when I went back to check "Secure Boot state" it still showed "Enabled."
Also, the description about "Windows UEFI mode" vs. "Other OS" is confusing. If you go the first link and check the third screen capture,
under "Other OS" says "Get the optimized function" (which function?) and then "Only on Windows UEFI mode ... Secure Boot can function properly"
(so with "Other OS" Secure Boot doesn't work properly but it is still enable?)
Regarding your other questions. The motherboard is new and 1708 is its default BIOS. I installed Windows 7 Ultimate x64 from scratch on a new HDD.
At the time I didn't pay attention to the Secure Boot option in the BIOS (it was set to "Windows UEFI mode") but W7 boots fine with either option.
By the way, my HDD is 500GB MBR (i.e. no GPT,) 1 partition, and its status is Healthy(System Boot, Page File, Active, Crash Dump, Primary Partition)
and in the BIOS main page (where it shows devices boot order) there isn't any UEFI blue ribbon on the graphical representation of my HDD.
Going back to TrueCrypt, the problem exactly happens once I enter the passphrase. It says Booting and then when Windows 7 should start, the screen
goes all black (except for a white cursor blinking on the upper left corner, which sometimes it could be seen on normal boot right after the ASUS logo screen
and before W7 starts.) By the way, once I hit that screen, HDD LED doesn't show any activity at all and no matter how much I wait nothing
ever happens until I hit the reset button.
|
|
|
|
Moderator |
|
| Posts
:
97630 |
| Level
:
|
| Tech Points
:
21157 |
| From:
United States |
|
|
Posted:4/18/2013 10:45:00 PM |
|
Hi J..
The blinking curson generally indicates the system can not find or read the master boot record on the hard drive.. and exactly why that is happening, I can't say... Apparently, enabing TrueCrypt disturbs the normal boot process... possibly looking for a TrueCrypt volume.. which may not exist...
http://www.truecrypt.org/docs/?s=tutorial
|
|
|
| There are 10 kinds of people in the World...Those who understand binary, and those who dont! |
|
|
|
| Posts
:
4 |
| Level
:
|
| Tech Points
:
1 |
| From:
United States |
|
|
Posted:4/19/2013 1:02:00 AM |
|
Normally, if no boot device is present, an error message appears. The blinking cursor, like I said, it is normal.
It happens after the BIOS POST and before OS boots (i.e. between ASUS logo screen and Windows 7 start screen).
By the way, the system does boot with TC. It shows its Boot Loader, where I input the passphrase. It is what happens
next (or rather what does not happen) the mystery. Basically, to make it graphically it goes like this:
W7 ALONE: Power on -> Beep -> ASUS Logo screen -> blinking cursor -> Windows 7 starts
W7 W/ TC: Power on -> Beep -> ASUS Logo screen -> TC Boot Loader screen -> I enter correct passphrase -> blinking cursor -> nothing else happens
One more thing regarding TC: I'm not trying to mount a volume, I'm doing whole disk encryption.
What fails it is the pre-test TC does to make sure everything is right before the actual encryption.
Also, I'm not new to TC, I use it before never had a problem during pre-test or after encryption.
What is true is that I never used it on an UEFI motherboard.
Again, thanks for your input, Ulrich. I keep trying different BIOS options regarding CMS and Secure Boot, none helped.
I just wish somebody who had this or a similar problem may read this thread and care to share their experience whether
they fixed or not.
|
|
|
|
VIP Member |
 |
| Posts
:
1 |
| Level
:
|
| Tech Points
:
1 |
| From:
United States |
|
|
Posted:12/24/2013 10:22:00 PM |
|
Had the same problem on sabertooth 990fx r2 gen 3 after a bios update on a Windows 7 x64 machine. Strangely, it would happen randomly. Sometimes it would go for days with no problems then it would decide not to boot 4-5 times in a row. Had it set to other OS in bios but secure boot was on. I played around and think I found a solution. Not sure if the sabertooth options will be the same but hopefully they're close enough to help. I enabled UEFI . After enabling, right below, a new option appears: key settings or key management , something to that effect. Click on it and the first option is clear saved keys. Clear them and go back to the previous screen. Switch back to other OS and secure boot should be disabled. Hope this helps!
|
|
|
|
|
|
| Posts
:
1 |
| Level
:
|
| Tech Points
:
1 |
| From:
Australia |
|
|
Posted:11/2/2014 12:34:00 PM |
|
Thanks Chris, this solution works for my Z97 Deluxe motherboard. Didn't enable UEFI, went straight to Boot > Secure Key Management. Clear Saved Keys, then go back to previous screen. This disabled Secure Boot. I had 'Other OS' selected because the keys were cleared.
|
|
|
|
Member |
 |
| Posts
:
4 |
| Level
:
|
| Tech Points
:
2 |
| From:
USA |
|
|
Posted:3/8/2016 3:01:00 AM |
|
Chris,
I am actually thinking about doing a new AMD build using the Sabertooth 99FX R2.0 (non Gen 3) or the M5A99FX R2.0.
I've been holding back on ordering the Asus MB, because there is this "reputation" on many web forums where people are complaining that Secure Boot cannot be turned off successfully in the Asus BIOS.
This is ONLY web post I've been able to find that indicates there is a fix for this.
I still haven't "made the jump" and bought a board, but I would be happy with either of the two listed above. Assuming the "clear saved keys" option is what fixing things, I think the message needs to get out there is a good work around.
THANK YOU FOR POSTING!
- Ted
|
|
|
|
Member |
 |
| Posts
:
5 |
| Level
:
|
| Tech Points
:
2 |
| From:
USA |
|
|
Posted:1/31/2017 9:16:00 AM |
|
Well, I am struggling on my Z97M Plus. Secure boot may appear disabled (shown as disabled and with PK key unloaded), but when from the Exit menu I select boot to EFI, after a few seconds of black screen it pops up a message telling me EFI secure boot is enabled. No matter what I do, backup keys, clear, select Other OS, I won't be able to boot Debian installer and I will be lead to the grub> prompt. From here it's quick to verify the EFI boot didn't happen, all the devices reported by grub show an "unknown file system".
|
|
|
|
Member |
|
| Posts
:
5 |
| Level
:
|
| Tech Points
:
2 |
| From:
USA |
|
|
Posted:1/31/2017 9:22:00 AM |
|
Interestingly enough, before upgrading the UEFI BIOS to 2903, there have been two instances where it booted "unsecure" even if the secure boot was enabled. The only reason why installer didn't complete is that the order connected devices were reported to grub was incorrect, naming USB drive as (hd0). That was fixed by UEFI BIOS 2903 but at that point I could not disable secure boot, nor boot, any more.
|
|
|
|
|
|
|
|
|