UEFI boot logo shows up on windows loading screen in windwos 8?


Recommended Posts

I have a MSI board that has UEFI, I installed windows 8 on it for the first time (clean install) when the system boots it shows the MSI logo with the press DEL for Setup F11 for boot menu etc..... full screen bitmap image...

well when you go to the UEFI loading screen for windows with the looping circles at the bottom, where the windows logo use to be in windows 7 now is showing the UEFI Boot logo for the MSI board...

is it supose to do this? It's almost like MS assumed the UEFI boot logo is the company logo and nothing else will be shown there kinda like how apple does it with the gray apple logo on the OS load

of course the keys DEL and F11 do nothing while this is showing...

so instead of this...

post-47883-0-20922700-1351698105.png

you get somethign like this (i made this image up so its not entirely correct, no press buttons for are shown on it)

post-47883-0-23925200-1351698109.png

I can't answer your question, but I hope EVGA sorts out its EFI driver for the 670-cards soon so I can try it out myself! :)

Just did a quick search because i wasn't sure what you were talking about, it looks like there is a problem with EFI booting on some Nvidia cards, but it only looks like a OSX Lion issue?

I also on that same system every so many seconds it makes that ding noise like it found new hardware... its been doing that for an hour now... almost like its changing hardware drivers one at a time... reboot didn't fix it..

of course no notifications of new hardware, nothing in the system tray showing the hardware found icon, nothing showing as changing in device manager while watching that...

I think that is by design. I turned off the boot logo on my ASUS board.

turning off the boot logo does nothing, still shows that image on the boot of windows

Just did a quick search because i wasn't sure what you were talking about, it looks like there is a problem with EFI booting on some Nvidia cards, but it only looks like a OSX Lion issue?

Nah, it's disabled in their current firmware because they haven't been able to verify stability with all motherboards... or something of the sort. They've apparently implemented some necessary bits but still waiting. :D

MSI claims they made windows 8 :p

But I think this might be fixed with a bios firmware upgrade?

I think MS is somehow reading the UEFI boot logo as the vendor logo, maybe MSI hasn't but a vendor logo in yet or something and its just taking the boot logo as the vendor logo?.. going to have to post on the MSI forum about this

Seems like most UEFI boards are doing this. Not sure how to disable it, but it doesn't bother me as the ASUS ROG Logo is nice and simple. I would go nuts though if I had to look at that obnoxious ****. OMG MILITARY QUALITY, DON'T YOU FEEL SPECIAL! LOLZ! :p

  • Like 2

Windows 8 allows the hardware manufacturer to customize the boot experience. I believe it's even the UEFI that draws it through the whole process (not the progress spinner itself though).

Seems like most UEFI boards are doing this. Not sure how to disable it, but it doesn't bother me as the ASUS ROG Logo is nice and simple. I would go nuts though if I had to look at that obnoxious ****. OMG MILITARY QUALITY, DON'T YOU FEEL SPECIAL! LOLZ! :p

As someone who also owns an Asus ROG board, I haven't seen that in Windows 8 and I used UEFI. Do you have to turn it on in the BIOS?

As someone who also owns an Asus ROG board, I haven't seen that in Windows 8 and I used UEFI. Do you have to turn it on in the BIOS?

Same but using a Sabertooth Z77 board on version 1616. I'd like to know as well

As someone who also owns an Asus ROG board, I haven't seen that in Windows 8 and I used UEFI. Do you have to turn it on in the BIOS?

I saw it on my rampage IV for the first time after updating my bios about 2 months ago.

Ironically just got a new bios available notification from MSI... and it now has a "Windows 8" bios configuration section, and when you turn that on, the Military class blah blah logo is replaced by just "MSI" and enables Graphics Output Protocol video modes instead of UGA

Yep, I get the mobo logo too now, after I updated my BIOS to support Windows 8 UEFI. Thankfully, AsRock has a smallish green logo, and not a gigantic in-your-face logo.

Sadly, my graphics card (EVGA 680 GTX) doesn't support UEFI-GOP, so I can't do the ultra-fast boot option. According to their forums, EVGA plans on releasing an optional firmware upgrade to enable it in their 6xx lineup...

Oh! That explains why Surface displays the word "Surface" on the boot screen instead of the new Windows logo.

At least, that's what I've observed in videos... I don't have one (yet!).

  • 2 weeks later...

Oh! That explains why Surface displays the word "Surface" on the boot screen instead of the new Windows logo.

At least, that's what I've observed in videos... I don't have one (yet!).

Yea..even Samsung's Intel based Series 7 tablets (or w/e that tablet was that was given out at last year's build) does that.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!