BIOS setting(s) to Install Windows Using UEFI

I'll answer the question, but fyi although Windows 7 can boot in UEFI mode (sort of, see below), it does not take advantage of any UEFI benefits.  The ONLY reasons you should install Windows 7 in UEFI mode are if you a) want to install it on a disk larger than 2TB and/or b) want to install Windows 7 and some OTHER operating system that uses UEFI mode on the same disk.  If neither of those applies to you, then you may as well install it in Legacy mode.

But if you're determined to use UEFI, even when Windows 7 is set up in UEFI mode, it still has some Legacy BIOS dependencies.  If you try to boot it on a system that is pure UEFI, it will blue screen.  To make it work, you need to disable Secure Boot and then also ENABLE Legacy Option ROMs.  But despite doing that, when you choose to boot from your installation media under the F12 one-time boot menu, you have to select the option for your device under the UEFI section, NOT the Legacy section.  Legacy Option ROMs is normally enabled to allow Legacy booting, but in this case it just allows Windows 7's legacy dependencies to be used even when it boots in UEFI.  Anyhow, as long as you boot your installation media in UEFI mode, Windows Setup will install the OS onto your disk in UEFI mode.

---

@EngiProg wrote:

Thanks jphughan:

I thought I had to change some setting(s) in BIOS to Boot for UEFI to make GPT disk

 

---

The BIOS changes you have to make are to put your system into UEFI mode rather than Legacy, and then enable Legacy Option ROMs (which requires you to disable Secure Boot).  That configuration allows your system to boot in UEFI mode even for Windows 7.  In terms of a GPT disk, that's handled by Windows Setup.  Again, as long as you boot your Windows installation media in UEFI mode, it will automatically install the OS onto your hard drive in UEFI mode, which includes setting up the disk as GPT.  If you already have data on that disk, then at the step where you select where to install Windows, delete all existing partitions on that disk until the entire disk shows up as unallocated space, then select that.  Windows will handle the rest.

Thanks jphughan:

I thought I had to change some setting(s) in BIOS to Boot for UEFI to make GPT disk

@EngiProg, one other bit of advice for you. Since you're performing a clean install of Windows 7 in 2019, you'll want to manually download a few other updates beforehand rather than planning to just use Windows Update when it gets installed.  You will save a huge amount of time.  The reason is that Windows 7 SP1 is very old now, so if you don’t do this, you could spend many hours installing hundreds of updates over several reboots.  In fact, the version of Windows Update included in original SP1 has an issue that causes it to sometimes take hours to even figure out what needs to be downloaded, before it actually downloads anything. It simply wasn't designed for the size of the update catalog that exists today.

Fortunately, manually downloading the updates below will avoid that. Just Google the KB numbers to find the download links. This assumes you're start from SP1, otherwise download and install SP1 first, then install these updates in this order:

- KB3020369: April 2015 Servicing Stack Update (required to install subsequent updates)

- KB3125574: Windows 7 Convenience Update (takes you from SP1's February 2011 state all the way to April 2016 in one big package rather than hundreds of individual updates)

- KB3172605: July 2016 Update Rollup (includes the fix for very long Windows Update scan times, so after installing this, you may still have a few dozen updates, but at least you won't be waiting potentially hours for them to even start downloading).

Fyi though, Microsoft will stop providing security updates for Windows 7 in January 2020, and if Windows XP's retirement is any indication, browser vendors will stop providing updates on Windows 7 shortly afterward, so if you plan to keep this system longer than that, you might want to think about upgrading to Windows 10 sooner rather than later.

Hello jphughan:

Thanks for advising, whenever I do a clean install, I always download the latest build, which I believe reduces massive updates

I’m unsure if I could get all the latest drivers for this laptop (Latitude E6420) for Windows 10 64-bit (knowing most of the W7 onward drivers work with W10), could you please provide URL for latest W10 Pro 64-bit for this laptop

Thanking you in advance

---

@EngiProg wrote:

Hello jphughan:

Thanks for advising, whenever I do a clean install, I always download the latest build, which I believe reduces massive updates

I’m unsure if I could get all the latest drivers for this laptop (Latitude E6420) for Windows 10 64-bit (knowing most of the W7 onward drivers work with W10), could you please provide URL for latest W10 Pro 64-bit for this laptop

Thanking you in advance

---

Microsoft hasn't provided updated Windows 7 media since SP1, so downloading it now will not give you any additional updates -- which is why I made the suggestion above.  Dell doesn't offer Windows 10 drivers for that system, but it does offer Windows 8 drivers, so it's likely that Windows Update would provide the necessary Windows 10 drivers.  If you're missing any low-priority drivers after that, it's very likely that the Windows 8 drivers will work.

Hi jphughan:

Thanks on the heads-up on media update of W7 download from MS

I’d go for W10 Pro 64-bit as long as following are available:

1. Audio
2. Network (LAN & WiFi)
3. Video

Anyone who experienced may please chime

Thank you

---

@EngiProg wrote:

Hi jphughan:

Thanks on the heads-up on media update of W7 download from MS

I’d go for W10 Pro 64-bit as long as following are available:

1. Audio
2. Network (LAN & WiFi)
3. Video

Anyone who experienced may please chime

Thank you

 

---

Those will definitely be available because that system uses Intel and Realtek for those items, and both Intel and Realtek provide drivers through Windows Update.  In fact given the age of that system, you'll probably find that Windows 10 has support for those things out of the box.

UEFI is only windows 8 or 10.

WINDOWS 7 SUPPORTS GPT but does not support UEFI SECURE BOOT.

E6420   E6420ATG  SYSTEMS are windows 8 MAX

as far as released drivers.

https://www.dell.com/support/article/us/en/19/how13996/latitude-e6420-windows-8-driver-cab?lang=en

https://www.dell.com/support/article/us/en/19/how13793/latitude-e6420-windows-7-driver-cab?lang=en

E6420XFR
https://www.dell.com/support/article/us/en/19/sln312677/latitude-e6420xfr-windows-7-driver-cab?lang=en

GPT is a partition type that goes back to XP.

You cannot make a GPT partition boot in XP.

Any Partition larger than 2TB requires 64 bit windows OS.

Partitions larger than 2TB require INTEL RST Drivers version 10.1.0.1008 or Higher.

Windows 8 and 10 drivers are not available for older models but that does not mean you cannot use VISTA or  Windows 7  WDDM 1.0 drivers in windows 8 or 10.

Single Driver packages for a specific series are available.

https://www.dell.com/support/article/us/en/19/sln312414/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment?lang=en

Not Supported is not the same as not working with windows 8 or 10.

Hello All!

I’m sorry to be little late, I have latest BIOS A25 installed, I’ve two issues at the moment which I’d like to resolve before proceeding for fresh W10 installation

1. Device Manager is showing my system as E6249 – don’t know why?
   It should be E6240 as on boot splash screen
   
   
   
2. Bluetooth installation failed – can someone provide solution reviewing log?
   Need help on this please
   
   

Log First attempt

[03/15/19 20:17:53] Update Package Execution Started
[03/15/19 20:17:53] Original command line: "D:\Drivers\Dell 6420\Driver\Network\Bluetooth\Network_Driver_1G1GX_WN32_6.3_A07.EXE"
[03/15/19 20:17:53] DUP Framework EXE Version: 3.0.92.1
[03/15/19 20:17:53] DUP Release: 1G1GXA00-00
[03/15/19 20:17:53] Intializing framework...
[03/15/19 20:17:55]
[03/15/19 20:18:19] User Command: attended
[03/15/19 20:18:19] DUP Capabilities Value: 8388607 (0x7FFFFF)
[03/15/19 20:18:19] DUP Vendor Software Version: 6.3
[03/15/19 20:18:19] Local System/Model Compatible with this Package? Yes
[03/15/19 20:18:19] Local System OS Version: 6.1.1.0
[03/15/19 20:18:19] OS Compatible with this Package? Yes
[03/15/19 20:18:19] Local System OS Language: EN
[03/15/19 20:18:19] Language Compatible with this Package? Yes
[03/15/19 20:18:19] (DupAPI::ExtractPayloadTo): *** Extraction Error: 9
[03/15/19 20:18:19]
[03/15/19 20:18:19] Name of Exit Code: ERROR
[03/15/19 20:18:19] Exit Code set to: 1 (0x1)
[03/15/19 20:18:19] Result: FAILURE
[03/15/19 20:18:30] Open file: C:\Users\Dell\AppData\Local\Dell\UpdatePackage\Log\Network_Driver_1G1GX_WN32_6.3_A07.txt

Log Second attempt

[03/15/19 20:17:53] Update Package Execution Started
[03/15/19 20:17:53] Original command line: "D:\Drivers\Dell 6420\Driver\Network\Bluetooth\Network_Driver_1G1GX_WN32_6.3_A07.EXE"
[03/15/19 20:17:53] DUP Framework EXE Version: 3.0.92.1
[03/15/19 20:17:53] DUP Release: 1G1GXA00-00
[03/15/19 20:17:53] Intializing framework...
[03/15/19 20:17:55]
[03/15/19 20:18:19] User Command: attended
[03/15/19 20:18:19] DUP Capabilities Value: 8388607 (0x7FFFFF)
[03/15/19 20:18:19] DUP Vendor Software Version: 6.3
[03/15/19 20:18:19] Local System/Model Compatible with this Package? Yes
[03/15/19 20:18:19] Local System OS Version: 6.1.1.0
[03/15/19 20:18:19] OS Compatible with this Package? Yes
[03/15/19 20:18:19] Local System OS Language: EN
[03/15/19 20:18:19] Language Compatible with this Package? Yes
[03/15/19 20:18:19] (DupAPI::ExtractPayloadTo): *** Extraction Error: 9
[03/15/19 20:18:19]
[03/15/19 20:18:19] Name of Exit Code: ERROR
[03/15/19 20:18:19] Exit Code set to: 1 (0x1)
[03/15/19 20:18:19] Result: FAILURE
[03/15/19 20:18:30] Open file: C:\Users\Dell\AppData\Local\Dell\UpdatePackage\Log\Network_Driver_1G1GX_WN32_6.3_A07.txt
[03/15/19 21:01:45] Name of Exit Code: ERROR
[03/15/19 21:01:45] Execution terminated at date-time 03/15/19 21:01:45
[03/15/19 21:01:45] ######

਍਍[03/15/19 23:03:49] Update Package Execution Started
[03/15/19 23:03:50] Original command line: "D:\Drivers\Dell 6420\Driver\Network\Bluetooth\Network_Driver_1G1GX_WN32_6.3_A07.EXE"
[03/15/19 23:03:50] DUP Framework EXE Version: 3.0.92.1
[03/15/19 23:03:50] DUP Release: 1G1GXA00-00
[03/15/19 23:03:50] Intializing framework...
[03/15/19 23:03:57]
[03/15/19 23:04:01] User Command: attended
[03/15/19 23:04:01] DUP Capabilities Value: 8388607 (0x7FFFFF)
[03/15/19 23:04:01] DUP Vendor Software Version: 6.3
[03/15/19 23:04:01] Local System/Model Compatible with this Package? Yes
[03/15/19 23:04:01] Local System OS Version: 6.1.1.0
[03/15/19 23:04:01] OS Compatible with this Package? Yes
[03/15/19 23:04:01] Local System OS Language: EN
[03/15/19 23:04:01] Language Compatible with this Package? Yes
[03/15/19 23:04:02] (DupAPI::ExtractPayloadTo): *** Extraction Error: 9
[03/15/19 23:04:02] Identified Behavior : attended
[03/15/19 23:04:02]
[03/15/19 23:04:02]
[03/15/19 23:04:02] Name of Exit Code: ERROR
[03/15/19 23:04:02] Exit Code set to: 1 (0x1)
[03/15/19 23:04:02] Result: FAILURE
[03/15/19 23:04:07] Name of Exit Code: ERROR
[03/15/19 23:04:07] Execution terminated at date-time 03/15/19 23:04:07
[03/15/19 23:04:07] ######

਍਍[03/16/19 20:02:38] Update Package Execution Started
[03/16/19 20:02:38] Original command line: "D:\Drivers\Dell 6420\Driver\Network\Bluetooth\Network_Driver_1G1GX_WN32_6.3_A07.EXE"
[03/16/19 20:02:38] DUP Framework EXE Version: 3.0.92.1
[03/16/19 20:02:38] DUP Release: 1G1GXA00-00
[03/16/19 20:02:38] Intializing framework...
[03/16/19 20:02:38]
[03/16/19 20:03:21] User Command: attended
[03/16/19 20:03:21] DUP Capabilities Value: 8388607 (0x7FFFFF)
[03/16/19 20:03:21] DUP Vendor Software Version: 6.3
[03/16/19 20:03:21] Local System/Model Compatible with this Package? Yes
[03/16/19 20:03:21] Local System OS Version: 6.1.1.0
[03/16/19 20:03:21] OS Compatible with this Package? Yes
[03/16/19 20:03:21] Local System OS Language: EN
[03/16/19 20:03:21] Language Compatible with this Package? Yes
[03/16/19 20:03:21] (DupAPI::ExtractPayloadTo): *** Extraction Error: 9
[03/16/19 20:03:21] Identified Behavior : attended
[03/16/19 20:03:22]
[03/16/19 20:03:22] Name of Exit Code: ERROR
[03/16/19 20:03:22] Exit Code set to: 1 (0x1)
[03/16/19 20:03:22] Result: FAILURE
[03/16/19 20:03:59] Open file: C:\Users\Dell\AppData\Local\Dell\UpdatePackage\Log\Network_Driver_1G1GX_WN32_6.3_A07.txt

Thanks in advance

---

@speedstep wrote:

UEFI is a type of BIOS

GPT is a partition Type.

They are not one and the same thing.

 

---

Yes I realize that, but they are related in that an OS booting in Legacy BIOS mode can only boot from MBR disks, and an OS booting in UEFI mode typically boots from a GPT disk but also supports MBR in order to allow things like having a flash drive that can be used to boot in Legacy BIOS or UEFI mode.  But the fact remains that if you're booting from a GPT disk, the OS is booting in UEFI mode, because again, OSes booting in Legacy BIOS mode cannot boot from GPT disks.

---

@speedstep wrote:

UEFI is only windows 8 or 10.

WINDOWS 7 SUPPORTS GPT but does not support UEFI SECURE BOOT.

GPT is a partition type that goes back to XP.

Any Partition larger than 2TB requires 64 bit windows OS.

 

---

@speedstep, the fact that Win7 does not support UEFI Secure Boot does not mean that it does not support UEFI.  It does (partially), as I explained above.  If you can boot an OS from a GPT disk, then the OS supports UEFI.  Win8 and above have better UEFI support, but it's not accurate to say that UEFI is only for Win8 and 10.

GPT is not a partition type that goes back to XP.  Only the rarely used Windows XP 64-bit edition supported GPT disks, along with Server 2003 SP1; Windows XP 32-bit didn't support GPT disks at all.

You don't need a 64-bit OS to work with a partition larger than 2TB.  The partition needs to be on a GPT disk, but 32-bit versions of Windows from Vista onward have supported those.  Booting from a partition that size requires UEFI, but again that is not necessarily limited to 64-bit.

UEFI is a type of BIOS

GPT is a partition Type.

(GPT) was introduced as part of the Unified Extensible Firmware Interface (UEFI) initiative. GPT provides a more flexible mechanism for partitioning disks than the older Master Boot Record (MBR) partitioning scheme that was common to PCs. PRIOR to UEFI GPT did not exist.

Is UEFI required for a GPT disk?

No. GPT disks are self-identifying. All the information needed to interpret the partitioning scheme of a GPT disk is completely contained in structures in specified locations on the physical media.

Can the 32- and 64-bit versions of Windows Server 2003 read, write, and boot from GPT disks?

Starting with Windows Server 2003 Service Pack 1, all versions of Windows Server can use GPT partitioned disks for data. Booting is only supported for 64-bit editions on Itanium-based systems.

Can Windows Vista, Windows Server 2008, and later read, write, and boot from GPT disks?

Yes, all versions can use GPT partitioned disks for data. Booting is only supported for 64-bit editions on UEFI-based systems.

Can Windows 2000, Windows NT 4, or Windows 95/98 read, write, and boot from GPT?

No.  Legacy software will see only the Protective MBR.

Windows XP can Create a GPT partition.  It Cannot However Boot from it EVER.

They are not one and the same thing.

UEFI CLASS 2.3.1 and up is Windows 8 and Later.

UEFI CLASS 3.0  is windows 10 and DOES NOT Support MBR or DOS or XP or Linux or anything that relies on MSDOS INT 13 bios booting.

How can a drive letter in the operating system be mapped to a partition in UEFI firmware?

There is no inherent mapping between drive letter and partition that can be used to determine one from the other. A basic data partition must be identified by its partition GUID.

How can an ESP partition be created?

ESP partitions can be created by using the UEFI firmware utility Diskpart.efi or the Windows command line utility Diskpart.exe.

What is the Extensible Firmware Interface System Partition (ESP)?

The ESP contains the NTLDR, HAL, Boot.txt, and other files that are needed to boot the system, such as drivers. The Partition GUID defines the ESP:

UEFI LEGACY VS Secure Boot

What is Secure boot anyway?

BIOS VS UEFI

LEGACY VS SECURE BOOT

Under WINDOWS 7 BIOS/MBR mode: SYSTEM / WINDOWS / RECOVERY

Under WINDOWS 8 / 10 UEFI/GPT mode: SYSTEM / MSR / WINDOWS / RECOVERY

The user is complaining that there is no MSR but you DO NOT GET ONE in windows 7.

The GPT partition has nothing to do with Booting the ESP is where booting happens.  If you are missing ESP and or you are running 32 bit OS you will not EVER be booting a GPT disk.

What is the Extensible Firmware Interface System Partition (ESP)?

The ESP contains the NTLDR, HAL, Boot.txt, and other files that are needed to boot the system, such as drivers. The Partition GUID defines the ESP:

Do only GPT Disks have ESPs?

No, MBR disks can also have ESPs. UEFI specifies booting from either GPT or MBR. The ESP on an MBR disk is identified by partition type 0xEF. However, Windows does not support booting UEFI from MBR disks or 0xEF partitions.

Where should the ESP be placed on the disk?

The ESP should be first on the disk. The primary benefit to placing the ESP first, is that it is impossible to span volumes when the ESP is logically between the two data partitions that you are attempting to span.

Windows 10 disks have 4 parts.  The MSR /RECOVERY/ ESP /OS

What is a Microsoft Reserved Partition (MSR)?

The Microsoft Reserved Partition (MSR) reserves space on each disk drive for subsequent use by operating system software. GPT disks do not allow hidden sectors. Software components that formerly used hidden sectors now allocate portions of the MSR for component-specific partitions. For example, converting a basic disk to a dynamic disk causes the MSR on that disk to be reduced in size and a newly created partition holds the dynamic disk database. The MSR has the Partition GUID:

DEFINE_GUID (PARTITION_MSFT_RESERVED_GUID, 0xE3C9E316L, 0x0B5C, 0x4DB8, 0x81, 0x7D, 0xF9, 0x2D, 0xF0, 0x02, 0x15, 0xAE)

Every GPT disk must contain an MSR. The order of partitions on the disk should be ESP (if any), OEM (if any) and MSR followed by primary data partition(s). It is particularly important that the MSR be created before other primary data partitions. The MSR and any partitions created from the MSR are only visible from the command line.

You can't see the MSR but its there.  The SYSTEM area gets larger and larger with each version of windows.  Windows 8 makes this 350 meg,  Windows 10 1809 makes it 550 meg.

DISK Management View

---

@speedstep wrote:

A MBR disk can be basic or dynamic, just like an GPT disk can be basic or dynamic. Compared with MBR disk, a GPT disk performs better in the followinig aspects:

• A GPT disk supports larger than 2 TB volumes while MBR cannot. 

• The GPT disk partitioning style supports volumes up to 18 exabytes in size and up to 128 partitions per disk while the MBR disk partitioning style supports volumes up to 2 terabytes in size and up to 4 primary partitions per disk (or three primary partitions, one extended partition, and unlimited logical drives).  

• GPT disk provides greater reliability due to replication and cyclical redundancy check (CRC) protection of the partition table. Unlike MBR partitioned disks, data critical to platform operation is located in partitions instead of unpartitioned or hidden sectors. 

• PT partitioned disks have redundant primary and backup partition tables for improved partition data structure integrity.

---

You seem to like copy/pasting content from other places without actually citing them.  You took this entire segment from this page. You even carried over the typos from that page where "following" was misspelled and the last bullet point just said "PT" rather than "GPT".