Cumulative update available, KB5012643 for Windows 11

As you know, Microsoft is releasing a first monthly patch for Windows in the first week of this 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 the KB5012643 patch that brings Windows 11 to version 22000652. Let’s see what’s new with this patch.

What’s New in Windows 11 Update KB5012643

  • New! Improvements have been made to maintaining the Windows safe boot component.
  • Azure Active Directory (Azure AD) log timeout 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 reconnect while waiting for accessibility hook manager (sethc.exe).
  • They fixed an issue that caused the operating system to start late in about 40 minutes.
  • Fixed an issue that incorrectly returned the 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 showed a black screen for some users when they signed in or logged 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 you from changing an expired password when accessing a Windows device.
  • Fixed an issue that could cause Windows to stop working when a Windows Defender Application Control (WDAC) policy was applied that did not require a restart.
  • Fixed an issue where the security part of a group policy was not copied to a machine.
  • Fixed an issue where the Key Distribution Center (KDC) code incorrectly returned the “KDC_ERR_TGT_REVOKED” error message when closing the domain controller.
  • Fixed an issue that could prevent the graphics processing unit (GPU) load balancer from working properly on the remote desktop.
  • Fixed an issue that prevented Microsoft RDP version 11 and subsequent 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 its active state after renaming it and pressing Enter.
  • Fixed an issue that caused the News & Interests dashboard to appear when it was not clicked, touched, 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 the 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 you install the January 2022 security update on the primary domain controller emulator (PDCe).
  • Fixed an issue where the EMI mode indicator was incorrect when enabling character deprecation policy was enabled.
  • Fixed an issue where the root domain’s primary domain controller (PDC) was generating warning and error events in the registry. This problem occurs when CDP incorrectly tries to scan only outbound approvals.
  • Fixed an issue affecting a multichannel message block server (SMB) connection that could result in a 13A or C2 error.
  • Resolves an issue that occurs when a network drive is assigned to a version 1 server block of the message block server (SMBv1). After restarting the operating system, the network drive is not accessible.
  • Fixed an issue that caused the virtual machine object (VCO) password setting to fail on a distributed network name resource.
  • Fixed an issue that corrupted a group when a client cache cleanup (CSC) method could not delete a created resource.
  • Fixed an issue that could cause the server to crash as the unpagged pool grows and consumes all memory. After a reboot, the same problem was repeated when trying to fix the error.
  • Resource containment overhead has been reduced in IOPS, which have many threads competing in a single file.

Leave a Comment