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, visit the following Microsoft website:
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.
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:
Use Windows Defender Offline to make sure that no malware is present on the system. For more information, go to the following Microsoft webpage:
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, and 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, visit the following Microsoft website:
You receive a 0x800f0922 error when you try to install this security update
Symptoms Consider the following two configurations:
Scenario one You have a Windows Server 2012-based server that uses UEFI firmware and has the Secure Boot option enabled.
Scenario two You have a Windows Server 2012 R2-based Hyper-V host running and you 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 2871690 may not install, and you receive a 0x800f0922 error message.
Cause This error occurs because the installer for security update 2871690 incorrectly expects BitLocker to be installed.
Workaround To work around this issue, use one of the following methods, based on your scenario:
Workaround for scenario one Install the BitLocker optional component on the server that uses UEFI and that has the Secure Boot option enabled.
Workaround for scenario two Install the BitLocker optional component on the guest virtual machine in the Hyper-V configuration.
Note You do not have to configure BitLocker on any drive. It is only necessary for the BitLocker component to be present on Window Server 2012 when you install security update 2871690.
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.
Windows 8 and Windows Server 2012 file information
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
6.2.920 0.16 xxx
Windows 8 and Windows Server 2012
6.2.920 0.20 xxx
Windows 8 and Windows Server 2012
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
Note The MANIFEST files (.manifest) and MUM files (.mum) that are installed are not listed.
For all supported x86-based versions of Windows 8
For all supported x64-based versions of Windows 8 and Windows Server 2012