For
Windows Hyper-V hosts, this article you are reading contains the released hotfix to
be installed on the Hyper-V Host to fix this issue for Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 Hyper-V Hosts.
For
VMware hosts,
contact your original equipment manufacturer to obtain the updated firmware that contains the fixed Intel microcode. VMware hosts must have this BIOS update installed to fix the issue. As per VMware, please open a support ticket with VMware referencing
PR #1178834 to log the issue.
Additionally, this issue can also be fixed by upgrading the Intel processors on the Hyper-V or VMware hosts.
Get the hotfix for Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites
To apply this hotfix, you must be running Windows Server 2012 R2, Windows Server 2012 or Windows Server 2008 R2 SP1.
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 file information notes
Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
- 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:
Version | Product | Milestone | Service branch |
---|
6.3.960 0.17 xxx | Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 | RTM | GDR |
- The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File name | File version | File size | Date | Time | Platform |
---|
Mcupdate_genuineintel.dll | 6.3.9600.17227 | 478,528 | 04-Jul-2014 | 21:29 | x64 |
Windows RT, Windows 8, and Windows Server 2012 file information notes
Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
- The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version | Product | Milestone | Service branch |
---|
6.2.920 0.16 xxx | Windows RT, Windows 8, and Windows Server 2012 | RTM | GDR |
6.2.920 0.21xxx | Windows RT, Windows 8, and Windows Server 2012 | RTM | LDR |
- 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.
- The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File name | File version | File size | Date | Time | Platform |
---|
Mcupdate_genuineintel.dll | 6.2.9200.17048 | 485,696 | 07-Jul-2014 | 06:43 | x64 |
Mcupdate_genuineintel.dll | 6.2.9200.21166 | 485,696 | 07-Jul-2014 | 06:50 | x64 |
Windows 7 and Windows Server 2008 R2 file information and notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
- 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:
Version | Product | Milestone | Service branch |
---|
6.1.760 1.18xxx | Windows 7 and Windows Server 2008 R2 | SP1 | GDR |
6.1.760 1.22xxx | Windows 7 and Windows Server 2008 R2 | SP1 | LDR |
- The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File name | File version | File size | Date | Time | Platform |
---|
Mcupdate_genuineintel.dll | 6.1.7601.18548 | 443,320 | 02-Aug-2014 | 02:12 | x64 |
Mcupdate_genuineintel.dll | 6.1.7601.22758 | 443,320 | 02-Aug-2014 | 02:04 | x64 |