Booting in UEFI mode

Hello,
I have a Z77A-G45 mainboard which supports UEFI. I am trying to install Windows 7 (64 bit) on a GPT hard drive which already has Linux Mint 13 (equivalent to Ubuntu 12.04 LTS) installed. The disk is 1TB big and I have reserved 250 GB of unallocated space for Windows at the beginning of the disk. The disk was partitioned using Gparted (or the Linux Mint partition editor which is also based in libparted I think).
The problem is that the Windows DVD only boots in BIOS mode, so it's not letting me install it on a GPT hard drive. As I have read I must boot the DVD in UEFI mode to be able to install Windows the way I want. The problem is that in the boot options I don't have one for booting in UEFI mode (the only option I get is tagged 'CD/DVD:ATAPI iHAS122 C'). I have read that I can boot into the UEFI shell, browse the DVD and start the installation program from a UEFI boot file (*.efi). When I try to do that most of the tutorials tell me to point my prompt to fs0: but I only see blk'n' (n is the number of the device) block devices. blk5 is the DVD. I mount it using the command 'mount' and the prompt tells me it boots successfully. Then I point the prompt to 'blk5:' and it works, but when I try 'cd' or 'ls' I get the error "ls/dir: Cannot open current directory - Not Found".
I am certain my motherboard supports UEFI and I am quite sure it's enabled because I get the graphical BIOS. I didn't have any problems formatting the disk as GPT, and the Windows installer (in BIOS mode) recognises all the partitions correctly but it won't let me install the OS complaining about the GPT hard drive.
What can I do? Is there a middle step I am skipping? As much as I read around everyone with this problem gets to browse the DVD in the UEFI shell but I am stuck there.
Thank you very much in advance.

I copied all of the files from the dvd to a usb 3.0 stick and installed from the in UEFI mode. (Just select the UEFI: HP usb stick or whatever)
Are you sure you don't see UEFI: DVD Burner in the boot list?

Similar Messages

[SOLVED]Unable to boot in UEFI mode from CD

Hello gents!
Here's the problem:
According to the beginner's guide I followed the instruction to test if I am in UEFI mode:
In case you have a UEFI motherboard, the CD/USB will launch UEFI Shell and display a message that
startup.nsh
script will be launched. Allow the shell to launch it. Then, to check whether you have booted into UEFI mode, load the efivars kernel module (before chrooting) and then check whether there are files in
/sys/firmware/efi/vars/
# modprobe efivars # before chrooting
# ls -1 /sys/firmware/efi/vars/
Well, the thing is that when I boot the CD no UEFI Shell is launched as well as no
startup.nsh
When I try to load the efivars I don't receive any message, so, I assume, the module is loaded; but the, when I invoke ls the message I receive is:
#ls: cannot access /sys/firmware/efi/vars/: No such file or directory
To me it looks that for some reason I am unable to access the UEFI mode when starting the CD iso.
Thank you guys for your courteous attention.
Have a wonderful day!!!
P.S. I've searched already in the following posts:
https://bbs.archlinux.org/viewtopic.php … 84#p148184
https://bbs.archlinux.org/viewtopic.php … 55#p148155
P.S.2
My mobo is an ASUS Maximus V Gene with i3770K on it.
Edit:
Ok guys! Thanks to all of you, but everything was brought about by my scarce knowledge of the mobo. Logging into the BIOS, in the boot section, you have to choose between normal DVD and UEFI DVD. When selecting the last, everything, I mean, the startup phase at least, went well.
Enjoy everybody
Any idea how to close/"solved" this forum tread?
Last edited by guidone (2012-09-11 20:34:21)

guidone wrote:Any idea how to close/"solved" this forum tread?
README: Forum Rules
Simply edit the original post by clicking on the 'edit' button at the lower right corner of it and prepend [SOLVED] to the title.

Unable to boot in UEFI mode.

After looking around at the wiki for a few days and playing around with Arch in VirtualBox I went to see if it would boot on my native hardware, and all the turns up is a black screen. Legacy mode is not an option as I am dual booting Windows 8.1 64 bit. I suspect this is related to my issues with Fedora as the Fedora installation media will not boot either, though it once did. Fedora used to work on my machine until it got dropped one day. After the drop I started having some strange issues and tried reinstalling Fedora, only to find that once it hit the bootloader I would face a black screen that never goes away until I power the system down. I sent my laptop in to Lenovo to be serviced and they replaced the optical drive, hard drive and did a reinstall of Windows 8. Fedora still would not boot after I got the machine back. I tried Ubuntu after the drop before sending it off and it worked, and that is what I currently have installed. My knowledge of UEFI is limited. Any ideas? My laptop is a Thinkpad L440 by the way.

Head_on_a_Stick wrote:
Actually, Ubuntu will install and run with Secure Boot enabled (as will the Arch live ISO) -- the blog post is just about making your own Secure Boot keys.
From Ubuntu, post the output of:
# efibootmgr -v
Yeah I know that, but I left it off to save the extra hassle.
Here is the output for the command:
swilliams@speedy:~/Videos$ sudo efibootmgr -v
[sudo] password for swilliams:
BootCurrent: 0014
Timeout: 0 seconds
BootOrder: 0014,0013,0000,0001,0002,0003,0007,0008,0009,000A,000B,000C,000D,0012
Boot0000 Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Lenovo Diagnostics
Boot0004 Startup Interrupt Menu
Boot0005 Rescue and Recovery
Boot0006 MEBx Hot Key
Boot0007* USB CD 030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55
Boot0008* USB FDD 030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49
Boot0009* ATAPI CD0 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35400
Boot000A* ATA HDD0 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f604
Boot000B* ATA HDD1 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f605
Boot000C* USB HDD 030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803
Boot000D* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot000E* IDER BOOT CDROM ACPI(a0341d0,0)PCI(16,2)ATAPI(0,1,0)
Boot000F* IDER BOOT Floppy ACPI(a0341d0,0)PCI(16,2)ATAPI(0,0,0)
Boot0010* ATA HDD 030a2400d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f6
Boot0011* ATAPI CD 030a2400d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a354
Boot0012* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803
Boot0013* Windows Boot Manager HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0014* ubuntu HD(2,1f4800,82000,e2e20688-f616-4344-9acc-e7ae20c772e3)File(\EFI\ubuntu\shimx64.efi)

Prepare an usb thumb drive, to boot windows 7 or 8 in UEFI mode

Purpose of this post:
Prepare an usb thumb drive, to boot windows 7 in UEFI mode and install the system in pure UEFI mode.
Why am I writing this:
I had a hard time finding out how to make a custom installation of windows 7 in pure UEFI mode, and avoid using the factory restore disks. After hours of research, experiments etc I finally got the point and found a solution. And I'm happy to share my research with you. I hope this will be of help. If something is not clear, or more information is needed, I will be glad to explain things further.
History:
As most of you already know, BIOS was developed for PC in early eighties and has remained unchanged in recent years. But, since 2000, Intel started working on a new firmware interface, called Extensible Firmware Interface, abbreviated EFI. And since 2005 United EFI Forum has been handling the responsibility for development, management and promotion of UEFI specifications. Bigger companies like Intel, AMD, Microsoft and Dell have already started to bring out their products in accordance to UEFI standards which has more stable, secure and easier to use interface.
How does UEFI works (in a nutshell):
Once you power on the UEFI based PC, the Pre-EFI is executed which initializes only the CPU, memory and the chipset. This followed by Driver Execution Environment (DEX) where other hardware is initialized.
Advantages of UEFI:
    It can integrate various drivers this will not require to load during booting so saves time.
   PC can connect to network without OS.
   Also integrated drivers allow rendering GUI based control panel which out dates the old school bluish BIOS screen.
   Not all the installed hard drives are scanned as boot drive is set during the installation of OS in UFFI.
   Applications like anti-virus and diagnostic tools can be stored on virtually any non-volatile storage devices attached to a PC.
For a system to boot and install in UEFI the partition table of the HDD should be GPT (GUID Partition Table), not the old school MBR (master boot record). GPT has many advantages, can have virtually an unlimited number of partitions (windows will allow only 128) and impressively big partitions.
Since UEFI has a lot of advantages why not having a system install and boot in UEFI mode? AFAIK new Lenovo notebooks/netbooks are UEFI capable and OS’s are already installed in pure UEFI mode.
So, let’s go now to the point. Do you want to have more control over your HDD? Let say, you have a 320GB HDD and you have divided it in two partitions, one of 50GB, for your Windows 7, and the remaining for your data. If something goes wrong and you need to restore your system to factory default, with the recovery disks, it will wipe your partition scheme, set the system to default and this way your data will be lost.
You may want to make a “vanilla” installation of windows from a USB thumb drive and avoid using factory recovery disks. Now here things get complicated. A standard preparation of the USB with Microsoft’s software (Windows 7 USB/DVD Download Tool), or other tools, will give you a bios installation, not a UEFI one. So for the system to boot, you will need to change some settings in bios, and changing it from UEFI to legacy bios. The installation will prepare the HDD in MBR partition table, and you will lose all the advantages of UEFI, described above.
Now this can be avoided, by properly preparing an USB to boot and install in UEFI mode. Here are the steps:
Step by step tutorial:
1.   In a windows computer, download a legal copy (although trial) of the windows 7 os. You can do this from here: http://www.mydigitallife.info/official-windows-7-sp1-iso-from-digital-river/
Be sure to download the same version that came preinstalled in your computer. For example, if you have a Lenovo x120e, with a Windows 7 professional, 64bit, download an iso image of the Windows 7 professional 64bit.
2.   Once downloaded burn the iso to a USB thumb (at least 4GB) using Windows 7 USB/DVD Download Tool.
3.   After preparing this, create a folder on your computer, name it whatever (i.e. W7pro64bit). Go to the root of your USB
and select all the files and folders there (9 in total) copy, and paste to your folder you created, W7pro64bit.
4.   Using windows format the usb again in FAT32. Windows 7 USB/DVD Download tool, formats it in NTFS. We need a FAT32 formatted disk to achieve our goal. Formating again the USB in FAT32 will not touch the MBR of the USB thumbdrive. And after copying back the files (see step 6) the USB will still be bootable. (nice, and simple, isn't it?)
5.   Now go to the folder W7pro64bit and do the following:
a.   Browse to W7pro64bit\sources\ and open install.wim file. It’s a big file, and can be opened as an archive with 7zip (free software). Do not extract it, do not modify it, just browse the file with 7zip. Just to be sure you do not mess with that file, you can copy it somewhere else in your computer, and than procede.
b.   Browse this file (install.wim) to \1\Windows\Boot\EFI\ and locate the file bootmgfw.efi. Do not move, delete it, but just drag that file to the desktop. (if you have copied the file install.wim to another place in your computer, than you are safely do whatever you want with that file ) Close the 7zip program to release the install.wim file.
c.   Rename the file you just copied to the desktop from bootmgfw.efi to bootx64.efi.
d.   Now go back to w7pro64bit folder and browse \efi\Microsoft. Form there copy the folder boot and paste it one level up, on the folder: \efi. It will look like this: \efi\boot.
e.   Now copy the file you saved on your desktop and renamed (bootx64.efi) to \efi\boot (inside the boot folder you copied on step 5d
6.   Now go to the root of the folder W7pro64bit and select all folders and files (9 in total) copy, and paste all those files back to your USB thumb drive. (see step 4 for more info)
7.   Go to the computer that you are going to reinstall, and before restarting it, use the program ABR (activation backup and restore) to backup the license of your windows os. (use google to find ABR). Advanced Tokens Manager (ATM ) is great too. This link may be of help: Backup and restore W7 activation. After the program finishes its magic, it will create a few files inside the folder where the program itself reside. Copy these files to a new folder in your usb. Rename it to ABR so you will quickly find it later. (if you decide to use ATM, the procedure may be a little different. But you are smart enough to figure out how to use it)
8.   Backup to an external storage all your data before continuing.(reminder: are you sure you saved the license as explained in step 7, to a safe place? To a external drive, to another computer? If you are sure, than go on with step 9)
9.   Now restart your laptop, and enter your bios settings. Go to the boot settings, and set the computer to boot in UEFI only. Not both, not UEFI first, or legacy, BUT UEFI only. Save and restart.
10.   Press f12 (or the corresponding key for your machine) to choose the boot device and chose to start from the USB thumb drive with your windows 7 pro 64 bit.
11.   If everything is done correctly, your computer will boot from the USB.
12.   Follow the wizard and choose a custom install, not upgrade. At the disk partition window delete all the partition you see there until you have only one unallocated space.
13.   Select it, and click next to install windows, without making partition in this point. The installer will create a GPT partition table not a MBR since the USB booted in UEFI mode.
14.   Immediately after the first restart remove your USB thumb, and the installation will continue from the HDD. Wait until installation finishes.
15.   When you will be finally on your desktop, on the installed OS plug your USB go to the ABR folder and click on restore.exe. It will restore your license and your copy of windows will be activated.
16.   Now you can go in computer management/disk management and shrink the HDD to create your partitioning scheme. Make sure to leave enough space to your windows os. (30gb or more for extra programs you will install at your choice)
17.      Download from lenovo.com thinkvantage system update and update your system. Windows update too can install all the necessary drivers, if you need only basic drivers support.
Note: if tvsu will fail to work, see this:
http://forums.lenovo.com/t5/ThinkVantage-Technologies/ThinkVantage-System-Update-Servers-down-the-wh...
It may look a looong tutorial, but once you do this for the first time, it will look a piece of cake.
Final words:
From now on, you can install windows 7 in UEFI mode with your special USB without changing your partition scheme anymore. If you have a data partition beside your os partition (see the example above), when you reinstall the system using your USB thumb drive, at the disk partition window chose the partition where windows is installed, delete it, and reinstall windows to the unformatted area. Your partition with your data will be intact and the installation will automatically mount your data partition to the system. And, all the scope of this procedure, you will always have a pure UEFI installation of the system, with all its benefits.
Have fun!
abvasili
Moderator note: changed subject to match new content. Was: Prepare an usb thumb drive, to boot windows 7 in UEFI mode
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode.

seanare wrote:
Thank you, as I noted here, your post was the key to my getting a Windows 8 SecureBooting setup on a W530.
In the case of Windows 8, I needed to copy the files away, reformat my USB key as FAT32 and copy the files back, and viola I was able to boot from my USB install media with the BIOS set to only boot UEFI. From there, there rest was easy (for Windows 8, the copying and renaming is not necessary, the key is having a FAT32 partition on the USB media, rather than an NTFS one; the EFI files are already in the right location).
Thank you again good sir.
You are welcome... and I'm happy that the change of the file system helps with windows 8 too. Thanks for confirming that.
abvasili
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode.

[SOLVED] Attempting to boot from USB key in UEFI mode

I am attempting to boot from a USB Key in UEFI mode to dual boot windows 8 and arch linux. I'm unsuccessful in getting the USB key to boot in UEFI mode.
I am following the guide on page: https://wiki.archlinux.org/index.php/Un … _Interface due to the fact that I am receiving error " No loader found. Configuration files in /loader/entries/*.conf are needed."
I am attempting to use the archiso media and have created refind.conf according to https://bugs.archlinux.org/task/31894#comment102233 in (USB)/EFI/boot/refind.conf
However, I'm stuck on the initial step from the wiki: Install refind-efi pkg. In the usb's filesystem, overwrite the file EFI/boot/bootx64.efi with /usr/lib/refind/refind_x64.efi.
My question is: How do I install the refind-efi package onto the USB key using an arch linux host machine and the USB plugged into the machine.
Last edited by tonysoprano (2013-02-13 04:09:56)

swordfish wrote:1. Might be possible, that the uefi integration is pretty bad. Have you already looked for an update of the uefi bios?
This is my thought, too. The "memory map has changed" message sounds like the firmware is messing with the way memory is laid out in the middle of the boot process. A firmware update, if available, is likely to be the best way to deal with this problem. If not, trying Fedora's patched GRUB Legacy and GRUB 2 are also worth doing; it's conceivable that one of them includes a workaround for the problem.
2. In your first posting you mention Windows 8 on this machine. Is W8 starting in uefi mode?
This is important, but if the disk uses GPT partitioning, then Windows is starting in EFI mode.
3. If W8 is starting in uefi mode, are you sure that secure boot is disabled?
It is; if it weren't, neither rEFInd nor ELILO could start -- or even if they were configured to start in Secure Boot mode, ELILO doesn't launch its kernels in a way that respects Secure Boot, so the ELILO failure can't be caused by Secure Boot. Also, when launched with Secure Boot active, rEFInd returns a clear error message about a security violation and then returns to its main menu; it doesn't hang the computer.
One possible workaround occurs to me if all else fails: Have rEFInd launch a BIOS version of GRUB. The setup procedure, in outline, is as follows:
Create a BIOS Boot Partition on the disk.
Install the BIOS version of GRUB 2.
Configure rEFInd to include a scan for BIOS-mode boot loaders by uncommenting the "scanfor" line in refind.conf and adding "hdbios" to it.
Thereafter, you'll see a new "generic" icon, which should launch GRUB, which should launch Linux in BIOS mode, even though Windows launches in EFI mode. This will work on most modern UEFI-based computers with a single hard disk, but things get trickier with multiple disks and with some UEFI implementations that lack the necessary firmware features. If a future firmware update fixes the problem, or if a future kernel's EFI stub loader includes a workaround, the EFI-mode booting will become an option once again.

Cannot boot Arch (USB or HDD) in UEFI Mode

I have a new MSi GT70-0ND, 1x 128GB SSD (no RAID) and 1x 750GB HDD. The SSD was preloaded with an MSi OEM copy of Windows 8. I did not receive an OEM disc, so I've tried to avoid touching the SSD and the hidden recovery partition on the HDD.
Using Universal USB Installer, installed archiso onto USB flashdrive.
Windows boot device selection menu did not detect the flashdrive.
Checked UEFI BIOS settings - USB set to "Full Initial".
Moved flashdrive from port to port, eventually was detected.
Reboot, received an error relating to bootloader signing.
Rebooted again into UEFI BIOS settings, disabled secure boot.
Rebooted, received infamous "No loader found. Configuration files in \loader\entries\*.conf are needed."
Googled, checked forums, saw gummiboot issues, recommendations to use rEFInd, and dd/UEFI issue.
Transferred archiso to working Arch machine, followed instructions here https://wiki.archlinux.org/index.php/UE … B_from_ISO.
Installed rEFInd using instructions here https://bugs.archlinux.org/task/31894#comment102233. I have since tried various changes to refind.conf and can not discern any difference.
Attempted to boot laptop from flashdrive in UEFI mode after Windows' boot device menu again failed to detect flashdrive multiple times.
Got rEFInd menu, found nothing functional (except Windows bootloader, of course): Arch entry froze the system requiring hard reboot, UEFI Shell v2 gave an assertion error (from memory, it was "String.c(166) String != ((void *)0)"); Googled, seeing some related but no identical errors, UEFI Shell v1 failed to start reporting something like "using load options '<null string>'".
Rebooted in BIOS/Legacy mode, but flashdrive was unbootable (duh)
Again using Universal USB Installer, installed archiso onto flashdrive.
Rebooted in BIOS/Legacy mode, archiso menu appeared, but during udev events, received a drm/nouveau init table error; Hard reboot. Appended
nouveau.modeset=0
to kernel line, everything worked
Installed vanilla Arch system to the HDD including UEFISYS partition.
When it came time to set up and install rEFInd/efibootmgr, of course
modprobe efivars
failed.
Redid flashdrive the UEFI-safe way on Arch machine, attempted to boot in UEFI mode, it appears that menu entries from my /boot/efi (UEFISYS) partition are present, but this is irrelevant as only the Windows bootloader and \refindx64.efi work (loads rEFInd graphical mode, in which nothing works except BOOTX64.efi which quickly flashes a message with a file path (too quickly to read) then loads Windows. UEFI Shell v2 now has same error as v1:
Using load options '<null string'> Error: Not Found while loading shellx64_v2.efi
rEFInd (version 0.5.0) "About" dialog reports EFI Revision 2.31, Firmware: American Megatrends 4.653, Screen Output: Graphics Output (UEFI)
I have tried adding various things to the refind.conf "options" directive, e.g. gpt, loglevel=7, pci=nocrs, add_efi_memmap, archisobasedir=arch, archisolabel=ARCH_201212, acpi=off, etc. in different combinations.
I am at wits' end. Bottom line: nothing but rEFInd (via flashdrive) and Windows works in UEFI boot mode - nothing. Any help will be greatly appreciated. Thank you.

I doubt if this will help you with your main goal, but I've fixed a few memory bugs in rEFInd recently, so the "String.c(166) String != ((void *)0)" error you mentioned might go away if you upgraded to the latest version of rEFInd (0.6.0).
Beyond that, here's a suggestion:
Prepare a USB flash drive or CD-R with rEFInd 0.6.0. Be sure to include an EFI driver for whatever filesystem you used in Arch's /boot (or root, if there's no separate /boot partition) in the flash drive's or CD's EFI/BOOT/drivers_x64 directory. (Note that rEFInd 0.6.0 includes an ext4fs driver.)
Using an emergency disc, create a refind_linux.conf file in Arch's /boot directory. Include, at a minimum, two lines, each of which should include the options "ro root=/dev/{whatever} initrd={\path\to\initrd}", changing the device filename to point to your root and the initrd= specification to point to your two Arch initrd files (one for each line). The path should be relative to the root of whatever filesystem holds those files, so if you've got a separate /boot partition, there would be no directories, just the filename preceded by a backslash; and if you have no separate /boot partition, you'd lead with "\boot\". Note the need for BACKslashes, not forward slashes, in the initrd= specification (but forward slashes in the root= specification).
Reboot using the rEFInd flash drive or CD-R you've prepared. With any luck, rEFInd should come up and show you an Arch option. Try using it. If it fails, try again, but hit Insert and select the second option from the list.
With any luck this will get your system booted in EFI mode, but I can't make any promises about that.

Blue screen when booting from USB drive in UEFI mode (2013.07)

SOLUTION for me was to update the firmware on my ASRock mb as thatu pdate changed the EFI software (by American Megatrends) version from 2.00 to 2.31. However, other users are still experiencing the blue screen.
SHORT VERSION
When I try to boot Arch Linux 2013.07 with an USB drive in UEFI mode (for installation), I get a blue screen (which is rather a literal description and not a hint towards the old Windows' one) with the message
Failed to install override security policy (14): Not found
LONG VERSION
I made an USB installation media (product: Intenso Rainbow) by following this advice on the wiki.
I used the july release of Arch for that. First of, after installing the image to the USB stick I found that I needed to correct the label in the archiso-x86_64.conf file to ARCH_201307 (or was it the label of the usb stick, can't remember right now). (Pretty sure it was the same problem with "Linux Live USB Creator" which I used 3-4 months ago...)
After doing that, I rebooted and selected the entry
UEFI Intenso Rainbow
from this list of entries:
SATA HDJ ... something (the hard drive where Win 7 64 bit is installed with all programs)
SATA something (hard drive which only contains data)
Windows Boot Manager
USB: Intenso Rainbow
UEFI: Intenso Rainbow
It went to a blue screen with a message in white text saying
Failed to install override security policy (14): Not found
Below that was an OK button which had a black rectangle over it.
After I experienced the bluescreen, I tried booting the
USB Intenso Rainbow
entry and the boot process then worked fine, I got to that Arch menu where I could choose
Boot Arch Linux (x86_64)
Boot Arch Linux (i686)
Boot existing OS
Run Memtest...
and so on...
But just to make sure, I then did the check for UEFI mode according to this and only saw a folder acpi and ... something else I can't really remember, but it definitely was not efi. Thing is, I needwant to boot into UEFI mode as I have Win 7 already installed in UEFI mode.
Some info about my motherboard: it's from ASRock and is called H67M. The BIOS is dated to 2011-10-26 and is version 1.7.
So far, I only found a mention of the problem here at superuser.com.
Last edited by jones (2013-07-15 07:15:18)

Ok then, so this thread has also become about the blank screen problem when booting (in this particular case, Arch 2013.06 since 2013.07 seems to be worse).
srs5694 wrote:Typically, you adjust kernel boot options using your boot manager or boot loader. In GRUB, you hit the "e" key to open an editor. In rEFInd, you hit F2 or Insert twice. I don't recall offhand what key does the job for gummiboot (which I'm pretty sure the Arch installer uses), but I'm certain it's got the feature.
You are right. Thanks. I realized I had the gummiboot config right in front of me all the time. It's the file 'archiso-x86_64.conf' in \loader\entries (on Windows).
An addendum: I think the USB: Intenso Rainbow boot option takes me into a GRUB menu. Hitting 'e' in this "big" and fully designed menu didn't do anything IIRC. Hitting 'Tab' did the trick to get into editing the boot command line.
Hitting 'e' worked in the gummiboot menu though.
So I tried booting with the following options (also by combining some of them)
nomodeset
acpi_backlight=vendor
radeon.modeset=0 (I have a Gigabyte 7870 card in this desktop machien)
i915.modeset=0
but it did not help.
To be rather safe than sorry: I should mention that there are two grey-ish bars visible on the top and bottom of the screen after I try to boot the first entry, Arch Linux archiso x86_64 UEFI USB. Always has been with those two older Arch version (2013.05+2013.06). I also found another thread where one user talks about using the VGA port of the monitor, which I am currently not, I am using the DVI one, so that's worth a try too. EDIT It did not help either. What I did was setting the primary graphics adapter in the UEFI north bridge configuration menu to 'onboard' which worked immediately when rebooting (I hit the button labeled "Source" on my monitor and it showed it is using the "Analog" mode), but the problem just stayed the same. Adding aforementioned boot options or a combination thereof did not change anything.
Thanks for the e-mail addresses, I sent one to James Bottomley.
Last edited by jones (2013-07-07 11:12:05)

Impossible to install arch in UEFI mode on my Acer Aspire S3-391

Hi there,
I am trying to install arch-linux on my Acer Aspire S3-391, which came with a pre-shipped Windows 8. I am trying to make a dual boot, so I would like to keep the UEFI mode at startup. However, my computer won't boot on the Arch Linux USB Flash drive when in UEFI mode : when plugged in, the key prevents the computer from loading anything. The "Acer" page keeps on reloading itself, without even letting me access the BIOS menu (In other words, the computer is blocked at "POST" phase when the installation media of arch is plugged in).
Here's what I did to try and solve the problem :
1) of course, I disabled Secure Boot and hibernation in Windows 8.
2) tried to boot in legacy bios. It works, and i could install arch this way : but as told before, i would like to install it in UEFI mode.
3) Checked, re-checked and re-rechecked the installation media.
4) tried to install Ubuntu in UEFI mode. It worked : the bootable key of Ubuntu was loaded, when the bootable key of arch is blocked. Why ? No idea...
5) Installed Ubuntu, and tried to install Arch in UEFI mode from Ubuntu, following the tutorial "Install_from_Existing_Linux". No luck here : i was blocked at step "Testing if you are booted into UEFI mode" on the beginner's guide : I was not, and I couldn't find any solution in the tutorial.
Any suggestions on what I should try next ?

If you've already installed in BIOS/CSM/legacy mode, my recommendation is to install your EFI-mode boot loader and try it out. You'll need to use something else that does boot (such as Ubuntu), install the boot loader using the Windows bcdedit command (assuming you're dual-booting), or install the boot loader as EFI/BOOT/bootx64.efi (if you're setting up for Linux alone) to get it to work, though.

Can't boot properly in UEFI mode

Hi!
After enabling "windows 8 feature" and booting in uefi only mode, no boot device is detected anymore. The efi shell comes up after the bios has started and I can't boot into windows. I tried a clear cmos but it didn't work. I have a Z87-GD65 (latest 1.11 or 1.1B bios) and my sata devices are a crucial mx100 ssd (with windows 8.1 64-bit), western digital black hdd and asus dvd reader. I'd like to be able to boot in uefi normally. Thanks for your help!

I think I've found topic for you
https://forum-en.msi.com/index.php?topic=250729.0;topicseen
It's about notebook but installation process is actually the same

Yoga 11s - how to boot from USB in UEFI mode (tried everything)

I have been trying for days to install Windows 7 on my new Yoga 11s in dual boot configuration with 8.1, with no luck. Typical catch-22 problem -- can't boot from the install media in UEFI mode, and if booted in legacy mode, Windows won't install on GPT partition. I followed all the steps everywhere mentioned: disabled secure boot, set boot mode and order in every possible combination, etc. I followed these steps exactly to create a UEFI-bootable USB drive:http://forums.lenovo.com/t5/Windows-8-and-8-1-Knowledge-Base/Why-can-t-I-boot-from-a-USB-key-on-UEFI-ThinkPad-or-ThinkCentre/ta-p/1004621 I can boot easily from the USB in legacy mode, but in UEFI mode, when starting the machine, the USB is ignored. If I go into Windows 8.1 recovery and do an advanced start and choose EFI USB, the machine thinks for a moment and then says: "System doesn't have any USB boot option. Please select other boot option in Boot Manager Menu." Then I click OK and it offers only one option on the menu, Windows Boot Manager. I don't know if the lack of boot options is just a symptom of the USB not really being UEFI-bootable, or some other steps are needed to add boot options. I even tried adding an item within the windows boot manager, but that didn't work, because even if it could work in principle I don't know the right settings. Has anyone actually made this work? If so, what is the secret?

I had the same problem and a lot of frustration. I finally solved the problem by using a different USB key. I also had to go into boot options and select the USB key even though I had the USB key first in the boot order. Right now I am Re-imaging from my backup and pray for success. Although things may look brigth afterall I have to leave out some steam:The whole problem started with a screen error, which had to be repaired. So before sending it to repair I made an image backup, - just in case. I got an eight hour time window where I had to wait for a pickup of the computer,- very frustrating when you are having a job requiring traveling. After ten days the computer computer came back with a scrambled hard disk with at note saying that it was an software error, although it was no doubt an hardware error because it worked perfectly with an external monitor. I have not counted the number of hours this bad service has costs but it exceeds the value of the computer!

Booting Windows 7 install DVD in uefi mode fails for satellite p870

So as the title says, I'm trying to boot the windows 7 installer in uefi mode. It gets pretty far into the boot process, but then just falls flat on it's face. Booting the DVD in safe mode, I can see that it loads all the drivers up to disk.sys, then it seems like it's trying to display the installer GUI and fails. The top quarter or so of the screen gets blanked to black, and then everything just sorta stops. DVD stops spinning, and nothing else happens. I'm kinda restricted to uefi at the moment, as the drive i want to install on has some stuff i'd rather not lose on it, and i've just carved out some empty space for windows.

Hello Jerry:
Trying to help a friend who just got a Satellite L875D that needs to downgrade from factory Win8 to a purchased disk of Win7-64 to continue using his legacy software & not have to re-train himself & buy more stuff. Tried putting in the Win7 disk before starting the first time, but it didn't boot from that drive. Then the initial start-up factory screen didn't give an F-key to enter BIOS. Some forum notes say it might be F-2 or F-12; another post says he tried every F key.
Do I have to do/finish the Win8 installation, and then let Win7 format the C drive? One post talks of the Win8 method to reach the UEFI, and then you say to disable secure boot. And I am not sure if the Win8 is in a "safe" partition since there are no disks included; or if I should do the Win8 install and make a backup of it, and then do the Win7 clean install.
Thank you.

Booting Arch-ISO from USB-Stick in UEFI mode fails

Hi there,
I'm running an Asrock H77M-ITX UEFI mobo. On this system I've already installed Arch on a Samsung 830 SSD (GPT formatted) - but in BIOS legacy mode because I've written the Arch-ISO image with "dd" to an USB-Stick (and UEFI boot mode wasn't even presented at boot).
Out of curiosity I've re-formatted the stick and copied Arch-ISO following https://wiki.archlinux.org/index.php/Un … B_from_ISO.
Now I could start the ISO in UEFI mode, but it failed to start gummiboot with the "No loader found. Configuration files in \loader\entries\*.conf are needed." error message, concerning a problem with gummiboot.
Following some advice on the forum, I did this:
- install refind-efi 0.4.7-2
- copy /usr/lib/refind/refindx64.efi to [USB]/EFI/boot and renaming it to bootx64.efi (i.e. replacing the original bootx64.efi from gummiboot)
- Create a new file in the same directory ([USB]/EFI/boot/) called refind.conf
- Add this to it:
textonly
scanfor manual
menuentry Arch {
loader /arch/boot/x86_64/vmlinuz
initrd /arch/boot/x86_64/archiso.img
options "gpt loglevel=7 add_efi_memmap none=UEFI_ARCH_x86_64"
With this I can launch Arch-ISO from the USB-Stick in UEFI mode and I can choose Arch from rEFIND. Then Arch-ISO starts booting but it always stops at the same point with this message:
sd 6:0:0:0: [sdb] No Caching mode page present
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sd 6:0:0:0: [sdb] Attached SCSI removable disk
ERROR: '/dev/disk/by-label/' device did not show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finished
sh: can't access tty: job control turned off
[rootfs /]#
sdb is the USB-Stick from which I start Arch-ISO. Again - I didn't use dd to write the ISO to the stick.
Maybe this is pretty easy to solve, but I have to admit that I'm somewhat stuck
Last edited by swordfish (2012-11-19 21:31:43)

WonderWoofy wrote:See what the difference is between archiso and archboot maybe? Seriously, have you made any effort whatsoever?
Of course. Read:
The "Main Page" ( https://www.archlinux.org/ ) states:
"You've reached the website for Arch Linux, a lightweight and flexible Linux® distribution that tries to Keep It Simple."
"Keep It Simple". Yeah!
In line with that, the "The Arch Way" page ( https://wiki.archlinux.org/index.php/The_Arch_Way ) states:
"The following five core principles comprise what is commonly referred to as the Arch Way, or the Arch Philosophy, perhaps best summarized by the acronym KISS for Keep It Simple, Stupid."
The ArchWiki ( https://wiki.archlinux.org/ ) links to several other pages, such as these:
The "Forum Etiquette" page ( https://wiki.archlinux.org/index.php/Forum_Etiquette ) states under "Ineffective Discussion":
"Arch is a Do It Yourself community" and "treat others as you would be treated; respect them and their views". I am very much a "do it yourself" person -- that's why I like The Arch Way. I also go by the Golden Rule stated here.
Now, everyone is a newbie at some time. I and other posters here are obviously newbies with respect to ArchLinux. Even experts were newbies at one time. Newbies, by definition, do not necessarily know what they're doing, or where to find information. Hence, Arch's "Beginners' Guide" and such. Hence, posts on this board from newbies asking for help.
As regards initial installation of ArchLinux, and consistent with the above, the FAQ ( https://wiki.archlinux.org/index.php/FAQ ), under "Q) Arch needs an installer. Maybe a GUI installer", states:
"A) Since installation doesn't occur often (read the rest of this article to know more about what rolling release means), it is not a high priority for developers or users. The Installation Guide and Beginners' Guide have been fully updated to use the command-line method. If you're still interested in using an installer, consider using Archboot."
So the basic installation instructions explicitly state that Archboot is not needed.
The "Installation Guide" ( https://wiki.archlinux.org/index.php/Installation_Guide ) says nothing about either Archboot or Archiso.
The "Beginners Guide" ( https://wiki.archlinux.org/index.php/Beginners%27_Guide ) says nothing about either Archboot or Archiso.
The "Archboot" page ( https://wiki.archlinux.org/index.php/Archboot ) is consistent with the above information, because it states:
"Archboot is a set of scripts to generate bootable media for CD/USB/PXE.
It is designed for installation or rescue operation."
The "Archiso" page ( https://wiki.archlinux.org/index.php/Archiso ) states:
"Archiso is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else."
So the pages describing both Archboot and Archiso clearly state that these tools are oriented towards already-existing installations -- even though it seems that they might be used, in certain circumstances, for initial installations.
I happen to be very new at playing around with installing Linux distros (although I've used Unix/Linux as a regular user for more than 30 years), and am brand new with respect to ArchLinux. I only began playing with it this past Saturday. So I would expect a bit of useful help as opposed to "RTFM!" I will soon get past the need to RTFM for basic tasks, but I have a way to go.
The fact is that for me and a number of other new ArchLinux users, the installation guides simply do not work. C.f. my post https://bbs.archlinux.org/viewtopic.php?id=153170 . I've done a lot of googling as well as searching the archives on this board, and others have come up against the same show-stopping installation problems that I have. I and others have posted to several recent threads on this board, trying to get past the problems, so far with no success.
Now, the.ridikulus.rat had written:
"You guys are using Archboot's kernel options for Archiso. Thats the issue in both the cases."
Given that neither of these sets of scripts were used by me or swordfish, this comment is not useful.
Given the above, can you or anyone else tell us what Archiso or Archboot might do to help us with our installation problems? Also, can you tell us how we, as newbies, ought to have found out how these might help?
Alan

How do you reinstall 64-bit Windows 7 in UEFI mode?

I have a PC with a single hard disk and, a while ago now, I installed 64-bit Windows 7 on it in UEFI mode.
The disk has two primary partitions: a C: partition which contains my Windows 7 system and other installed software such as Office, and a D: partition which contains only personal data.
(In other words, I don’t have a multi- or dual-boot system.)
I now wish to reinstall 64-bit Windows 7 into the same C: partition, again in UEFI mode.
There is a procedure for reinstalling Windows 7 documented on the following MS Web page:
http://windows.microsoft.com/en-us/windows/installing-reinstalling-windows#1TC=windows-7
in the section entitled “Using the Custom installation option without formatting the hard disk”.
The following YouTube video demonstrates this procedure:
http://www.youtube.com/watch?v=fr_s29MWOA0
and it looks relatively straightforward.
Essentially, the re-installation starts by inserting the installation DVD into the optical disk drive and running setup.exe while still logged on to Windows 7 with an administrator user ID.
At the screen entitled “Where do you want to install Windows?”, both the System Reserved partition (the example in the video is a legacy BIOS installation) and the C: primary partition are visible.
On that screen, you simply select the C: primary partition and click
Next, and Windows 7 is effectively reinstalled over Windows 7.
Any personal data in the C: partition is preserved in a folder called Windows.old.
The big question is, does this procedure work for a UEFI installation?
The documentation does not state that it works only for a legacy BIOS installation.
If I were to follow the procedure, when I reach the screen entitled “Where do you want to install Windows?”, I would expect to see the EFI System Partition (ESP), the Microsoft Reserved Partition (MSR), my C: primary partition and my D: primary partition.
Can I simply select the C: primary partition and click Next to start the (re-)installation?
It appears that nowhere in the procedure do you specify what mode of installation (legacy BIOS or UEFI) is required.
Does the installation setup simply use the same mode as that of the existing installation?
Does anyone have any experience of reinstalling Windows 7 in UEFI mode, using this procedure or any other method?

Hi,
It depends. Do you have Windows 7 DVD? Does your computer have a Boot from EFI Drive option?
Windows 7 DVD can boot in either BIOS mode or UEFI mode. Different UEFI firmware implementations support different methods for handling the installation operation. The processes for booting the computer into UEFI mode for the Windows product DVD are
the same. If you can find a boot from EFI Drive option, please perform the suggestions as i referred to.
If you cannot find any boot option, perform the steps below:
Use Device Manager's Firmware option and select Boot from EFI Internal Shell.
Use the EFI internal shell, as follows:
Start the EFI internal shell from the EFI boot menu and select the drive with the Windows product DVD. The following example assumes that the drive is Fs0:
Shell> Fs0:
Start the EFI boot application. For example, on an x64 system, run the following command:
fs0:> \EFI\BOOT\BOOTX64.EFI
After the application starts, you may be immediately prompted to press a key to boot from the drive to continue. Press a key to continue booting from the installation media.
Andy Altmann
TechNet Community Support

[SOLVED] Unable to boot in UEFI System

For several days I have been trying to get Arch to boot on my desktop by following the Beginners' guide and refering to other Arch wiki articles as well as Arch Forum posts for any problems that I had. I have tried a few bootloaders such as GRUB, gummiboot, and rEFInd and they all give the same result when I attempt to boot - a blinking cursor with no menu and then it returns me to the BIOS;. My UEFI motherboard is the ASUS VI Hero. I have disabled secure boot and both fast boots. I use a live USB with UEFI that is able to boot on my system and was created with dd.
Below are the outputs of some commands that might be useful.
root@archiso ~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 512M 0 part
├─sda2 8:2 0 4G 0 part
└─sda3 8:3 0 219.1G 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 487.3M 0 part
└─sdb2 8:18 0 931G 0 part
sdc 8:32 0 232.9G 0 disk
├─sdc1 8:33 0 100M 0 part
└─sdc2 8:34 0 232.8G 0 part
sdd 8:48 1 3.8G 0 disk
├─sdd1 8:49 1 595M 0 part /run/archiso/bootmnt
└─sdd2 8:50 1 31M 0 part
loop0 7:0 0 256.8M 1 loop /run/archiso/sfs/airootfs
loop1 7:1 0 32G 1 loop
└─arch_airootfs 254:0 0 32G 0 dm /
loop2 7:2 0 256M 0 loop
└─arch_airootfs 254:0 0 32G 0 dm /
Windows 7 is on sdc and Arch is on sda (sdb is an extra storage device for Windows). Both sdc and sda are SDDs.
root@archiso ~ # parted /dev/sda print
Model: ATA SanDisk SDSSDHII (scsi)
Disk /dev/sda: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot, esp
2 538MB 4833MB 4295MB linux-swap(v1)
3 4833MB 240GB 235GB ext4
root@archiso ~ # cat /mnt/etc/fstab
# UUID=0dff590b-24f1-47a2-870e-3f4d2c5bcb6a
/dev/sda3 / ext4 rw,relatime,data=ordered,discard 0 1
# UUID=FA3A-728C
/dev/sda1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# UUID=524e2980-d1e6-4948-88f9-c193682d5a9e
/dev/sda2 none swap defaults 0 0
# efibootmgr
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003
Boot0000* grub
Boot0001* Hard Drive
Boot0002* ubuntu
Boot0003* UEFI: General USB Flash Disk
Boot0008 Hard Drive
Ignore ubuntu, that was on my HDD from before but has been removed. The grub option usually disappears after reboot unless I run efibootmgr -O after I install the bootloader. Using efibootmgr -v option, the output is a bit hard to read.
# efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003
Boot0000* grub HD(1,800,100000,f9c04628-178b-4c94-9b92-62c04f2a5151)File(\EFI\grub\grubx64.efi)
Boot0001* Hard Drive BIOS(2,0,00)..GO..NO........u.W.D.C. .W.D.1.0.E.Z.E.X.-.0.8.M.2.N.A.0....................A.................................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.3.C.1.F.6.4.5.0.4.6........BO..NO........u.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .2.5.0.G.B....................A.................................>..Gd-.;.A..MQ..L.1.S.B.D.S.N.F.A.7.1.3.0.7.5. .L. . . . ........BO..NO........o.S.a.n.D.i.s.k. .S.D.S.S.D.H.I.I.2.4.0.G....................A...........................>..Gd-.;.A..MQ..L.4.1.3.4.3.7.0.4.7.0.2.0. . . . . . . . ........BO..NO........u.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k....................A.............................B..Gd-.;.A..MQ..L.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k........BO
Boot0002* ubuntu HD(1,800,f3a9e,3eaa3162-6352-4ad8-a725-89c738f2b3ad)File(\EFI\Ubuntu\grubx64.efi)
Boot0003* UEFI: General USB Flash Disk ACPI(a0341d0,0)PCI(1d,0)USB(1,0)USB(1,0)HD(1,fc,f800,612a5c68)..BO
Boot0008 Hard Drive BIOS(2,0,00)..GO..NO........o.S.a.n.D.i.s.k. .S.D.S.S.D.H.I.I.2.4.0.G....................A...........................>..Gd-.;.A..MQ..L.4.1.3.4.3.7.0.4.7.0.2.0. . . . . . . . ........BO..NO........u.W.D.C. .W.D.1.0.E.Z.E.X.-.0.8.M.2.N.A.0....................A.................................>..Gd-.;.A..MQ..L. . . . .W. .-.D.M.W.3.C.1.F.6.4.5.0.4.6........BO..NO........u.S.a.m.s.u.n.g. .S.S.D. .8.4.0. .E.V.O. .2.5.0.G.B....................A.................................>..Gd-.;.A..MQ..L.1.S.B.D.S.N.F.A.7.1.3.0.7.5. .L. . . . ........BO..NO........o.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k....................A.......................B..Gd-.;.A..MQ..L.G.e.n.e.r.a.l. .U.S.B. .F.l.a.s.h. .D.i.s.k........BO
I mount /dev/sda3 to /mnt and /dev/sda1 to /mnt/boot before I arch-chroot and when I tried grub, I installed with:
# grub-install --target=x86_64-efi --efi-directory=/boot--bootloader-id=grub --recheck
No errors are reported. I then make a config file for grub with:
# grub-mkconfig -o /boot/grub/grub.cfg
Last edited by DetotatedWam (2015-04-01 22:12:06)

Boot\ Secure Boot menu >
Secure Boot state: Disabled
Platform Key (PK) state: Unloaded
OS Type: Windows UEFI mode
I have tried setting "OS Type" to "Other OS" before but that doesn't change anything. I just tried it again and the BIOS freezes upon "Save Changes & Reset".
Boot\ Secure Boot menu\ Key Management >
PK Management: Unloaded
KEK Management: Unloaded
DB Management: Unloaded
DBX Management: Unloaded
The other day, I deleted all of them and backed them up on a USB in order to disable secure boot.
Note: After looking at this menu again I am noticing options to append from file for KEK, DB, and DBX that might help.
Append KEK from File
Allows you to load the additional
KEK from a storage device for an
additional db and dbx loaded
management.
[Yes]
Load the default KEK
[No]
Load from a USB storage device
Append db from File
Allows you to load the additional db
variable from a storage device so
that more custom signed UEFI
executble files can be loaded.
*UEFI executabled files include UEFI
boot loaders, drivers and
applications.
[Yes]
Load the default db
[No]
Load from a USB storage device
Append dbx from File
Allows you to load the additional
dbx variable from a storage device
so that more custom signed UEFI
executble files cannot be loaded.
*UEFI executabled files include UEFI
boot loaders, drivers and
applications.
[Yes]
Load the default dbx
[No]
Load from a USB storage device
Boot\ CSM (Compatibility Support Module)
Launch CSM: Enabled
Boot Device Control: UEFI and Legacy OPROM
Boot from Network Devices: Legacy OPROM first
Boot from Storage Devices: Both, UEFI first
Boot from PCI-E/PCI Expansion Devices: Legacy OPROM first
As a side note: After a reboot, I noticed the Arch boot option disappeared again.
Head_on_a_Stick wrote:Have you managed to boot any other distributions that are not compatible with Secure Boot?
I have been able to boot Windows 7 and ubuntu but I beleive both are compatible with Secure Boot so, no.
Head_on_a_Stick wrote:The Arch live ISO has the EFI applications PreLoader.efi & HashTool.efi included so that will boot up with Secure Boot enabled.
I will try this and post the results.
Edit: Now my BIOS Freezes everytime I try to save & exit.
Last edited by DetotatedWam (2015-04-01 19:59:18)

T440s & Windows 7 in UEFI mode

Hi,
I try to install Windows 7 on my T440s. However, I fail booting the USB stick with error code 0xc000000d ("An error occurred while attempting to read the boot configuration data"). I created the USB stick as described in the Forum here (http://forums.lenovo.com/t5/Windows-7-Knowledge-Base/Prepare-an-usb-thumb-drive-to-boot-windows-7-in...). Also, the USB-Stick boots fine in UEFI mode on my old (HP) Laptop. Also I can boot on CSM-Mode Compatibility Support Module. I tried several other how-tos and what else Google answered search fo that error code (e.g. disabling USB3, disable nearly everything the UEFI BIOS could disable etc...). It really seems to be an issue in conjunction with that UEFI implementation...
I'm using latest UEFI BIOS (GJET64WW, 2.14).
Anyone successfully installed Windows 7 on that model? Any help would be appriciated.
Best regards,
falstaff
Solved!
Go to Solution.

Hi,
What do you mean by Also I can boot on CSM-Mode Compatibility Support Module ?
Windows 7 won't run in UEFI mode without CSM enabled. IIRC it may boot but won't run.
I don't have a T440s to test with, but here's how I make and boot a Win 7 UEFI installer: format a flash drive as a single partition - FAT32. Use an (un)archiving tool like 7zip in Windows to extract the contents of a Win 7 SP1 installer ISO to a flash drive. (or just copy a DVD to flash).
Boot it and install. IIRC the file manipulation required to create a bootable flash drive applied to pre-SP1 Win 7.
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Booting in UEFI mode

Similar Messages

Maybe you are looking for