Microsoft Windows Server | WI484709

Impact: SCVMM might have issues creating new VMs or creating new NICs for existing VMs. Originating KB URL: https://support.microsoft.com/en-us/topic/5021237 Originating KB Release Date: 2022-12-13T10:00:00-08:00 Originating Build: 17763.30000 Resolved KB URL: https://support.microsoft.com/en-us/topic/5022554 Date Resolved: 2022-12-20T14:00:00-08:00 Vendor Message History: ======================= Published: 2022-12-21T22:41:45.513+00:00 ---------------------------------------- After installing KB5021237 (https://support.microsoft.com/help/5021237) on Hyper-V hosts managed by Software Defined Networking (SDN) configured System Center Virtual Machine Manager (VMM) (https://learn.microsoft.com/system-center/vmm/overview), you might receive an error on workflows involving creating a new Network Adapter (also called a Network Interface Card or NIC) joined to a VM network or a new Virtual Machine (VM) with a Network Adapter joined to a VM network. Existing VMs with existing Network Adapters should not have issues connecting after installing KB5021237 (https://support.microsoft.com/help/5021237), only new Network Adapters created after installation of KB5021237 (https://support.microsoft.com/help/5021237) are affected. When experiencing this issue, you might receive one of the following errors: 1. When creating a new VM or a new network adapter on an existing VM, you might receive, "<vmName> failed to modify device 'Ethernet Connection" 2. Software defined networking (SDN) software load balancer (https://learn.microsoft.com/system-center/vmm/sdn-slb) service might fail, and you might receive, "<SLBVMName> failed to modify device 'Ethernet Connection' error" 3. SDN RAS Gateway (https://learn.microsoft.com/system-center/vmm/sdn-gateway) service might fail, and you might receive, "<GatewayVMName> failed to modify device 'Ethernet Connection' error" Workaround: To mitigate this issue, open an elevated PowerShell window (select the Start button then type powershell, right click or long press on it and select "Run as Administrator") on all SCVMM managed Hyper-V hosts and run the following commands: $lang = (Get-WinSystemLocale).Name C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\$lang\VfpExt.mfl C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\VfpExt.mof A script with this workaround for large scale deployments and a post-install script that can be integrated with patching tools are available in this KB article (https://support.microsoft.com/topic/win12b-issue-in-system-center-virtual-machine-manager-3aeadda7-1c37-4005-b5cc-a18fba0017e1). Resolution: This issue was resolved in out-of-band (OOB) updates released December 20, 2022 for installation on all Hyper-V hosts in your environment which are using Software Defined Networking (SDN) and managed by System Center Virtual Machine Manager (SCVMM). You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue. To get the standalone package for these out-of-band (OOB) updates, search for the KB number in the Microsoft Update Catalog (https://www.catalog.update.microsoft.com/). You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site (https://docs.microsoft.com/windows-server/administration/windows-server-update-services/manage/wsus-and-the-catalog-site#the-microsoft-update-catalog-site). For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog (https://docs.microsoft.com/mem/configmgr/sum/get-started/synchronize-software-updates#import-updates-from-the-microsoft-update-catalog). Note The below updates are not available from Windows Update and will not install automatically. Cumulative updates: - Windows Server 2022: KB5022553 (https://support.microsoft.com/help/5022553) - Windows Server 2019: KB5022554 (https://support.microsoft.com/help/5022554) Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released December 13, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above. Affected platforms: - Client: None - Server: Windows Server 2022; Windows Server 2019 Published: 2022-12-14T22:19:29.167+00:00 ---------------------------------------- After installing KB5021237 (https://support.microsoft.com/help/5021237) on Hyper-V hosts managed by Software Defined Networking (SDN) configured System Center Virtual Machine Manager (VMM) (https://learn.microsoft.com/system-center/vmm/overview), you might receive an error on workflows involving creating a new Network Adapter (also called a Network Interface Card or NIC) joined to a VM network or a new Virtual Machine (VM) with a Network Adapter joined to a VM network. Existing VMs with existing Network Adapters should not have issues connecting after installing KB5021237 (https://support.microsoft.com/help/5021237), only new Network Adapters created after installation of KB5021237 (https://support.microsoft.com/help/5021237) are affected. When experiencing this issue, you might receive one of the following errors: 1. When creating a new VM or a new network adapter on an existing VM, you might receive, "<vmName> failed to modify device 'Ethernet Connection" 2. Software defined networking (SDN) software load balancer (https://learn.microsoft.com/system-center/vmm/sdn-slb) service might fail, and you might receive, "<SLBVMName> failed to modify device 'Ethernet Connection' error" 3. SDN RAS Gateway (https://learn.microsoft.com/system-center/vmm/sdn-gateway) service might fail, and you might receive, "<GatewayVMName> failed to modify device 'Ethernet Connection' error" Workaround: To mitigate this issue, open an elevated PowerShell window (select the Start button then type powershell, right click or long press on it and select "Run as Administrator") on all SCVMM managed Hyper-V hosts and run the following commands: $lang = (Get-WinSystemLocale).Name C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\$lang\VfpExt.mfl C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\VfpExt.mof A script with this workaround for large scale deployments and a post-install script that can be integrated with patching tools are available in this KB article (https://support.microsoft.com/topic/win12b-issue-in-system-center-virtual-machine-manager-3aeadda7-1c37-4005-b5cc-a18fba0017e1). Next steps: We are working on a resolution and will provide an update in an upcoming release. Affected platforms: - Client: None - Server: Windows Server 2022; Windows Server 2019 Published: 2022-12-13T18:22:19.093+00:00 ---------------------------------------- After installing KB5021237 (https://support.microsoft.com/help/5021237) on Hyper-V hosts managed by Software Defined Networking (SDN) configured System Center Virtual Machine Manager (VMM) (https://learn.microsoft.com/system-center/vmm/overview), you might receive an error on workflows involving creating a new Network Adapter (also called a Network Interface Card or NIC) joined to a VM network or a new Virtual Machine (VM) with a Network Adapter joined to a VM network. Existing VMs with existing Network Adapters should not have issues connecting after installing KB5021237 (https://support.microsoft.com/help/5021237), only new Network Adapters created after installation of KB5021237 (https://support.microsoft.com/help/5021237) are affected. When experiencing this issue, you might receive one of the following errors: 1. When creating a new VM or a new network adapter on an existing VM, you might receive, "<vmName> failed to modify device 'Ethernet Connection" 2. Software defined networking (SDN) software load balancer (https://learn.microsoft.com/system-center/vmm/sdn-slb) service might fail, and you might receive, "<SLBVMName> failed to modify device 'Ethernet Connection' error" 3. SDN RAS Gateway (https://learn.microsoft.com/system-center/vmm/sdn-gateway) service might fail, and you might receive, "<GatewayVMName> failed to modify device 'Ethernet Connection' error" Workaround: To mitigate this issue, open an elevated PowerShell window (select the Start button then type powershell, right click or long press on it and select "Run as Administrator") on all SCVMM managed Hyper-V hosts and run the following commands: $lang = (Get-WinSystemLocale).Name C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\en-US\VfpExt.mfl C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\VfpExt.mof A script with this workaround for large scale deployments and a post-install script that can be integrated with patching tools are available in this KB article (https://support.microsoft.com/topic/win12b-issue-in-system-center-virtual-machine-manager-3aeadda7-1c37-4005-b5cc-a18fba0017e1). Next steps: We are working on a resolution and will provide an update in an upcoming release. Affected platforms: - Client: None - Server: Windows Server 2022; Windows Server 2019 Published: 2022-12-13T18:03:44.307+00:00 ---------------------------------------- After installing KB5021237 (https://support.microsoft.com/help/5021237) on Hyper-V hosts managed by Software Defined Networking (SDN) configured System Center Virtual Machine Manager (VMM) (https://learn.microsoft.com/system-center/vmm/overview), you might receive an error on workflows involving creating a new Network Adapter (also called a Network Interface Card or NIC) joined to a VM network or a new Virtual Machine (VM) with a Network Adapter joined to a VM network. Existing VMs with existing Network Adapters should not have issues connecting after installing KB5021237 (https://support.microsoft.com/help/5021237), only new Network Adapters created after installation of KB5021237 (https://support.microsoft.com/help/5021237) are affected. When experiencing this issue, you might receive one of the following errors: 1. When creating a new VM or a new network adapter on an existing VM, you might receive, "<vmName> failed to modify device 'Ethernet Connection" 2. Software defined networking (SDN) software load balancer (https://learn.microsoft.com/system-center/vmm/sdn-slb) service might fail, and you might receive, "<SLBVMName> failed to modify device 'Ethernet Connection' error" 3. SDN RAS Gateway (https://learn.microsoft.com/system-center/vmm/sdn-gateway) service might fail, and you might receive, "<GatewayVMName> failed to modify device 'Ethernet Connection' error" Workaround: To mitigate this issue, open an elevated PowerShell window (select the Start button then type powershell, right click or long press on it and select "Run as Administrator") on all SCVMM managed Hyper-V hosts and run the following commands: $lang = (Get-WinSystemLocale).Name C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\en-US\VfpExt.mfl C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\VfpExt.mof A script with this workaround for large scale deployments and a post-install script that can be integrated with patching tools are available in this blog post (https://techcommunity.microsoft.com/t5/system-center-blog/system-center-2022-update-rollup-1-is-here/ba-p/3676690). Next steps: We are working on a resolution and will provide an update in an upcoming release. Affected platforms: - Client: None - Server: Windows Server 2022; Windows Server 2019