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:

For all supported x86-based versions of Windows 8

Download Download the update package now.

For all supported x64-based versions of Windows 8

Download Download the update package now.

For all supported x64-based versions of Windows Server 2012

Download Download the update package now.

For all supported x86-based versions of Windows 8.1

Download Download the update package now.

For all supported x86-based versions of Windows 8.1 without update 2919355 installed

Download Download the update package now.

For all supported x64-based versions of Windows 8.1

Download Download the update package now.

For all supported x64-based version of Windows 8.1 without update 2919355 installed

Download Download the update package now.

For all supported x64-based versions of Windows Server 2012 R2

Download Download the update package now.

For all supported x64-based versions of Windows Server 2012 R2 without update 2919355 installed

Download Download the update package now.

Release Date: May 13, 2014

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

File name

SHA1 hash

SHA256 hash

Windows8-RT-KB2920189-x64.msu

FE5DE44CE540BB7DEC0352124285F280C1897C3C

D87E59FE445D3984450E24FA19BCF9F6DC7BFAE25A16C946B5E0F6EA1E41A97A

Windows8-RT-KB2920189-x86.msu

92991DD8A5CD43DD154737C47EDEBF0ADE1CEC07

A02D667EBEEDA34BF5F7367AB82C9FAF1CC0A05D4816C12B3BC31E57968F9C2D

Windows8.1-KB2920189-x64.msu

C24ED9942FC5620F15E4FF8E397BF3BD14B898FC

D07AEBD62E4C13024C8AE825303CC91CB8D49EEEC0A921ECBE46B47EDB59A407

Windows8.1-KB2920189-x86.msu

8580BC54511D58EE473E09811F139636D93067F7

9C44D060EDCB758068D9673A7A4336AF9B3480FEEF44F899A13BAA0A1F411FF0

Windows8.1-KB2961908-x64.msu

A52E1FDF7F4EBE32535F61C4F0E60B8E3905DD01

C80716AA8B6C692A6DF1DE7C19C4A6736B867056F3794066CC13EFA4E9D15E01

Windows8.1-KB2961908-x86.msu

4BD6069836A5CF21DA6BEFF828362279A2265D77

56307CDA19CF936B1C3234774B9D0A693F1A4B4A9C187AE9E365C479A846C484


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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×