Windows 10: Why does a Secure boot window flash on and off very fast, Why?

A window will flash on and off very fast. I see Secure Boot in the window but that's all because it flashes very fast. My system is Asus AMD Athlon tm II x2 220 processor and my BIOS version/date Americian Megatrends inc. 0504. I'm using Windows Pro with 8 GB memory, My system information shows my Secure Boot State is Unsupported. My main questions is does this harm my system or cause it to be a security risk and if it's not a risk how do I Stop this window from appearing? Looking forward to hearing from you. Thanks in advance*Moved from feedback.

:)

 

Windows 8 Secure Boot Feature: Not So Secure?

• Linux
• Linux
• Linux
• Linux
• Oh and OSX

Here is a statement from a Kernal Developer at Red Hat:

I'm not sure this exploits the legacy BIOS but rather it exploits the legacy boot method on MBR drives, injecting a signed key before the OS boots, which you are correct in that it has nothing to do with Windows 8. And the simplest fix would just be to require boot drives use GPT when Secure Boot is enabled in UEFI.

 

Windows 8 Secure Boot Feature: Not So Secure?

So Linux is switching to secure boot also? Or they have to because of UEFI?

 

Windows 8 Secure Boot Feature: Not So Secure?

We have brought you the potential perils of the upcoming UEFI Forum-implemented - www.uefi.org - Windows 8 secure boot feature here, here and here. However, it appears that it may not be so 'secure' after all, since there appears to be a surefire way to circumvent it, at least for the moment, while it's in development.

Softpedia has scored an exclusive interview with security researcher Peter Kleissner, who has created various Windows (XP, Server 2003 etc) "bootkits", which allow OS infection at the highest privilege level, giving unrestricted access to the whole of the PC. His latest one, called Stoned Lite, shows how the Windows 8 secure boot process, still in development, can be subverted, as it stands. He is planning to release details of how the code works at the upcoming International Malware Conference (MalCon) - http://malcon.org - that will take place in India on November 25th. It appears that the real vulnerability exists in the legacy BIOS boot procedure, not in Microsoft's implementation of secure boot, as Kleissner said:

And as Softpedia put it:

Kleissner explained that the basic way Stoned Lite works is by using command line escalation:

So, this problem is only present if someone has physical access to the computer and is able to boot off a CD or USB stick. Therefore, this security vulnerability will have no impact in many scenarios where the threat of this kind of attack is very low. Examples include the home environment (usually) and data centres with very good physical security and the other measures they have in place. The most likely place for problems could be in workplaces where someone boots a PC after hours and installs a keylogger or other malware on the system. A significant threat, to be sure. However, despite this vulnerability, secure boot still makes conventional malware attacks useless, such as drive-by downloads from malicious or hacked websites and opening attachments from spam emails, among the many infection vectors around.

Still, it makes Microsoft's bold claim in September, that:

a little less reassuring, doesn't it?

Note that Kleissner will not be at MalCon in person, because he will be attending another conference held on the same day, the European Bitcoin Conference in Prague, where he will show "how to re-direct locally initiated BitCoin transactions, but also show how the BitCoin wallet can be secured better against theft." Therefore, someone else will go in his place to deliver the message, or he may pre-record it.

Finally, while this is a big step forward for PC security, like every other security improvement, there's always a hack to get around it with time somehow, somewhere, which can then be patched and hacked and patched... However, in this case, when the secure boot system goes live and a core vulnerability is found in the UEFI or some other low level component, patching won't be so simple, or maybe even impossible, due to its low level nature. So, once again the suspicion remains that this whole 'initiative' is a backdoor to locking out competing operating systems such as Linux and to DRM your whole PC to 'protect' the profits of big content, in a similar way they already do on games consoles.

There's a lot of big corporate interests riding on secure boot, so do not ever rule out the possibility that it will be subverted to further them.