2012R2 Hyper-V Hotfixes Info
The bulk of my work these days involves engineering and architecture around the 2012R2 Hyper-V platform. We support hundreds of Hypervisors so I have seen my fair share of Hyper-V issues. I’ve worked with Microsoft through many Hyper-V Sev-A / Sev-B cases, and even had Microsoft on site to troubleshoot several complex issues. Through all that I have compiled a list of 26 2012R2 Hyper-V hotfixes that I am presently proactively applying to all new Hyps and retroactively applying to existing ones. If you’re like me then throughout your Windows career you’ve only applied hotfixes when a problem presented itself that a hotfix specifically addressed. For me, this is the exception. I’ve seen this set of hotfixes solve a myriad of Hyper-V issues and prevent those issues from occurring on newly deployed Hyps.
Below you will find:
- Links to Microsoft articles which outline all available 2012R2 Hyper-V hotfixes
- My recommended list of mandatory 2012R2 Hyper-V hotfixes with links to each hotfix
- I have pre-packaged my custom hotfix set into a .zip for your download convenience – you may alternatively visit the links below and download each hotfix individually
- Powershell script to test for and automatically install the set of 2012R2 Hyper-V hotfixes
As with all things patching and hotfix related you are hereby cautioned to research each hotfix, it’s prerequisites, purpose, and potential impact on your environment. Test this in your lab before rolling to production, then test some more. It’s a good idea to be at the latest windows patch level on the Hyp prior to installing the hotfixes. In my experience I have utilized the script below to apply the complete set to hundreds of Hyps with zero issues. If a hotfix doesn’t apply (many won’t – for example – standalone [non-clustered] Hyps) the script simply carries on to the next hotfix. Only those that are applicable to your Hyp will be applied. Test! I hope these improve your environment as much as they have mine.
2012R2 Hyper-V Hotfix Links
All relevant links for Hyper-V hotfixes are listed below in order of importance. You can find title, purpose, and download links referenced in these articles. If you support a Hyper-V environment I recommend you become very familiar with these articles and check back from time to time as they are updated.
- Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
- Recommended hotfixes, updates, and known solutions for Windows Server 2012 R2 Hyper-V environments
- Hyper-V: Update List for Windows Server 2012 R2
My recommended 26 2012R2 Hyper-V Hotfixes
KB3093899= VMs that run on CSVs fail if DCM can't query volumes in Windows Server 2012 R2 KB3091057 = Cluster validation fails in the Validate Simultaneous Failover test in a Windows Server 2012 R2-based failover cluster KB3076953 = Cluster services go offline when there's a connectivity issue in Windows Server 2012 R2 or Windows Server 2012 KB3068445 = Virtual machines that host on Windows Server 2012 R2 may crash or restart unexpectedly KB3068444 = An unrecoverable failure occurred inside the filter manager error on a failover cluster node that hosts shared VHDx files KB3090343 = Cluster service stops during the VSS backup in a Windows Server 2012 R2-based Hyper-V cluster KB3060678 = Snapshots are not deleted after you perform a backup operation by using VSS in Windows Server KB3063283 = Update to improve the backup of Hyper-V Integrated components in Hyper-V Server 2012 R2 KB3130944 = March 2016 update for Windows Server 2012 R2 clusters to fix several issues KB3139896 = Hyper-V guest may freeze when it is running failover cluster service together with shared VHDX in Windows Server 2012 R2 KB3130939 = Nonpaged pool memory leak occurs in a Windows Server 2012 R2-based failover cluster KB3141074 = 0x00000001 Stop error when a shared VHDX file is accessed in Windows Server 2012 R2-based Hyper-V guest KB3072380 = Hyper-V cluster unnecessarily recovers the virtual machine resources in Windows Server 2012 R2 KB3031598 = Hyper-V host crashes and has errors when you perform a VM live migration in Windows 8.1 and Windows Server 2012 R2 KB3095308 = VMs may not get additional memory although they're set to use Dynamic Memory in Windows Server 2012 R2 KB3027108 = 0x0000003B or 0x0000007E Stop error on a Windows-based computer that has 4K sector disks KB3037313 = Old files are not removed after a migration of virtual machine storage in Windows 8.1 or Windows Server 2012 R2 KB3025091 = Shared Hyper-V virtual disk is inaccessible when it's located in Storage Spaces on a Windows Server 2012 R2-based computer KB3018489 = No host bus adapter is present error when querying SAS cable issues in Windows Server 2012 R2 or Windows Server 2012 KB3046826 = You cannot upgrade Hyper-V integration components or back up Windows virtual machines KB3020717 = VMMS crashes when you perform live migration and request VM information at the same time in Windows Server 2012 R2 KB3044457 = STATUS_PURGE_FAILED error when you perform VM replications by using SCVMM in Windows Server 2012 R2 KB3036173 = 0x00000050 Stop error when Hyper-V host crashes in Windows Server 2012 R2 KB3049443 = Live migration of virtual machine to another host fails on a Windows Server 2012 R2-based Hyper-V host server KB3102354 = Hyper-V generation 2 virtual machines can't start with some pass-through disks in Windows Server 2012 R2 KB3137691 = LBFO Dynamic Teaming mode may drop packets in Windows Server 2012 R2
2012R2 Hyper-V Hotfixes .zip download
The linked zip file below contains the 26 hotifxes identified above. If you utilize this zip then the script below will be able to automatically apply all required hotfixes to your Hyper-V server.
Powershell Test-Hotfixes / Install-Hotfixes
In the GitHub link below you will find hotfixes.ps1 which will test to see if the 26 hotfixes are applied on your Hyper-V server. Keep in mind that not all hotfixes are applicable to all configurations, and that some of the hotfixes are available via Windows Updates. Install-Hotfixes will attempt to install each hotfix on your Hyper-V server. Any hotfix that is not applicable is ignored and the script will move on to the next hotfix.
It is unlikely that all 26 will be required on your server so if Test-Hotfixes still shows a few missing after you attempt install, this is perfectly fine.