Today, Microsoft is releasing this month’s preview updates for 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 production users will have the option to choose to test this in a week or two, and then it’ll be part of next month’s mandatory Patch Tuesday update.
As usual, there are a ton of fixes. This one has an interesting problem though, which is that it fixes an issue that would cause Windows 10 or Windows 11 to take 40 minutes to boot. Microsoft did not elaborate on this bug or what caused it.
Here is the full list of fixes for Windows 11 update
- New! We’ve added improvements for servicing the Secure Boot component of Windows.
- We fixed an issue that prevented the AppX Deployment Service (AppXSvc) from working after installing some MSIX apps.
- We fixed a race condition that occurs early in the boot process that can cause a stop error.
- We’ve enhanced the Autopilot client to address updated Trusted Platform Module (TPM) features that support self-deployment and pre-provisioning scenarios.
- We changed the Azure Active Directory (Azure AD) registration timeout from 60 minutes to 90 minutes for hybrid Azure AD joined Autopilot scenarios. This also resolves a race condition that causes an exception when the timeout occurs.
- We fixed an issue that caused the operating system to start up approximately 40 minutes late.
- We fixed a memory leak issue that affected Windows systems used 24 hours a day, every day of the week.
- We fixed an issue that affected Dynamic Host Configuration Protocol (DHCP) option 119 (domain search list) by preventing the connection-specific DNS suffix search list from being used.
- We fixed an issue that affected the Title attribute in Microsoft Edge IE mode.
- We fixed an issue where 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 could cause video subtitles to be partially cut off.
- We fixed an issue with incorrect alignment of video subtitles.
- We fixed an issue that caused Kerberos authentication to fail and the error was “0xc0030009 (RPC_NT_NULL_REF_POINTER)”. This occurs when a client computer attempts to use Remote Desktop Protocol (RDP) to connect to another computer while Remote Credential Guard is enabled.
- We fixed an issue that caused Windows to go into BitLocker recovery after a maintenance update.
- We fixed an issue that prevented the Endorsement Key (EK) certificate from being retrieved from the TPM device.
- We fixed an issue that could fail when copying the security portion of a Group Policy to a machine.
- We fixed an issue that prevented the Microsoft RDP client control, version 11 and later, from being instantiated in a Microsoft Foundation Class (MFC) dialog.
- We’ve displayed the temperature above the weather icon on the taskbar.
- We fixed an issue that prevented you from using the minimize, maximize, and close buttons on a maximized app window. This issue occurs because the Notification Center maintains input focus.
- We fixed an issue that could occur when using Netdom.exe or the Active Directory Domains and Trusts snap-in to list 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).
- We fixed an issue that caused 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 parse outbound approvals only.
- We fixed an issue that occurs when you map a network drive to a Server Message Block version 1 (SMBv1) share. After restarting the operating system, you cannot access this network drive.
- We fixed an issue that affected a multi-channel SMB connection and could throw a 13A or C2 error.
- We fixed an issue that corrupted a pool when a client-side caching (CSC) cleanup method failed to remove a resource that had been created.
- We fixed an issue that could cause the server to hang because the non-paged pool grows and uses all memory. After a restart, the same problem recurs when you try to repair the damage.
- We’ve reduced resource contention overhead in high input/output operations per second (IOPS) scenarios that have many threads competing on a single file.
As you can see, that’s the whole list. At this time, you will only see this update if you are on the Windows Insider Program Release Preview channel. It will expand to more users in the coming weeks, as it always does.
If you’re still using Windows 10, but not due to system requirements, you still won’t be able to get Windows 10 build 19044.1679. In fact, unless you’re limited by system requirements, the Release Preview channel will take you straight to Windows 11. You will be offered the preview update as far as production is concerned, as you will be offered if you are on an older, supported version of the operating system.
Source: Microsoft (1) (2)