December 13, 2022—KB5021249 (OS Build 20348.1366)

**12/22/22
IMPORTANT **After November 22, 2022, there are no more optional, non-security preview releases for Windows Server 2022. Only cumulative monthly security updates (known as the “B” or Update Tuesday release) will continue for Windows Server 2022.

11/8/22
IMPORTANT Because of minimal operations during the holidays and the upcoming Western new year, there won’t be a non-security preview release for the month of December 2022. There will be a monthly security release (known as a “B” release) for December 2022. Normal monthly servicing for both B and non-security preview releases will resume in January 2023.

For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. For an overview of Windows Server 2022, see its update history page. NoteFollow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

Improvements

This security update includes improvements that were a part of update KB5020032 (released November 22, 2022). When you install this KB:

• This update addresses an issue that affects remote networks. This issue stops you from reconnecting to them using DirectAccess.
  If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.For more information about security vulnerabilities, please refer to the Security Update Guide and the December 2022 Security Updates.

Windows Server 2022 servicing stack update - 20348.1300

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

Known issues in this update

tasklist /m sqlsrv32.dll

`| This issue is addressed in KB5022291.
After installing this update on Hyper-V hosts managed by SDN configured System Center Virtual Machine Manager (VMM), 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 this update, only new Network Adapters created after installation of this update are affected.When experiencing this issue, you might receive one of the following errors:

• When creating a new VM or a new network adapter on an existing VM, you might receive, “<vmName> failed to modify device 'Ethernet Connection”
• Software defined networking (SDN) software load balancer service might fail, and you might receive, “<SLBVMName> failed to modify device ‘Ethernet Connection’ error”
• SDN RAS Gateway service might fail, and you might receive, “<GatewayVMName> failed to modify device ‘Ethernet Connection’ error”
  | This issue is addressed in KB5022553.

How to get this update

If you want to remove the LCUTo remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command:DISM /online /get-packages.Running Windows Update Standalone Installer (wusa.exe) with the**/uninstall **switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

File InformationFor a list of the files that are provided in this update, download the file information for cumulative update 5021249. For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 20348.1300.