Microsoft security advisory: Update rollup of revoked noncompliant UEFI modules

INTRODUCTION

Microsoft has released a Microsoft security advisory about this issue for IT professionals. The security advisory contains additional security-related information. To view the security advisory, go to the following Microsoft website:

https://technet.microsoft.com/security/advisory/2962824

More Information

The following files are available for download from the Microsoft Download Center:

Known issues with this security update

• You cannot start the computer after you install this security update
  
  
  
  If you install this security update on a system that uses a noncompliant Unified Extensible Firmware Interface (UEFI) module, you may be unable to start the computer.
  
  If your system will not start after you install this security update, follow these steps:
  

  1. Use Windows Defender Offline to make sure that no malware is present on the system. For more information, go to the following Microsoft webpage:
     

     http://windows.microsoft.com/en-US/windows/what-is-windows-defender-offline

  2. Restart the computer by using recovery media (on USB, DVD, or network [PXE] restart), and then perform recovery operations. For more information, go to the following Microsoft webpage:

     http://technet.microsoft.com/en-us/library/hh824874.aspx

  To avoid this issue, we recommend that you apply this update after you remove noncompliant UEFI modules from your system to make sure that the system can successfully start. Also, consider upgrading to compliant UEFI modules if they are available. 
  
  For more information about your UEFI module, contact the UEFI module supplier. This might include the system vendor, the plug-in card vendor, or other UEFI software vendors such as UEFI backup and restore solutions, UEFI anti-malware, and so on.
  
  For information about how to contact the UEFI module supplier, go to the following Microsoft website:

  http://support.microsoft.com/gp/vendors
  
  

• You receive a 0x800f0922 error when you try to install this security update
  
  Symptoms
  Consider the following two configurations:
  

  • Configuration 1
    You have a Windows Server 2012-based server that uses UEFI firmware and has the Secure Boot option enabled.

  • Configuration 2
    You have a Windows Server 2012 R2-based Hyper-V host running and are running a Generation 2 virtual machine guest that uses UEFI firmware support and has the Secure Boot option enabled. The guest virtual machine is running Windows 8 or Windows Server 2012.

  In these configurations, security update 2962824may not install, and you receive a 0x800f0922 error message. 
  
  Cause
  This error occurs because the installer for security update 2962824 incorrectly expects BitLocker to be installed.
  
  
  Workaround
  To work around this issue, use one of the following methods, based on your scenario:

  • Workaround for configuration 1
    Install the BitLocker optional component on the server that uses UEFI and that has the Secure Boot option enabled.
    

  • Workaround for configuration 2
    Generation 2 virtual machines are not affected by this issue, and you do not have to install the update in this case.

  Note You do not have to configure BitLocker on any drive. It is necessary only for the BitLocker component to be present on Window Server 2012 when you install security update 2962824.

More information about this security updateThe following articles contain more information about this security update as it relates to individual product versions. The articles may contain known issue information. If this is the case, the known issue is listed under each article link.

• 2920189 Description of the update rollup of revoked noncompliant UEFI modules: May 13, 2014

• 2961908 Description of the update rollup of revoked noncompliant UEFI modules: May 13, 2014