Microsoft releases Windows 11 build 22000.651 to the Release Preview channel

Microsoft releases Windows 11 build 22000.651 to the Release Preview channel

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

As usual, there are a ton of fixes. This one has an interesting one though, which is that it fixes an issue that would cause Windows 10 or Windows 11 to take 40 minutes to startup. Microsoft didn’t elaborate on this bug or what caused it.

XDA VIDEO OF THE DAY

Here’s the full list of fixes for the Windows 11 update

  • New! We added improvements for servicing the Secure Boot component of Windows.
  • We fixed an issue that causes the AppX Deployment Service (AppXSvc) to stop working after you install certain MSIX apps.
  • We fixed a race condition that occurs early in the startup process that might cause a stop error.
  • We improved the Autopilot client to process updated Trusted Platform Module (TPM) capabilities that support self-deployment and pre-provisioning scenarios.
  • We changed the timeout for Azure Active Directory (Azure AD) registration from 60 minutes to 90 minutes for hybrid Azure AD-joined Autopilot scenarios. This also addresses a race condition that causes an exception at timeout.
  • We fixed an issue that delays OS startup by approximately 40 minutes.
  • We fixed a memory leak issue that affects Windows systems that are in use 24 hours each day of the week.
  • We fixed an issue that affects the Dynamic Host Configuration Protocol (DHCP) option 119 (Domain Search List) by preventing the use of the connection-specific DNS Suffix Search List.
  • We fixed an issue that affects the Title attribute in Microsoft Edge IE mode.
  • We fixed an issue in which mobile device management (MDM) policies were not allowed on Windows Enterprise editions that were upgraded to Enterprise using Azure AD-joined subscription entitlement.
  • We fixed an issue that might cause video subtitles to be partially cut off.
  • We fixed an issue that incorrectly aligns video subtitles.
  • We fixed an issue that causes Kerberos authentication to fail, and the error is “0xc0030009 (RPC_NT_NULL_REF_POINTER)”. This occurs when a client machine attempts to use the Remote Desktop Protocol (RDP) to connect to another machine while Remote Credential Guard is enabled.
  • We fixed an issue that causes Windows to go into BitLocker recovery after a servicing update.
  • We fixed an issue that prevents retrieval of the Endorsement Key (EK) certificate from the TPM device.
  • We fixed an issue that might fail to copy the security portion of a Group Policy to a machine.
  • We fixed an issue that prevents the instantiation of the Microsoft RDP Client Control, version 11 and higher, inside a Microsoft Foundation Class (MFC) dialog.
  • We displayed the temperature on top of the weather icon on the taskbar.
  • We fixed an issue that prevents you from using the minimize, maximize, and close buttons on a maximized app window. This issue occurs because the Notification Center keeps the input focus.
  • We fixed an issue that might occur when you use Netdom.exe or the Active Directory Domains and Trusts snap-in to list or modify name suffixes routing. These procedures might fail. The error message is, “Insufficient system resources exist to complete the requested service.” This issue occurs after installing the January 2022 security update on the primary domain controller emulator (PDCe).
  • We fixed an issue that causes the primary domain controller (PDC) of the root domain to generate warning and error events in the System log. This issue occurs when the PDC incorrectly tries to scan outgoing-only trusts.
  • We fixed an issue that occurs when you map a network drive to a Server Message Block version 1 (SMBv1) share. After restarting the OS, you cannot access that network drive.
  • We fixed an issue that affects an SMB multichannel connection and might generate a 13A or C2 error.
  • We fixed an issue that damages a pool when a Client-Side Caching (CSC) cleanup method fails to delete a resource that was created.
  • We fixed an issue that might cause the server to lock up because the nonpaged pool grows and uses up all memory. After a restart, the same issue occurs again when you try to repair the damage.
  • We reduced the overhead of resource contention in high input/output operations per second (IOPS) scenarios that have many threads contending on a single file.

As you can see, it’s quite the list. Right now, you’ll only see this update if you’re on the Release Preview channel of 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 won’t be able to get Windows 10 build 19044.1679 just yet. In fact, unless you’re restricted by system requirements, the Release Preview channel would take you right to Windows 11. You’ll be offered the preview update when it comes to production, as you will be if you’re on an earlier, supported version of the OS.

Source: Microsoft (1) (2)

About author

Rich Woods
Rich Woods

Managing Editor for XDA Computing. I've been covering tech from smartphones to PCs since 2013. If you see me at a trade show, come say hi and let me ask you weird questions about why you use the tech you use.

We are reader supported. External links may earn us a commission.