How do you revert the windows 10 boot menu from GUI mode to text mode?


Recommended Posts

This is really frustrating, the windows 10 GUI boot menu refuses to load my mouse or keyboard drivers so I can't pick which OS to boot from. I've tried disabling the GUI boot menu and going back to the classic text menu boot screen but windows 10 seems to decide when it wants to boot the GUI or text mode, about 1 in 10 times it'll load the text mode menu and 9/10 times the GUI boot menu.

I used BCDEdit to set it to use the text menu but it just completely ignores it. So how do I fix this damn annoying bug and just have the text boot menu always?

 

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  en-GB
inherit                 {globalsettings}
default                 {current}
resumeobject            {4f94dff9-91f6-4de5-aefd-911547258079}
displayorder            {current}
                        {4f94dff9-91f6-4de5-aefd-911547258079}
toolsdisplayorder       {memdiag}
timeout                 5
displaybootmenu         No

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-GB
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {4f94dff9-91f6-4de5-aefd-911547258079}
nx                      OptIn
bootmenupolicy          Legacy
hypervisorlaunchtype    Auto

Windows Boot Loader
-------------------
identifier              {4f94dff9-91f6-4de5-aefd-911547258079}
device                  partition=D:
path                    \Windows\system32\winload.efi
description             Windows 7
locale                  en-GB
inherit                 {bootloadersettings}
recoverysequence        {4f94dff9-91f6-4de5-aefd-911547258079}
recoveryenabled         Yes
osdevice                partition=D:
systemroot              \Windows
resumeobject            {4f94dff9-91f6-4de5-aefd-911547258079}
nx                      OptIn
bootmenupolicy          Legacy

Have you tried enabling legacy devices in your BIOS? That's what I had to do to get my keyboard to work when booting up. Otherwise it didn't work unless I used a PS/2 Keyboard (My mobo doesn't have that port anymore D: )

  On 01/12/2015 at 11:30, BinaryData said:

Have you tried enabling legacy devices in your BIOS? That's what I had to do to get my keyboard to work when booting up. Otherwise it didn't work unless I used a PS/2 Keyboard (My mobo doesn't have that port anymore D: )

Expand  

Legacy mode is enabled in my BIOS by default. It's probably a BIOS firmware issue though because once I power my PC off, USB devices aren't properly powered off, i.e. mouse LED stays on.

  On 01/12/2015 at 11:31, n_K said:

Legacy mode is enabled in my BIOS by default. It's probably a BIOS firmware issue though because once I power my PC off, USB devices aren't properly powered off, i.e. mouse LED stays on.

Expand  

Is it an older Motherboard? My old Intel LGA775 Motherboard left all the Lights on. Drove me insane. I ended up switching the power on the PSU off at night, otherwise all my case fan LEDs would stay on. =/

Hello,

 

Just to confirm, you ran a

bcdedit /set {default} bootmenupolicy legacy

command from an elevated Command Prompt to initially set the boot menu policy, correct?

 

Regards,

 

Aryeh Goretsky

 

Yes I used an elevated command prompt.
I was wrong - this issue isn't fixed, setting displaybootmenu to yes hasn't resolved it, sometimes it will be a GUI boot menu, other times it will be text based...

Hello,

 

It seems strange to me that the computer would randomly display GUI and text boot menus. 

 

Is more than one operating system installed on the computer?  If so, perhaps its boot manager is interfering.

 

Regards,

 

Aryeh Goretsky

 

It's UEFI with rEFInd as the main bootloader, one option is for linux and the other is for windows, this then chainloads the windows bootloader which shows windows 10/windows 7 but flips randomly between text/GUI mode.

Hello,

 

I am thinking it is some sort of compatibility issue with rEFInd.  Do you have another disk drive you can wipe, install into the computer, and partition only with Windows 10 and then try changing the boot configuration with bcdedit to see if that makes any difference?

 

Regards,

 

Aryeh Goretsky

 

  • 3 months later...

For anyone with the same issue, the problem is not windows 7, it's not linux and it's not refind: it's windows 10. To be more precise it's fast boot in windows 10.

To resolve the issue, you need to disable the fast startup option which you do by fully disabling hibernate, from an admin command prompt: powercfg /H off

  On 03/04/2016 at 14:52, xendrome said:

BTW try making sure your mouse/keyboard are not plugged into USB 3.0 ports, that might fix the boot GUI keyboard/mouse issue.

Expand  

They're all in USB 2.0 ports, I only have one front USB 3.0 port. As said though, in text boot mode the keyboard works flawlessly, in GUI boot mode neither the mouse or keyboard work until windows has booted. Resolved anyhow with fast startup disabled!

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

    • No registered users viewing this page.
  • Posts

    • Now I may not quite understand this, so someone tell me if I'm off the mark here, but does this mean they'll be potentially removing drivers for now unsupported systems, such as old processors and chipsets? In the past 15 years, Windows has been amazing at just installing on any device, and often having zero, or just a few unessential drivers missing on first install. It would be a shame for that experience to go, though I understand the reasoning, or at least their financial reasoning for it!
    • Microsoft is removing legacy drivers from Windows Update by Usama Jawad Last month, we learned that Microsoft is making major changes to the development of hardware drivers in Windows. This included the retirement of Windows Metadata and Internet Services (WMIS), along with the process for pre-production driver signing. Now, the Redmond tech firm has informed partners that it will be getting rid of old drivers in Windows Update. In what is being described as a "strategic" move to improve the security posture and compatibility of Windows, Microsoft has announced that it will be performing a cleanup of legacy drivers that are still being delivered through Windows Update. Right now, the first phase only targets drivers that already have modern replacements present in Windows Update. As a part of its cleanup process, Microsoft will expire legacy drivers so that it is not offered to any system. This expiration involves removing audience segments in the Hardware Development Center. Partners can still republish a driver that was deemed as legacy by Microsoft, but the firm may require a justification. Once the Redmond tech giant completes its first phase of this cleanup, it will give partners a six-month grace period to share any concerns. However, if no concerns are brought forward, the drivers will be permanently eradicated from Windows Update. Microsoft has emphasized that this will be a regular activity moving forward and while the current phase only targets legacy drivers with newer replacements, the next phases may expand the scope of this cleanup and remove other drivers too. That said, each time the company takes a step in this direction, it will inform partners so that there is transparency between both parties. Microsoft believes that this move will help improve the security posture of Windows and ensure that an optimized set of drivers is offered to end-users. The firm has asked partners to review their drivers in Hardware Program so that there are no unexpected surprises during this cleanup process.
    • No idea, but I had a client the other week that lost the entire drive to it. I suggested relying on the Samsung T7's instead. The Sandisk Extreme's had reliability issues too.
    • I use it every day so personally yes I need it, or rather I want it. I use OpenShell though, not the garbage modern Start Menu. I just counted and at the moment I have a total of 92 program shortcuts organized into six folders almost exactly the way I did back in Windows 95. I can get to any program I want to run very quickly. I never use Search to find or run programs.
    • I do miss the Apps view from Windows 8.1 Update.
  • Recent Achievements

    • One Month Later
      KynanSEIT earned a badge
      One Month Later
    • One Month Later
      gowtham07 earned a badge
      One Month Later
    • Collaborator
      lethalman went up a rank
      Collaborator
    • Week One Done
      Wayne Robinson earned a badge
      Week One Done
    • One Month Later
      Karan Khanna earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      682
    2. 2
      ATLien_0
      274
    3. 3
      Michael Scrip
      220
    4. 4
      +FloatingFatMan
      171
    5. 5
      Steven P.
      160
  • Tell a friend

    Love Neowin? Tell a friend!