Microsoft releases Windows 11 build 22000.651 for the Release Preview channel

Today, Microsoft releases this month’s preview updates for Windows Insiders. Those in the Release Preview channel get Windows 11 build 22000.651 or Windows 10 build 19044.1679, depending on what your machine supports. By preview update, this means that production users will have the option to test this in a week or two, and then it will be part of next month’s mandatory Patch Tuesday update.

As usual, there are a host of fixes. However, this one has an interesting one, which is that it solves a problem that would make Windows 10 or Windows 11 take 40 minutes to start. Microsoft did not elaborate on this error or what caused it.

Here is the full list of fixes for the Windows 11 update

  • New! We added enhancements to servicing the Secure Boot component in Windows.
  • We’ve fixed an issue that caused the AppX Deployment Service (AppXSvc) to stop working after you installed certain MSIX apps.
  • We fixed a running condition that occurs early in the startup process and that can cause a stop error.
  • We enhanced the Autopilot client to handle updated Trusted Platform Module (TPM) features that support self-deployment and pre-provisioning scenarios.
  • We changed the Azure Active Directory Registration (Azure AD) timeout from 60 minutes to 90 minutes for hybrid Azure AD-connected autopilot scenarios. This also addresses a running condition that causes a timeout exception.
  • We solved a problem that delays the start of the OS by about 40 minutes.
  • We have fixed an issue with memory leakage affecting Windows systems that are in use 24 hours a day, 7 days a week.
  • We resolved an issue that affects Dynamic Host Configuration Protocol (DHCP) option 119 (Domain Search List) by preventing the use of the connection-specific DNS Suffix Search List.
  • We’ve fixed an issue that affects the Title attribute in Microsoft Edge IE mode.
  • We resolved an issue where Mobile Device Management (MDM) policies were not allowed in Windows Enterprise editions that were upgraded to Enterprise using Azure AD-joined subscription rights.
  • We’ve fixed an issue that could cause video subtitles to be partially cut off.
  • We’ve fixed an issue that incorrectly adjusts video subtitles.
  • We have fixed an issue that caused Kerberos authentication to fail and the error was “0xc0030009 (RPC_NT_NULL_REF_POINTER)”. This happens when a client machine tries to use the Remote Desktop Protocol (RDP) to connect to another machine while Remote Credential Guard is enabled.
  • We resolved an issue that caused Windows to go into BitLocker recovery after a service update.
  • We have fixed an issue that prevents retrieval of the Endorsement Key (EK) certificate from the TPM device.
  • We resolved an issue that might not be able to copy the security portion of a Group Policy to a machine.
  • We have fixed an issue that prevents the installation of Microsoft RDP Client Control, version 11 and later, in a Microsoft Foundation Class (MFC) dialog box.
  • We showed the temperature on top of the weather icon on the taskbar.
  • We’ve resolved an issue that prevents you from using the buttons to minimize, maximize, and close a maximized app window. This issue occurs because the message center retains input focus.
  • We have fixed an issue that may occur when using Netdom.exe or the Active Directory Domains and Trusts snap-in to view or change names suffix routing. These procedures may fail. The error message is: “There are insufficient system resources to complete the requested service.” This issue occurs after installing the January 2022 security update on the primary domain controller emulator (PDCe).
  • We resolved an issue that caused the root domain primary controller (PDC) to generate warnings and error events in the system log. This issue occurs when the PDC erroneously attempts to scan only outgoing trust relationships.
  • We have fixed an issue that occurs when you associate a network drive with a Server Message Block version 1 (SMBv1) share. After restarting the operating system, you can not access that network drive.
  • We resolved an issue that affects an SMB multichannel connection and could generate a 13A or C2 error.
  • We’ve fixed an issue that could damage a pool when a Client-Side Caching (CSC) cleanup method could not delete a resource that was created.
  • We have fixed an issue that could cause the server to unlock because the non-sided pool grows and uses up all memory. After a restart, the same problem occurs again when you try to repair the damage.
  • We reduced the overhead of resource conflicts in high input / output operations per second (IOPS) scenarios that have many threads fighting over a single file.

As you can see, it’s quite a list. Right now, you will only see this update if you are on the Release Preview channel in the Windows Insider program. It will expand to more users in the coming weeks, as it always does.

If you’re still on Windows 10 but not due to system requirements, you will not be able to get Windows 10 build 19044.1679 yet. In fact, unless you are limited by system requirements, the Release Preview channel will take you directly to Windows 11. You will be offered the preview update when it comes to production, which you will be if you are on an earlier, supported version of U.S.

Source: Microsoft (1) (2)

Leave a Comment