Windows 7 Pro UEFI Install Secure Boot Violation Asus Maximus VII Ranger

[gupsterg]

I have been using Windows 7 UEFI for approx. 5 months without an issue (my orig thread). I had not applied any updates to OS other than what Agent's patching scripts did to the Win7 SP1 USB UEFI install I made.

On the 6th of April I decided to reinstall Windows as I'd been meddling around with "things" on my rig, I just wanted a fresh install. On the 7th of April I decided to hide some of the nagware updates and apply the others, as I did batch installs of 15 updates or so I rebooted after each set of updates.

All went well until I only had approx. 5 "Important" updates and 10 "Optional" (IIRC), after doing those and rebooting I was greeted with:-





I then disabled secure boot to get back into windows, I restored the computer to an earlier point prior to the last set of updates I applied and still I'd get the same screen on post with secure boot enabled. So next I went back a complete day, ie no updates but original state after installing OS and drivers, again same screen with secure boot on.

Now as I have done no firmware updates the message can't be due to that IMO. As OS only has drivers that originally showed no violation it can't be that. Currently I think Windows update has done something and when I do restore to an earlier point that change is not being reverted.

Only way "Secure Boot" will now function is if I change "Windows UEFI Mode" to "Other OS" or disable secure boot.





It seems I'm not alone with this issue, another Asus owner but Z170, orig link translated link. Another search revealed this video on YT (published 21/03/16), some of the comments also highlight they got issue with secure boot os type after windows update.

When I select "Other OS" note "Platform Key (PK) State" shows "Unloaded", when I select "Key Management" all keys are loaded.





I'm now thinking when I select "Other OS" technically Secure Boot is not functioning, the "Platform Key (PK) State" will only show "Loaded" on UEFI Screenshot 1 if "Windows UEFI Mode" is selected; which results in secure boot violation.

So how do I go about checking what is causing the secure boot violation? are the PK keys no longer valid for whatever update has occurred to OS?

I don't mind wiping install but do mind taking the time to reinstall updates 1 by 1 to see which creates the issue (if it is that).

[BobF64]

Um, Windows 7 does not support SecureBoot, and it should be turned off.

[watercooled]

Well the obvious answer is to not bother with secure boot.

But if you want it working, I guess it's possible windows update has changed something in the boot chain. I recall something similar happening with my Linx tablet when I was playing around with it. To fix it I think I had to re-load the PK to default - have you tried that?

Edit: Just realised you're talking about Win7 (brain fart), which as BobF64 doesn't support secure boot IIRC?

[gupsterg]

Guys for months on original install of Windows 7 Pro UEFI I had secure boot with os type as "Windows UEFI Mode" and "Platform Key (PK) State" as "Loaded". OS only ever had Agent's updates applied to it and none newer.

Then fresh install of Windows 7 Pro SP1 (with only Agent's updates applied to ISO) worked as well, settings as in first sentence of this post. Only until I applied newer updates, it showed image at system post in post 1. About the last 10 or so updates remaining in list, prior ones there was no such message (inc. reboots), now uninstalling those does not help .

I have deleted keys within UEFI and reloaded default (stored in UEFI) plus stored ones on USB, secure boot with os type as "Windows UEFI Mode" does not work. Only selecting "Other OS" (where keys are unloaded) works or full disable of secure boot.

[EHill]

I'm experiencing the exact same issue - on an ASUS Maximus Hero VII mobo - after the last set of MS updates (just did a fatal re-boot today). I bet MS solution involves "upgrading" to Windows 10. Very fryustrated as it's my main PC and is now bricked - hope disabling secure boot will fix the issue.

Just like gupsterg, my system had been running very stable for months with no changes to the BIOS.

Hope someone can find a solution - tech is so damn frustrating to me (and I've been in the field for a long time).

-Cheers.

[watercooled]

Maybe try contacting Asus support? As far as I know (though I couldn't stand and argue by any means, maybe there are bodges I'm not aware of) Win7 has never supported Secure Boot, so maybe something like a BIOS bug has allowed it to just appear as though it was functioning?

[BobF64]

Two things comes to mind, have you only ever used Windows 7 on the hard drive?
And did you let the Windows install partition the drive on the first install or did you do it yourself?

[gupsterg]

@EHill

Besides by solution posted in OP, the reason for why this occurred after recent MS updates is on ROG forum where I also started same thread , link to post.

@BobF64

I partitioned SSD manually via command line whilst installing Win 7 Pro, OP has a link to thread where there is information on how I installed UEFI Win 7 Pro few months back .

[BobF64]

So, therefore the answer is as previously stated, Windows 7 does not support Secure Boot and it should be turned off.

Why it worked before the update sounds like an unintended effect caused by ASUS configuring the BIOS with something they probably shouldn't have.

[gupsterg]

Yes, indeed UEFI of Asus was at fault.

Yes, Win 7 does not support secure boot.

At the time when I installed Win 7 UEFI as having secure boot enabled wasn't causing an issue (even though research showed not supported feature by OS) I used it.

KB3133977 heading "Known issues in this update" was updated to have correct info, "Last Review: 05/02/2016 16:22:00 - Revision: 5.0".