Unsolved

This post is more than 5 years old

1 Rookie

 • 

60 Posts

880355

October 7th, 2013 09:00

Windows 8.1 Pro Update Causing "SecureBoot isn't configured correctly" Watermark

Guys, how do I legitimately stop this watermark from showing up? I am booting with UEFI right now but Secure Boot is disabled (gray'd out so I can't even modify this option). I tried doing a Legacy boot, but this doesn't work...this just gives me an error about rebooting and selecting a proper boot device (I'm not sure why this doesn't work either, because I'm selecting it to boot from my hard drive in legacy boot mode). Also, since I just updated to Windows 8.1 Pro from Windows 8 Pro, I'm not sure why I started seeing this watermark, because it was not there before. Anyone have any ideas what's causing this and how to get around it?

Computer

Aurora R4, A09 Bios

October 19th, 2013 15:00

Also having this issue, I've gone into the BIOS to try and enable Secure Boot and it won't allow me to change the setting. I hope this fix comes sooner than later, it's mostly annoying.

I have an Aurora R4, A09 BIOS as well.

4 Posts

October 19th, 2013 18:00

I only posted what worked for me. NO I didn't read all the comments in this forum. I found this forum by googling my problem. Once I fixed my problem, I simply shared it with everyone else. I will no longer do so. If you never figure out your issue will be fine for me. Anger indented.

1 Message

October 19th, 2013 18:00

This a neat write up except mine does not have enhanced boot configuration data validation profile there.  Under F2 it will nor change.  My computer is an xps8500 which came with Windows 8

4 Posts

October 19th, 2013 18:00

Have you tried reset to factory defaults?

1 Rookie

 • 

60 Posts

October 19th, 2013 19:00

Guys, for people such as myself with an Alienware Aurora R4 and two Radeon HD 7950s that experience the gray secure boot option, we just need to wait for a fix from Dell as the Dell representative previously stated:

In some of the cases SECURE BOOT is greyed out in the BIOS. You can continue to use system normally with no impact on performance. Engineering is aware of this issue and resolution will be shared shortly.

I agree with C0debreaker though. Secure Boot is a UEFI feature that's been out for awhile now...the BIOS issue with it being grayed out should have been addressed well back in Windows 8 bcause even then secrue boot was broken in the BIOS. Now it's strictly being enforced in 8.1 and this skeleton just got resurrected. As a sidenote, some of you guys have been wondering how some users came to the conclusion that this is a video card error...well to confirm it for yourselves, if you try to boot and use F12 to access your boot options you can try to start with secure boot enabled from there (this is not the same as F2 which accesses BIOS options, because F12 sets BIOS boot options only for the current "boot instance" - basically like BIOS options, but one-time, and with more verbose error logging). Now, that being said, the error might be due to graphics cards not being UEFI compliant, but I mean, these cards we purchased from you guys at Dell and they're pretty damn new. Really not sure why secure boot on the BIOS even relies on graphics cards to be UEFI compliant, or what that even entails for cards.

Here is what this site (http://forums.tweaktown.com/gigabyte/54668-win-8-1-secure-boot-isnt-configured-correctly-water-mark-not-able-access-bios-after-enable-secure-boot.html) says about it:

I haven't seen a solution to fix that yet other than:
- use the internal Intel IGFX . Enabling it (not "Auto" but "Enable") in the bios and you monitor connected to it)
- or ask your manufacturer to provide you a GOP vBIOS (if you are lucky enough)
- or to buy a compatible graphic card (only a few one can at the moment).

So, Dell, I guess you guys should give us a Graphics Output Protocol compatible Video BIOS, no?

1 Rookie

 • 

60 Posts

October 19th, 2013 20:00

Found out more about how secure boot works from here: http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c03653200

Problem is:

-  Legacy boot does not work on my PC without having to reformat Windows. I am locked into UEFI boot with no way of enabling secure boot.

- Dell, is your BIOS really "sure" that the 7950 graphics card that shipped with my system is NOT UEFI compliant? Keep in mind how new it is.

- Shouldn't there be a way to recreate the secure boot keys once you refresh your hardware like, add a new graphics card, without having to reformat your PC?

1 Message

October 20th, 2013 02:00

I'm really unsure why everyone is losing their minds over a watermark on their desktop, if you're one of those who just cant live with a little software bug, perhaps you shouldn't update to a new version of an OS the day it's released (but alas, those too impatient to wait a week or two to upgrade are often bound to be too impatient to wait for a bug fix). There are many, many worse issues that could have come up... it's a watermark... As Chris M said, Microsoft is aware of this little bug, as are OEM's. Rather than rage, complain, and repost things how about we be productive and give them the necessary info to address the issue, eh? A fix will come. 

Anyways, Chris M I'm patiently waiting to hear about a fix for the watermark. I've got it as well, and though it makes my entire PC nigh unusable because it imposes on my background image, I think I can live with it for a while... lol. In the meantime i'll just add my system specs to the list to help with the issue. I have the same issue as most; Alienware X51 with GTX 555, enable secure boot is greyed out, cannot disable "Enable Legacy OPROM" to allow secure boot either. Cheers.

1 Message

October 20th, 2013 03:00

I couldn't change anything in BIOS settings until I changed the security password which is the first option under Security settings.

This was on my Acer laptop.

5 Posts

October 20th, 2013 10:00

I have experienced the same problems as others with my X51 with none of the fixes working and the option to enable secure boot is greyed out running A12 bios

I will check this thread regularly for any news about a fix 

1 Message

October 20th, 2013 17:00

I have a Dell XPS 8500 (new Summer 2012), originally W7 Home Premium, upgraded to W8 Pro Media (Jan 2013), and once again updated to 8.1 Pro Media without the Watermark.

Another Dell Desktop GX520, an old XP machine.  It was updated to W8 - 32 bit last January.  It was updated to 8.1 Pro without incident, however the ACER V5 notebook [OEM W8] updated to 8.1, the Watermark appeared on the START Screen.  I created a BIOS Password and Enabled "SecureBoot". It made no difference. 

1 Rookie

 • 

60 Posts

October 21st, 2013 08:00

I'm really unsure why everyone is losing their minds over a watermark on their desktop, if you're one of those who just cant live with a little software bug, perhaps you shouldn't update to a new version of an OS the day it's released (but alas, those too impatient to wait a week or two to upgrade are often bound to be too impatient to wait for a bug fix). There are many, many worse issues that could have come up... it's a watermark... As Chris M said, Microsoft is aware of this little bug, as are OEM's. Rather than rage, complain, and repost things how about we be productive and give them the necessary info to address the issue, eh? A fix will come. 

Anyways, Chris M I'm patiently waiting to hear about a fix for the watermark. I've got it as well, and though it makes my entire PC nigh unusable because it imposes on my background image, I think I can live with it for a while... lol. In the meantime i'll just add my system specs to the list to help with the issue. I have the same issue as most; Alienware X51 with GTX 555, enable secure boot is greyed out, cannot disable "Enable Legacy OPROM" to allow secure boot either. Cheers.

I guess if you bought yourself a Ferrari, drove it for awhile, then bought brand new tires for it from the same tire manufacturer because they have better performance, and every time you hit the gas after the tire swap your odometer would consistently triple the number of kilometers it shows you traversing, it wouldn't bother you?

I guess if...you bought anything while thinking of the future with the thought of upgradability in mind, it wouldn't bother you if a "feature" of that product was broken already, but you only found out about that feature being broken after upgrading it...I guess that wouldn't bother you.

It would bother me.

353 Posts

October 21st, 2013 09:00

Wow nobody can keep the topic online in here amazing. 

31 Posts

October 21st, 2013 12:00

Agree 100%. Saying those of us who have this problem should just not worry about it is inappropriate and insulting.

Simply stated, it is not anyone else's place to tell *me* how *I* should feel about a *defect* in a product *I paid my good $ for*, no matter how minor or insignificant he might feel the defect to be. To anyone who has this advice to me, my advice to you is in turn to [expletive deleted].

And yes, Dell should be monitoring this thread, and keeping us posted.

3 Posts

October 21st, 2013 12:00

Agreed.

qklein's response does not help anyone - regarding the watermark (that is subjective, if you bought a car and an invalid maintenance message in red was on your dash, you'd probably be annoyed (or not), but the point is, free world, clearly it is bothering a ton of folks).  The frustration is simply the limited responsiveness from Dell.  For those that are non-technical, it is disconcerting to them as they do not know if something is actually wrong.  Since the numbers of folks impacted are so large, Dell could assist by providing a notice directly on their Home support page stating that they are working with Microsoft on it and will post any resolution).  Not a big deal, but would illustrate good customer support.  I guess despite the PC market declining, they are not worried about the loyalty market share from current owners...


I am not sure about him (or her), but many of us made a large investment in our high end PCs.  Whether the machine is bricked or whether it is a simply watermark, we do deserve a non-scripted response, even if it is, "we are working on it, will post here when a solution is known or if we have more information on timing".  It also would not help if they checked in occasionally if it is going to take a long time. 

BTW - Maybe someone should tell PC World that qklein decided they are wasting space making a big deal out of this...http://www.pcworld.com/article/2056292/windows-8-1-launch-weekend-plagued-by-some-show-stopping-installation-issues.html

Dell should be moderating...

That said, Aurora R4 - GTX 770 - Does not support GOP so enabling SecureBoot only leads to a black screen on reboot until it is turned back off (applies to legacy as well).  And yes, I can be patient as well. 

353 Posts

October 21st, 2013 12:00

I agree 100% where is the input from dell when is this going to be fixed i'm so tired of this. 

No Events found!

Top