Cumulative update available, KB5012643 for Windows 11

Cumulative update available, KB5012643 for Windows 11

As you know, Microsoft releases a first monthly Windows patch in the first week of the month. It is usually the first Tuesday of each month. But it also offers an optional update at the end of the month which will end up being, if there are no setbacks, the cumulative update for the following month. This time we have to talk about patch KB5012643 which brings Windows 11 to version 22000.652. Let’s see what’s new with this patch.

What’s New in Windows 11 KB5012643 Update

  • New! Improvements have been made to the maintenance of the Windows Secure Boot component.
  • The timeout for Azure Active Directory (Azure AD) registration has been increased from 60 to 90 minutes for hybrid scenarios added to Azure AD Autopilot. This also resolves a race condition that was causing a timeout exception.
  • Fixed an issue that caused a remote desktop session to close or a reconnect to hang while waiting for the accessibility hook handler ( sethc.exe ).
  • They fixed an issue that caused the operating system to start up late by about 40 minutes.
  • Fixed an issue that incorrectly returned registry execution policy settings.
  • Fixed an issue that caused Internet Explorer to crash when copying and pasting text using an Input Method Editor (IME).
  • Fixed an issue that displayed a black screen for some users when logging in or out.
  • Fixed an issue that caused Kerberos authentication to fail with error “0xc0030009 (RPC_NT_NULL_REF_POINTER)”. This happens when a client machine tries to use RDP (Remote Desktop Protocol) to connect to another machine while Remote Credential Guard is enabled.
  • Fixed an issue that prevented changing an expired password when accessing a Windows device.
  • Fixed an issue that could cause Windows to stop working when applying a Windows Defender Application Control (WDAC) policy that did not require a restart.
  • Fixed an issue where the security portion of a Group Policy might not be copied to a machine.
  • Mitigated an issue where the Key Distribution Center (KDC) code incorrectly returned the “KDC_ERR_TGT_REVOKED” error message when shutting down the domain controller.
  • Fixed an issue that could prevent GPU load balancing from working correctly in Remote Desktop.
  • Fixed an issue that prevented Microsoft RDP version 11 and later client control from being instantiated in a Microsoft Foundation Class (MFC) dialog.
  • We fixed an issue that could cause a Microsoft OneDrive file to lose active status after renaming it and pressing Enter.
  • Fixed an issue that caused the News & Interests panel to appear when not clicked, tapped, or hovered over.
  • Fixed an issue that prevented the Shift KeyUp event from being broadcast to an application when using the Korean IME.
  • Fixed an issue that could occur when using Netdom.exe or the Active Directory snap-in to enumerate or change name suffix routing. These procedures may fail. The error message is “There are not enough system resources to complete the requested service”. This issue occurs after installing the January 2022 security update on the Primary Domain Controller Emulator (PDCe).
  • Fixed an issue where the EMI mode indicator was incorrect when character dampening policy was enabled.
  • Mitigated an issue where the primary domain controller (PDC) of the root domain generated warning and error events in the log. This issue occurs when CDP incorrectly attempts to scan only outbound approvals.
  • Fixed an issue affecting a multi-channel Server Message Block (SMB) connection that could result in a 13A or C2 error.
  • Addresses an issue that occurs when mapping a network drive to a Server Message Block version 1 (SMBv1) share. After restarting the operating system, the network drive is not accessible.
  • Fixed an issue that caused Virtual Machine Object (VCO) password configuration to fail on a Distributed Network Name resource.
  • Fixed an issue that corrupted a pool when a client-side cache (CSC) cleanup method failed to delete a created resource.
  • Fixed an issue that could cause the server to crash as the non-paging pool grew and consumed all memory. After a restart, the same problem repeated itself when trying to repair the fault.
  • Reduced resource contention overhead in high input/output (IOPS) scenarios that have many threads competing on a single file.

Leave a Comment

Your email address will not be published.