Enabling UEFI Boot Support on Compaq

Hi, I purchased a Compaq CQ5300Y a long time ago, and since it has been sitting in the corner of my room for so long, I decided to try and put Steam OS on it, because it just came out. So I got as far as plugging my USB drive into the computer, and it will not boot onto it because I need UEFI Legacy or something.
I was wondering if there are any updates to BIOS for UBUNTU that I may need to get to enable this, or if there is some setting that I missed in the BIOS.
Thanks,
Kyle

Here are the specs for your Compaq Presario CQ5300Y Desktop Computer. Based on the specs, this model shipped with Windows 7 installed and is about 4 years old. Your computer is a "Legacy" computer and only supports a traditional BIOS. This model will never support UEFI, Secure Boot, etc. There are no BIOS updates available for this model under any operating system.
If you have any further questions, please don't hesitate to ask.
Please click the white KUDOS star to show your appreciation
Frank
{------------ Please click the "White Kudos" Thumbs Up to say THANKS for helping.
Please click the "Accept As Solution" on my post, if my assistance has solved your issue. ------------V
This is a user supported forum. I am a volunteer and I don't work for HP.
HP 15t-j100 (on loan from HP)
HP 13 Split x2 (on loan from HP)
HP Slate8 Pro (on loan from HP)
HP a1632x - Windows 7, 4GB RAM, AMD Radeon HD 6450
HP p6130y - Windows 7, 8GB RAM, AMD Radeon HD 6450
HP p6320y - Windows 7, 8GB RAM, NVIDIA GT 240
HP p7-1026 - Windows 7, 6GB RAM, AMD Radeon HD 6450
HP p6787c - Windows 7, 8GB RAM, NVIDIA GT 240

Similar Messages

  • [SOLVED] Removing archiso's UEFI boot failed using xorriso

    I'm trying to remove UEFI boot support of the latest archiso since I have to boot the install CD on my MacBook2,1 (which doesn't support UEFI, only supports 32-bit EFI).
    I follow this guide but this is the xorriso output:
        libburn : SORRY : Neither stdio-path nor its directory exist
        xorriso : FAILURE : Cannot aquire drive 'stdio:~/archiso.iso'
        xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
    Can anyone help me with this?
    Last edited by mirakulous (2013-05-30 09:34:04)

    Hi,
    as upstream programmer of xorriso i would really appreciate
    to see this fixed in the wiki ... or yielding a bug report
    if xorriso is to blame.
    I tried the following with success on my quite outdated
    GNU/Linux system:
    $ wget http://mirror.de.leaseweb.net/archlinux … 1-dual.iso
    # mount -o loop /dvdbuffer/archlinux-2013.05.01-dual.iso /mnt/iso
    $ xorriso -as mkisofs -iso-level 3 \
        -full-iso9660-filenames\
        -volid "ARCH_201305" \
        -appid "Arch Linux CD" \
        -publisher "Arch Linux <https://www.archlinux.org>" \
        -preparer "prepared like a BAWSE" \
        -eltorito-boot isolinux/isolinux.bin \
        -eltorito-catalog isolinux/boot.cat \
        -no-emul-boot -boot-load-size 4 -boot-info-table \
        -isohybrid-mbr "/dvdbuffer/archlinux-2013.05.01-dual.iso" \
        -output "$HOME/archiso.iso" "/mnt/iso/"
    (I do not have SYSLINUX development installed, but the ISO image
    bears a suitable -isohybrid-mbr template at its start. So i use
    that one.)
    This yields
      GNU xorriso 1.3.0 : RockRidge filesystem manipulator, libburnia project.
      xorriso : UPDATE : 107 files added in 1 seconds
      xorriso : NOTE : Copying to System Area: 32768 bytes from file '/dvdbuffer/archlinux-2013.05.01-dual.iso'
      libisofs: NOTE : Aligned image size to cylinder size by 55 blocks
      Written to medium : 260608 sectors at LBA 0
      Writing to 'stdio:/home/thomas/archiso.iso' completed successfully.
    The original ISO reports on inquiry of its content
      $ xorriso -indev  /dvdbuffer/archlinux-2013.05.01-dual.iso -toc
      Boot record  : El Torito , ISOLINUX isohybrid MBR pointing to boot image
      Boot catalog : '/isolinux/boot.cat'
      Boot image   : '/isolinux/isolinux.bin' , boot_info_table=on
      Boot image   : '/EFI/archiso/efiboot.img' , platform_id=0xEF
    The repacked one reports no EFI boot image that is reachable
    via El Torito
      $ xorriso -indev /home/thomas/archiso.iso -toc
      Boot record  : El Torito , ISOLINUX isohybrid MBR pointing to boot image
      Boot catalog : '/isolinux/boot.cat'
      Boot image   : '/isolinux/isolinux.bin' , boot_info_table=on
    If this does not work for archlinux users, then please tell
    me the version of xorriso that fails, the necessary preparations,
    the program arguments used, and the messages of xorriso.
    Have a nice day
    Thomas

  • GT60 0ND is Impossible UEFI Boot Oprion?

    GT60 0ND is Impossible UEFI Boot Oprion?
    Hi 
    I have a GT60 0ND , and my OS is Windows 8 Enter X64
    Mainboard:  MS-16F3
    PCB Version:  REV:1.0
    BIOS Version: E16F3IMS.30S
    BIOS Date:  2012-12-27
    EC-FW Version:  16F3EMS1.504
    To know about how to update win8 BIOS under UEFI mode, please click here.
    When going into the bios, I dont have the following option
    Under Security tab, look for the option ”Secure Boot” and set it to ”Disabled”
    Can I unlock bios UEFI boot?

    Quote from: guwer on 30-January-13, 09:38:34
    GT60 0ND is Impossible UEFI Boot Oprion?
    Hi 
    I have a GT60 0ND , and my OS is Windows 8 Enter X64
    Mainboard:  MS-16F3
    PCB Version:  REV:1.0
    BIOS Version: E16F3IMS.30S
    BIOS Date:  2012-12-27
    EC-FW Version:  16F3EMS1.504
    To know about how to update win8 BIOS under UEFI mode, please click here.
    When going into the bios, I dont have the following option
    Under Security tab, look for the option ”Secure Boot” and set it to ”Disabled”
    Can I unlock bios UEFI boot?
    Did your notebook come with Windows 7 or Windows 8 installed ORIGINALLY?
    If it came with Windows 7, there is no way to enable UEFI booting.....which explains why you can't see that option....

  • How to Enable Secure Boot on UEFI Systems?

    SymptomsWhen attempting to enable Secure Boot, the system does not allow you to select the option to enable or disable Secure Boot.  This is due to the way Acer's UEFI implementation requires a Supervisor Password be set in order to access this option.
    UEFI is a newer technology that replaces the older standard BIOS.
    DiagnosisCreating a Supervisor Password in UEFI will allow you to access the Secure Boot options. It is important that you remember this password as it will be required to make any changes in the UEFI interface.
    SolutionCreate a Supervisor Password to gain access to the Secure Boot option. 
    Refer to our FAQ for all the steps on how to access Secure Boot on Desktops, Notebooks, and Tablets:
    Enable or Disable Secure Boot in Windows 8

    Das macht man 2-3 mal und dann ist nix mehr mit Bios. Dann kommt Passwort ist falsch und das war's dann. Hab ich schon auf verschiedenen Lappis gehabt. Sprich TOSHIBA... und Aspire E1-571g. Beim Toshi den Baustein ausgelötet neuen gekauft, beschrieben und wieder eingelötet. Kostet schlappe 150,-€. Mal schauen was beim Acer rauskommt.Vielleicht gibt es ja noch einen Jumper um das UEFI BIOS zurückzusetzen

  • Windows Server 2012 R2 Will Support for UEFI boot in WDS.

    Hi
    Currently we had issue in WDS while deploying the image via UEFI boot in the DELL Optiplex 3010. We already deployed the Windows 8 install image and boot image in the Windows Server 2012 R2. After selecting the Network boot its show Start PXE IPV4 and it
    will immediately flicker and get back to Network Boot option. Any one please help me out of this.....
    But the same is working in Legacy boot and it doesn't activate the Windows 8.

    Hi,
    As I cannot confirm the exact settings on your side, please see the suggestions provided in following thread:
    WDS: EFI BIOS won't PXE boot into EFI mode
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/wds-efi-bios-wont-pxe-boot-into-efi-mode?forum=winserversetup
    The same issue is discussed a lot in this thread and several possible suggestions are provided. See if it is helpful. If there is anything unclear please just let us know. 
    If you have any feedback on our support, please send to [email protected]

  • UEFI Booting/ Enabling BIOS Features

    Hello,
    I have a Lenovo G475 laptop and I would like to know how to enable the (U)EFI mode in the BIOS menu and is it possible to access advanced features?
    I want to UEFI boot an operating system.
    InsydeH2O
    BIOS Version: 41CN24WW(V2.00)
    EC Version:   41EC24WW(V2.00)
    Thank you.

    hi lks1981,
    Welcome to the Lenovo Community.
    The Lenovo G475 only have the old Basic Input/Output System (BIOS) and doesn't have a UEFI as an additional option. Until such time Lenovo allows flashing of the BIOS to convert it to UEFI, you can't yet enable this option.
    If you want to transform the BIOS to UEFI (to allow booting from HDD's larger than 2TB and up to 128 partitions or mix MBR with GPT type partitions) , you can try to use Developer's UEFI Environment (DUET), you can find more info here - http://tinyurl.com/d9owxqr
    Hope this helps.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Uefi - enable 'legacy boot' option - discarded at reboot

    trying to boot into any non-system 'external media'
    fails when I enable 'legacy boot' option
    tried removing battery - 20 second power off
    reboot and find setting reverted or blank screen -
    manual forced 'bios recovery' (win+b)
    magic key combos?
    bios ver [F.10]

    HI @rolithiums 
    Thank you for your inquiry, I will do my best to help.
    I grasp you are having a difficulty changing the boot order.  Here is a link to  Configuring Boot Order that will assist you.
    Good Luck!
    Sparkles1
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

  • Satellite C50-B with Win 8.1 - PXE error appeares using UEFI boot mode

    I have a C50-b laptop running Win 8.1 and recently needed to boot it from a usb key so eventually found the way to do that (miss the bios first boot menu) and managed to do that.
    My problem is even when I have returned to uefi and set the boot order to be local disk, cd, network it asks everytime do I want to boot for PXE IP4,IP6 then IP4 and IP6 again. I have also disabled secure boot
    I think some value is missing when I switched to BIOS and back to UETI boot option but where is the laptop getting the setting to tell it to PXE/Network boot when its down the list and wake on LAN is disabled.

    According to the automated support on the site I should do the following for Win 8
    Switch on the notebook and immediately begin tapping the F2 key continuously.
    When the system setup (BIOS) appears, stop tapping F2. Tap F9 once, select 'Yes', and press Enter.
    Use the cursor keys to move to the Advanced menu.
    Choose System Configuration and press Enter.
    Ensure that Boot Mode is set to UEFI Boot.
    Press Escape to return to the Advanced menu and choose the Security menu.
    Set Secure Boot to Enabled.
    Press F10 once, select 'Yes', and press Enter.

  • Windows 8.1 Ent eval enabled Secure Boot I think

    I want to get my laptop back to its original format.
    Currently dual booting Windows7/8.1
    During the installation of Windows 8.1 Enterprise evaluation it paused to say it was going to enable secure boot.  I did'nt think much of it I thought I could change it back from the bios.  Did it flash my firmware?  I checked the system status
    with msinfo32.exe; was legacy mode and with powershell; secure boot not supported.  I don't have any options to disable secure boot in the bios nor from within Windows -"I know how to disable it in windows 8.1".  I can't boot a foreign
    operating system, but I can boot a Microsoft OS which sounds like secure boot to me.  I want to get it back to running Windows 7 dual booting with Linux.  I use both at work and need both.  I made the mistake by loading the Eval on my primary
    laptop.  I read I need to revert back to Windows 7 completely, formating and re-installing the OS.  Will this clear my secure boot simulation issue?  I have not changed the partitions or removed any O/S's.   What's the best way
    to proceed?

    Hi,
    I want to explain that, Secure Boot is indepent with system, you can disable it in UEFI interface.
    To disable Secure Boot, you can follow the steps below:
    1.Before disabling Secure Boot, consider whether it is necessary. From time to time, your manufacturer may update the list of trusted hardware, drivers, and operating systems for your PC. To check for updates, go to Windows Update, or check your manufacturer's
    website.
    2.Open the PC BIOS menu. You can often access this menu by pressing a key during the bootup sequence, such as F1, F2, F12, or Esc.
    Or, from Windows, hold the Shift key while selecting Restart. Go to Troubleshoot > Advanced Options: UEFI Firmware Settings.
    3.Find the Secure Boot setting, and if possible, set it to Disabled. This option is usually in either the Security tab, the Boot tab, or the Authentication tab.
    4.Save changes and exit. The PC reboots.
    I found an aticle that teach how to install dual-boot Windows 7 and Ubuntu 12.04 on a PC with UEFI hardware:
    http://www.linuxbsdos.com/2012/10/11/dual-boot-windows-7-and-ubuntu-12-04-on-a-pc-with-uefi-hardware/
    Hope this helps.
    Roger Lu
    TechNet Community Support

  • MB BIOS 2.2TB MBR limitation: Can add-on drive controller BIOS enable UEFI/GPS on a non-bootable data drive?

    I am working on older hardware that is not UEFI enabled so it is subject to the 2.2TB volume limitation under Windows Server 2012 R2 resulting in 11.6TB of unusable drive space. I installed an Adaptec Series 7 2274500-R 71605E controller card and created
    a striped RAID 10 totalling 13.6 TB of drive space. During boot, the Adaptec BIOS is installed on the system, which prompts the following question:
    Since the boot utilizes the motherboard BIOS, clearly the boot partition cannot exceed the 2.2TB limit. But what about a separate logical data drive? If I shrink the boot partition to 1TB, create a second volume at RAID level of 12.6TB formatted with GPT
    NTFS, would the Adaptec BIOS enable UEFI/GPT (since the MB BIOS would not boot to the second logical drive) and Windows Server see the full 12.6TB second drive volume?
    Yes, I am aware that I can create multiple 2.2TB partitions, but that would be an inefficient option for this installation.
    Any thoughts or suggestions will be greatly appreciated.
    Thanks!

    Hi,
    According to your description, my understanding is that you want to use add-on drive controller to enable UEFI/GPS on a non-bootable drive.
    In order for an operating system to fully support storage devices that have capacities that exceed 2 TB, the device must be initialized by using the GUID partition table (GPT) partitioning scheme. If the user intends to start the computer from one of these
    large disks, the system’s base firmware interface must use the Unified Extensible Firmware Interface (UEFI) and not BIOS. Windows support for hard disks that are larger than 2 TB, and there are some prerequisites are needed.
    Detailed information reference link:
    https://support.microsoft.com/en-us/kb/2581408
    Best Regards,
    Eve Wang
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Enabling CD boot G780

    Hi guys
    I have a G780 and i need to boot it from CD but i just can't seem to find a way to enable it.
    My CD/DVD drive is recognised in the "information" section of the bios but on the "boot" section it doesn't show up, all there is is the hard drive and 2 EFI networks listed. (Also if i press F12 during start up i only get the hard drive and EFi network options too)
    What sequence of things in the bios do i need to tweak so that i will be able to boot from cd?
    Thanks in advance.

    Windows 8 computers have UEFI firmware, but include a compatibility support module (CSM) that is set up to use the legacy version of BIOS.
    The UEFI firmware supports two boot modes: UEFI boot mode and Legacy BIOS boot mode.
    The UEFI firmware settings determines what type of boot devices are available in the boot menu: UEFI, Legacy BIOS, or both types of boot devices.
    I have a Lenovo G580 with UEFI firmware.
    When the default "UEFI boot mode" and "Secure Boot" settings are enabled in the UEFI firmware.
    You can boot from the following devices:
    - Windows 8 64-bit DVD
    - Windows 8 64-bit FAT32 USB flash drive (see screenshot below)
    Link to image
    But you can't boot from the following devices:
    - Windows 8 64-bit NTFS USB flash drive
    - Windows 8 32-bit DVD/USB
    - Windows 7 32/64-bit DVD/USB
    Here is more info:
    http://www.eightforums.com/installation-setup/39909-clean-installs-new-ssd-s-getting-8-0-8-1-a-2.htm...
    Moderator note: large image(s) converted to link(s):  About Posting Pictures In The Forums

  • Request MSI GX640 UEFI boot bios mod

    Hello I was wondering if someone could help me re-enable the UEFI Boot option in the latest MSI GX640 bios version E1656IMS.10F
    Also is it possible to add SSD support in AHCI mode as well, because currently I can not get an ssd to boot in that mode. It only works in IDE mode for some reason.
    I would also like it to be fully unlocked.
    Thank you!

    Alright cool. The reason I asked about the UEFI Boot feature is because it was enabled in the original BIOS, but they disabled the feature in a BIOS update because when the feature was enabled it would cause the system to hang when booting from a CD/DVD.
    I bought this Dell AMD HD 7970m GPU for my GX640 and I found out that it is a UEFI card that doesn't have a legacy vBIOS, and after I installed it, my laptop would not post and I got a black screen. I was thinking that if I had that UEFI Boot feature back, then my computer would boot with the GPU installed in it. Please correct me if I am wrong, and please let me know if some sort of BIOS mod would make this GPU work in my GX640.

  • How to enable hardware virtualisation support?

    Today I upgraded to mac os x lion and when I open parallels desktop it asks me to enable hardware virtualisation support on my MacBook pro so that I can run windows xp as a virtual machine. I have searched the net and cannot find a way to access the bios to enable this feature, please could I have some support and advise on how to enable the VT. I did have any problems whilst I was on os x snow leopard and parallels used to work fine.
    Thanks in advance.

    Boot camp  is the way to go then you will be able to turn it on. Run boot camp install windows xp and you be able to get into the bios
    Here's some other help full info as well
    VMware Fusion 3.1.3 was designed for OS X 10.6 (Snow Leopard) but is compatible with Mac OS X 10.7 (Lion), with the reservations listed below. If you are running an older versions of VMware Fusion, upgrade to VMware Fusion 3.1.3 before upgrading to Lion. Fusion 2.x is incompatible with Lion.  For the best experience, reinstall Fusion after upgrading to Lion.  When running Fusion on Lion, these limitations are known to exist:
    The Migration Assistant, included with VMware Fusion, is not compatible with Mac OS X Lion. This is due to a change in file sharing components.
    VMware recommends that a Snow Leopard-based Mac be used to migrate an existing PC. The resulting virtual machine can then be used in Fusion running on Lion.
    Boot Camp partitions are not accessible through Fusion after upgrading to Lion.
    To work around this issue, delete the Boot Camp virtual machine from the library and recreate it.  For more information, see A Boot Camp virtual machine fails to power on with a disk error (1003483).
    Minor visual issues have been reported when using Mission Control with Unity mode.
    Mac OS X 10.7 (Lion) Client and Server cannot be run as guests, at this time.
    VMware can provide best effort support if you choose to upgrade to Lion, but we cannot guarantee a resolution for all issues.
    To be alerted when this article is updated, click Subscribe to Document in the Actions box.

  • Extended partition on old MBR HDD makes Windows 7 UEFI boot fail

    There seems to be a bug in Windows 7 Pro x64 that prevents it from booting on a GPT partitioned HDD when the same machine also has an MBR partitioned HDD with an extended partition.
    I have a UEFI bootable PC with two HDDs:
    Disk 0 is GPT partitioned and contains Windows 7 Pro x64 and openSUSE systems.
    Disk 1 is MBR partitioned and contains Windows XP Pro x64 systems and bootable ISO images.
    Both the disks also have separate partitions for data and for booting.
    They are normally booted via rEFInd on disk 0 as follows:
    UEFI => rEFInd  => Windows 7 or GRUB2.
    UEFI => rEFInd => disk 1 MBR => GRUB4DOS.
    I had previously installed Windows 7 when it was first released, but abandoned it in favour of XP and openSUSE instead.  With the end of support for XP I decided to re-install W7.  Before doing so I unplugged disk 1 to ensure that W7 booted completely
    independently of XP.  After installing W7 I installed SP1 and all the Windows updates.  The new W7 system could be booted without problem via rEFInd => \EFI\Microsoft\Boot\bootmgfw.efi
    However when I plugged in disk 1 W7 would no longer boot.  It displayed the message "Windows is Loading Files" as the bar progressed twice before returning to the rEFInd menu.  On selecting W7 again it presented the option to "Launch
    Startup Repair", but on doing so it too just displayed "loading files" and returned to the reEFInd menu. 
    I UEFI booted from the installation DVD and ran Repair.  When re-booted W7 presented a menu with choice of new and recovered systems, but both failed as before.  Neither could be booted in safe mode.  Booting directly from the UEFI firmware menu
    into W7, instead of via rEFInd, gave similar results. 
    Investigations showed that the problem is caused by the extended partition on disk 1.  If it is deleted, or just hidden by changing the partition type from 0x0F to 0x00, then W7 boots OK.  Plugging in an external USB HDD with logical partitions also
    prevents W7 from booting.
    This all seemed to be similar to the problem described in KB979374, so I downloaded the hotfix (404153_intl_x64_zip.exe), which is supposed to be applicable to Windows 7 as well as WindowsServer 2008 R2.  However when the hotfix was run it displayed "The
    update is not applicable to your computer" and logged the following error:
       error 2149842967 "" (Command line: ""C:\Windows\system32\wusa.exe" "<pathname>\Windows6.1-KB979374-x64.msu" ")
    Is this because the version of files mentioned in KB979374 is older (6.1.7600.20617) than the version of Winload.exe in my system (6.1.7601.17556)? 
    According to http://www.techienewsnetwork.com/247/22/ SP1 included hotfix 979374, but it doesn't appear in the list of Installed Updates given in my W7 control panel.  Should it, are hotfixes included in a service pack listed individually?  If
    not is there any way to tell whether or not hotfix 979374 has been applied? 
    How can W7 be booted without having to change the partition type code of  extended partitions every time, is there a newer hotfix that will fix the problem in Windows 7 SP1?
    Almost all the references I can find to this problem are at least 2 years old, which suggests it might have been fixed.  Does anyone else with an up to date Windows 7 SP1 have this problem with extended partitions.  An easy test is to plug in an external
    HDD with logical partitions and see if W7 will still boot.
    I don't want to convert disk 1 to GPT as that would make XP un-bootable.  Also GRUB4DOS only supports MBR, and it is very useful for booting ISO images as well as XP. 
    Cheers.

    Hi Wade,
    To be sure that openSUSE, XP, or any other software on my PC isn't part of the problem I decided to do a new install of Windows 7 on a blank HDD.  As I don't have a spare one I had to backup everything on disk 1 (MBR) and then wipe it, including the MBR,
    with zeros (using AOMEI Partition Assistant).
    I unplugged the original disk 0 so that the PC had just single completely blank HDD (previously disk 1),  UEFI booted the Windows 7 DVD and installed W7 again.  Unfortunately at this first attempt W7 partitioned the blank HDD as an MBR disk and booted
    in legacy BIOS mode, even though I had booted the DVD in UEFI mode.  So I deleted all the partitions it had just created and converted the disk to a GPT one.
    The next time I installed W7 it was a UEFI one, with an EFI system partition.  After installing SP1 and re-booting it a few times to make sure it was working OK I plugged in the external HDD with an extended partition before re-booting.  The result
    was exactly the same as reported above for the main GPT disk: it briefly flashed "Starting Windows" then displayed "Loading files" for a few seconds as the bars progressed; when Startup Repair was launched it failed as well.
    After removing the HDD I booted the new W7 and added some missing drivers and installed all the Windows Updates, including the optional ones.  Many hours later the result was a new up to date installation of Windows that worked perfectly (no errors in
    any log files), with no other software on the PC.  However as soon as the external HDD was plugged in it failed to boot, as described previously.
    I then ran Bootrec from the DVD, trying all the commands,  but the results were exactly the same: everything worked successfully but no Windows installations were found, and it didn't fix the problem. 
    The documentation on how to use Bootrec describes how to backup the BCD store that is on the C: drive (e.g. "ren c:\boot\bcd bcd.old").  However the BCD store for UEFI based systems is in the EFI system partition, NOT on the C: drive.  This suggest
    that Bootrec does not apply to UEFI based systems.
    Are you sure that the MBR is used when booting in UEFI mode?  From what I have read in several places (not MS pages) the protective MBR on the GPT isn't used, but instead the UEFI firmware runs \EFI\Microsoft\Boot\bootmgfw.efi which looks in the BCD store
    in the EFI partition.  Can you point me to any MS documentation please that explains exactly how UEFI booting works for Window 7, including its use of the MBR.
    Do you have a Windows 7 system that can boot from UEFI when an MBR disk with an extended partition is attached.  If so how is your installation different from the one I have just set up, i.e. Windows 7 installed on a PC with just
    a single empty GPT HDD?
    Do you work at Microsoft?  If so perhaps you could find out if anybody with a straightforward UEFI booted Windows 7 has problems when an MBR HDD with an extended partition is attached.
    Sorry for the delay in responding, but a lot of work was involved.

  • [SOLVED, sort of] Yet another UEFI boot issue

    Hello everyone,
    Let me start by saying sorry for the long (first) post.
    I've ended up with a UEFI boot problem I can't solve. I've searched the forum and internet and I realize I'm not the only one who ran into problems with UEFI. Unfortunately, the problems other have had seem not similar to mine. I've spent almost 2 days now trying to figure this out, and I'm getting nowhere (though I've learnt some more about UEFI, which I guess is good). I was hoping someone here can give me some hints on how to proceed.
    So lets start with the background. I recently bought a new computer (Lenovo Thinkpad Edge E530 with Windows 8) and of course I want to run ArchLinux on it (been using ArchLinux for almost 7 years now and no plans on switching). Installation went ok with only a few problems during installation that I managed to solve (or so I thought). I must admit I didn't follow the guide fully. I didn't want to remove the Restore and Windows partitions, so I figured it would be safe to reuse the existing UEFI System Partition, as long as there was enough room, which there was. Anyway, I now have a computer I can boot into ArchLinux and also Windows 8, just the way I want it, almost. There is this one final issue I haven't been able to figure out how to solve.
    The problem
    Whenever I reset/power on the computer, I must press Enter during the initial screen (showing a Lenovo logo, and a message about pressing Enter to interrupt normal startup). If I don't press Enter before the timeout (a second or so), the screen will go white and that's it. No beep, no message, no nothing but a white screen. A power cycle is the only way to leave this state. Occasionally the screen will be a white bar at the top and random colours below, but I'm guessing this only represents what is in graphics memory at the time (0x00, 0xFF or any other random value).
    If i do press Enter however, then I'm presented with a menu where I can select what to boot; rEFInd (which is preselected) along with Windows 8 and some restore and diagnostic entries. Pressing enter will take me to the preselected rEFInd, pressing enter again (or wait for timeout) will boot linux, and I'm in. Nothing weird there. And if I select Windows in rEFInd, then windows boot, just as expected.
    There is no difference whether I'm switching from Windows to Linux or Linux to Windows or just reboot the same OS I was using again. The result is the same whatever I choose to boot.
    So the question is: Why do I have to select rEFInd manually and go through all these menus? Should I not be able to just power it on and let it boot the preselected rEFInd entry and continue from there, without me helping it?
    Trying to solve it
    Searching here and on the internet gave me some ideas on what to try, so here is a list of my attempts:
    efibootmgr show me there is a rEFInd entry, and that it is the first one in boot order
    I copied refindx64.efi to /boot/efi/EFI/Boot/bootx64.efi (replacing an existing entry)
    I've updated the EFI firmware (from Lenovo) to the latest and greatest
    One other guy had almost the same issue, but with a single boot of Windows. He solved it with Microsoft Boot Manager (there is an Automatic Repair, or something). I even dared trying this, though I must admit I was a bit hesitant about letting some Microsoft program trying to repair my computer. Anyway, it said it couldn't repair my problem, nor did it say I had one, so I am none the wiser.
    None of the above gave anything.
    So, that's it. I guess I can live with having to press Enter on every power up/reset, but it is very annoying having to do so, and even more so when I forget it because then I'm forced to power cycle it. I hope someone reading this can figure out what's going on, because I am clueless.
    Best regards,
    Johan
    Last edited by 6feet5 (2013-01-08 19:03:50)

    WonderWoofy wrote:@srs5694, have you thought about filing a bug report/feature request about the naming scheme here?  I would imagine that something coming directly from the upstream developer would be something that they should take into consideration.  Also, I imagine that renaming it to refindx64.efi kind of goes against the whole "vanilla packages" thing we tout around here... so it really makes me wonder why it is done in the first place.
    I've just done that:
    https://bugs.archlinux.org/task/33326
    It's not been very important until recently; but I've been putting a lot of effort into the ancillary support scripts (install.sh and mvrefind.sh). They necessarily rely on the files having certain names, so installing them under other names robs users of functionality.
    6feet5 wrote:I've decided to try and restore the whole unit, thinking it would take maybe an hour or two. It's been running now for almost 3 hours and only completed 20%.
    Good luck with that!
    FWIW, it seems that the number of EFI-related bug reports on Linux forums has gone way up recently. No doubt this is because EFI is now pretty much universal on new computers, so problems that used to affect one or two people now affect dozens or hundreds, and some of those post about them.

Maybe you are looking for