To apply this hotfix, you must be running Windows Server 2012 R2, Windows Server 2012 or Windows Server 2008 R2 SP1. If you do not see your language, it is because a hotfix is not available for that language. The "Hotfix download available" form displays the languages for which the hotfix is available. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: ![]() The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. This hotfix might receive additional testing. Apply this hotfix only to systems that are experiencing the problem described in this article. However, this hotfix is intended to correct only the problem that is described in this article. Get the hotfix for Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2Ī supported hotfix is available from Microsoft. As per VMware, please open a support ticket with VMware referencing PR #1178834 to log the issue.Īdditionally, this issue can also be fixed by upgrading the Intel processors on the Hyper-V or VMware hosts. VMware hosts must have this BIOS update installed to fix the issue. Resolutionįor 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.įor VMware hosts, contact your original equipment manufacturer to obtain the updated firmware that contains the fixed Intel microcode. Virtual machines that are running on Virtualization hosts, either Hyper-V or VMware may experience operating system crashes to include stop errors. This issue occurs because Ivy Bridge, Ivy Town, and Haswell processors require a firmware upgrade that contains a CPU microcode update. This update must be installed only on a problematic Windows Server host that has the Hyper-V role installed and that's running on an Intel Ivy Bridge, Ivy Town, or Haswell processor.Ī virtual guest system may crash in Windows Hyper-V or VMware when the host system uses one of the Intel processors that's mentioned in the "Introduction" section. This update improves the reliability of 圆4-based versions of Windows Server that use certain Intel processors. This article describes a microcode update for Intel processors in Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 Service Pack 1 (SP1).
0 Comments
Leave a Reply. |