Unified Extended Firmware Interface support in Windows Vista
| Article ID | : | 930061 |
| Last Review | : | October 26, 2007 |
| Revision | : | 1.4 |
INTRODUCTION
MORE INFORMATION
Microsoft determined that vendors would not have any interest in producing native UEFI 32-bit firmware because of the current status of mainstream 64-bit computing and platform costs. Therefore, Microsoft has chosen not to ship support for 32-bit UEFI implementations.
Rigorous testing on a variety of UEFI implementations on a variety of hardware platforms must be performed before Microsoft can provide support for UEFI. As of mid-2006, no firmware vendors had provided production-ready UEFI implementations. When Windows Server 2008 is released, it is expected that enough production-quality UEFI implementations will be available then for Microsoft to work with hardware vendors to test UEFI implementations on a variety of platforms.
Microsoft is working closely with the Unified EFI Forum and industry partners to make sure that it can provide a high-quality, standards-based UEFI solutions. Microsoft has demonstrated Windows support for starting the computer by using a native UEFI boot at industry events such as Windows Hardware Engineering Conference (WinHEC).
As part of this continuing effort, Microsoft also made technology preview code for UEFI boot support available in the Vista Beta 2 release. This technology preview enabled partners to test their UEFI implementations to make production-ready samples available for Microsoft for testing support in Windows. The technology preview code was removed for the Windows Vista release candidates (RC) and final release to manufacturing.
However, support for well-tested UEFI will be made available in a future update to Windows Vista. The supporting code will be present for Windows Server 2008.
To ease the transition from BIOS boot to UEFI boot, we recommend that you design your software carefully so that differences between UEFI and BIOS in the operating system are not noticeable to the end-user
The following items are the most significant UEFI and BIOS boot considerations:
| • | To install the operating system by using UEFI, the installation must be started by using UEFI. Similarly, to install the operating system by using BIOS, the installation must be started by using BIOS. | ||||||||
| • | If the operating system is installed by using UEFI, it can only be started by using UEFI. This is because the BIOS cannot access the Boot Configuration Data (BCD) boot options on the EFI System Partition (ESP). | ||||||||
| • | The Windows installation disc will be able to start either by using UEFI or by using BIOS. El Torito multiple boot catalog support is used for this capability:
|
||||||||
| • | By default for platforms that support UEFI and BIOS, we recommend that the platform start by using EFI. | ||||||||
| • | Windows Vista supports both CD boot and DVD/UDFS boot. UDFS also uses El Torito and is built by using the UDFS bridge format. | ||||||||
| • | A UEFI-based system requires a separate EFI system partition (ESP). We recommend that BIOS systems also use a separate system partition so that Windows Vista and Windows Server 2008 features such as BitLocker Drive Encryption function correctly. Use of separate EFI and BIOS system partitions will also enable a smoother transition to EFI systems. | ||||||||
| • | For SysPrep migration between EFI and BIOS systems, Windows state should not be maintained on the system partition. |
REFERENCES
| • | EFI and Windows Vista
http://www.microsoft.com/whdc/system/platform/firmware/efibrief.mspx (http://www.microsoft.com/whdc/system/platform/firmware/efibrief.mspx)
|
| • | ACPI specification
http://www.acpi.info (http://www.acpi.info)
|
| • | El Torito specification
http://www.phoenix.com/NR/rdonlyres/98D3219C-9CC9-4DF5-B496-A286D893E36A/0/specscdrom.pdf (http://www.phoenix.com/NR/rdonlyres/98D3219C-9CC9-4DF5-B496-A286D893E36A/0/specscdrom.pdf)
|
| • | Microsoft BitLocker Drive Encryption white paper
http://technet.microsoft.com/en-us/windowsvista/aa906018.aspx (http://technet.microsoft.com/en-us/windowsvista/aa906018.aspx)
|
| • | Boot Configuration Data
http://msdn2.microsoft.com/en-us/library/aa362692.aspx (http://msdn2.microsoft.com/en-us/library/aa362692.aspx)
|
| • | Microsoft Extensible Firmware Initiative FAT32 File System Specification
http://www.microsoft.com/whdc/system/platform/firmware/fatgen.mspx (http://www.microsoft.com/whdc/system/platform/firmware/fatgen.mspx)
|
| • | Microsoft Platform Design portal
http://www.microsoft.com/whdc/system/platform/default.mspx (http://www.microsoft.com/whdc/system/platform/default.mspx)
|
| • | Microsoft Portable Executable and Common Object File Format Specification
http://www.microsoft.com/whdc/system/platform/firmware/PECOFF.mspx (http://www.microsoft.com/whdc/system/platform/firmware/PECOFF.mspx)
|
| • | Unified EFI Update [WinHEC 2005 Presentation]
http://www.microsoft.com/whdc/system/platform/firmware/default.mspx (http://www.microsoft.com/whdc/system/platform/firmware/default.mspx)
|
| • | United Extensible Firmware Interface Specification
http://www.uefi.org (http://www.uefi.org)
|
APPLIES TO
| • | Windows Vista Ultimate |
| • | Windows Vista Starter |
| • | Windows Vista Home Premium |
| • | Windows Vista Home Basic |
| • | Windows Vista Enterprise |
| • | Windows Vista Business 64-bit Edition |
| • | Windows Vista Business |
| • | Windows Vista Ultimate 64-bit Edition |
| • | Windows Vista Home Premium 64-bit Edition |
| • | Windows Vista Home Basic 64-bit Edition |
| • | Windows Vista Enterprise 64-bit Edition |
| • | Windows Server 2008 Datacenter without Hyper-V |
| • | Windows Server 2008 Enterprise without Hyper-V |
| • | Windows Server 2008 for Itanium-Based Systems |
| • | Windows Server 2008 Standard without Hyper-V |
| • | Windows Server 2008 Datacenter |
| • | Windows Server 2008 Enterprise |
| • | Windows Server 2008 Standard |
| • | Windows Web Server 2008 |
Keywords:Â |
kbinfo kbtshoot kbexpertiseinter KB930061 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Back to the top
Leave a Reply