Windows Server 2019/2022: Out-of-Band Updates fixes Hyper-V Issue (Dec. 20, 2022)

Windows[German]The security updates rolled out by Microsoft on the December 2022 patchday lead to problems with Hyper-V in certain constellations. New VMs can no longer be created, existing VMs have problems with Ethernet connections, etc. Microsoft has now released a special update (out-of-band update) for Windows Server 2019 as well as Windows Server 2022 to fix the problem.


Advertising

The Hyper-V problem

The security updates rolled out by Microsoft on the December 2022 patchday cause problems with Hyper-V in certain constellations. New VMs can no longer be created, existing VM have problems with Ethernet connections, etc. The following updates and server versions are affected, according to Windows Server 2022 Release Health status page:

However, the error only occurred with specific configurations, the details of which I listed in the blog post Windows Server 2019/2022: December 2022 security updates cause Hyper-V issues. Microsoft had offered several workarounds to mitigate the issues.rag aufgeführt habe. Microsoft hatte verschiedene Workarounds angeboten, um die Probleme zu entschärfen.

Out-of-band update for Hyper-V bug

EP pointed out to me on the English-language blog (thanks for that) that Microsoft has deployed special updates (out-of-band updates) to fix the Hyper-V bug. On the Windows Server 2022 Release Health status page, there is a post Software Defined Networking (SDN) managed by SCVMM might have issues with new VMs in the Know Issues since December 20, 2022.

There, Microsoft informs that the Hyper-V issue has been fixed by the following out-of-band (OOB) updates. The December 20, 2022 updates are intended for installation on all Hyper-V hosts that use Software Defined Networking (SDN) and are managed by System Center Virtual Machine Manager (SCVMM).

The out-of-band updates only fix the following issues:

  • When creating a new VM or a new network adapter on an existing VM, the error "<vmName> could not change device 'Ethernet Connection'" is displayed.
  • The Load Balancer service (Software Defined Networking) might fail and the message "<SLBVMName> could not change device 'Ethernet Connection'" is displayed.
  • The SDN RAS Gateway service may fail and the message "<GatewayVMName> could not change the device 'Ethernet connection'" is displayed.

Both updates are not available via Windows Update, but must be downloaded from the Microsoft Update Catalog and installed manually. When using WSUS, the downloaded update must be imported. For those who have not installed the December 13, 2022 security updates because of the Hyper-V bug, you can install the out-of-band updates above. This is because they are cumulative and include the patches from the December 13, 2022 security update.


Advertising

It should be noted, however, that Microsoft also states this time in the Known Issues of the updates that the special updates create problems with ODBC connections. After installing this update, applications that use ODBC connections through the Microsoft ODBC SQL Server driver (sqlsrv32.dll) to access databases may fail to connect. In addition, applications may generate an error when accessing SQL Server. Details can be found in the respective update description (e.g. KB5022553).

Similar articles
Patchday: Windows 10-Updates (December 13, 2022)
Patchday: Windows 11/Server 2022-Updates (December 13, 2022)
Windows Server 2019/2022: December 2022 security updates cause Hyper-V issues


Cookies helps to fund this blog: Cookie settings
Advertising


This entry was posted in issue, Update, Virtualization, Windows and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *