Release of out-of-band update KB5010795 for Windows 11, 10 and Windows Server

Contents hide

2 Windows 10 versions 20H2, 21H1, and 21H2 — KB5010793

3 Windows Server 2022 — KB5010796

Microsoft released out-of-band updates for Windows 11, Windows Server 2022, Windows 10, and other client and server versions of Windows on January 17, 2022.

Microsoft acknowledged that the January 2022 security updates were causing problems, especially on Windows Server systems.

Tip: Check out our overview of known issues for Windows 11, which we update regularly.

Out-of-band updates address various issues in the client and server versions of Microsoft’s Windows operating system.

Windows 11 — KB5010795

KB5010795 for Windows 11 is now available through Windows Update, as a direct download, and WSUS (by importing it). The update includes the latest servicing stack update.

The update fixes the following two issues:

Addresses an issue that could cause IPSEC (IP Security) connections containing vendor IDs to fail.
Addresses an issue that could cause removable media using Resilient File System (ReFS) to fail to mount or to mount in the RAW file format.

Read This Now: Light, light and fast Launcher for slow Android cell phone? Better option!

There is still a known issue that some ‘image editing software’ may not reproduce colors correctly on certain high dynamic range (HDR) displays.

Windows 10 versions 20H2, 21H1, and 21H2 — KB5010793

KB5010793 for Windows 10 is now available through Windows Update, the Microsoft Update Catalog, and as an import through WSUS.

The update addresses four issues in total:

Addresses an issue that could cause IPSEC (IP Security) connections containing vendor IDs to fail.
Addresses an issue that could cause removable media using Resilient File System (ReFS) to fail to mount or to mount in the RAW file format.
Addresses an issue that could cause Windows servers to restart unexpectedly on domain controllers.
Addresses an issue that prevented “Active Directory (AD) attributes from being written correctly during a Lightweight Directory Access Protocol (LDAP) modify operation” when multiple attribute changes were made.

Microsoft lists three known issues, all of which are longstanding:

The new Microsoft Edge may not install on devices that use custom ISO images or custom offline media to install new versions of Windows 10.
Some devices may not be able to install updates after installing KB5003690 from June 2021. Windows may display the error “PSFX_E_MATCHING_BINARY_MISSING”.
When connecting devices in an untrusted domain using Remote Desktop, connections might not be authenticated using smart card authentication. Should be resolved according to Microsoft via known issue rollback.

Read This Now: Why can't I upload stories on Instagram? - Images or Videos - Solution

Windows Server 2022 — KB5010796

KB5010796 for Windows Server 2022 is available through Windows Update, as a direct download from the Microsoft Update Catalog, and as an import through WSUS. The update requires the installation of KB5005039, released in August 2021.

The update fixes four issues, two of which are also fixed in the Windows 11 update described above, and all four of which are also fixed in the Windows 10 update.

Addresses an issue that could cause IPSEC (IP Security) connections containing vendor IDs to fail.
Addresses an issue that could cause removable media using Resilient File System (ReFS) to fail to mount or to mount in the RAW file format.
Addresses an issue that could cause Windows servers to restart unexpectedly on domain controllers.
Addresses an issue that prevented “Active Directory (AD) attributes from being written correctly during a Lightweight Directory Access Protocol (LDAP) modify operation” when multiple attribute changes were made.

Read This Now: How to remove the Xbox app from Windows | Tips and Tricks

Microsoft lists a known issue: When connecting devices in an untrusted domain using Remote Desktop, connections may not be authenticated using smart card authentication. Should be resolved according to Microsoft via known issue rollback.