Today, Microsoft is releasing this month’s preview updates to Windows Insiders. Those in the Release Preview channel will get Windows 11 build 220000.651 or Windows 10 build 19044.1679, depending on what your device supports. With a preview of the update, this means that production users will have the opportunity to choose to test this in a week or two, after which it will be part of the mandatory Patch Tuesday next month.
As usual, there are a lot of fixes. This program has an interesting issue though, and that is that it fixes an issue that could cause Windows 10 or Windows 11 to take 40 minutes to start up. Microsoft has not provided details about this error or what caused it.
Here is the complete list of fixes for Windows 11 Update
- new! We added improvements to the Windows Secure Boot Component service.
- We have fixed an issue causing the AppX Deployment Service (AppXSvc) to stop working after installing some MSIX applications.
- We have fixed a race condition that occurs early in the startup process that could be causing the stop error.
- We optimized the Autopilot client to address updated TPM capabilities that support self-deployment and pre-provisioning scenarios.
- We’ve changed the Azure Active Directory (Azure AD) logging timeout from 60 minutes to 90 minutes for hybrid autopilot scenarios associated with Azure AD. This also handles a race condition that causes an exception when it times out.
- We fixed an issue that delayed OS startup by about 40 minutes.
- We’ve fixed a memory leak affecting Windows systems that are used 24 hours a day, 7 days a week.
- We have fixed an issue affecting the Dynamic Host Configuration Protocol (DHCP) 119 (Domain Lookup List) option by preventing the use of the search list in the connection’s DNS suffix.
- We have fixed an issue affecting the title attribute in Microsoft Edge IE mode.
- We fixed an issue where Mobile Device Management (MDM) policies were not allowed on Enterprise editions of Windows upgraded to Enterprise using subscription entitlement associated with Azure AD.
- We’ve fixed an issue that could cause video subtitles to partially break.
- We fixed an issue where video subtitles were incorrectly aligned.
- We have fixed an issue causing Kerberos authentication to fail, the error is “0xc0030009 (RPC_NT_NULL_REF_POINTER)”. This occurs when the client machine tries to use Remote Desktop Protocol (RDP) to connect to another machine while Remote Credential Guard is enabled.
- We fixed an issue causing Windows to enter BitLocker recovery after a service update.
- We fixed an issue that prevented the Authentication Key (EK) certificate from being retrieved from a TPM.
- We have fixed an issue where copying the security portion of Group Policy to a device might fail.
- We’ve fixed an issue preventing Microsoft RDP Client Control, version 11 and later, from being instantiated inside a Microsoft Foundation Class (MFC) dialog.
- We 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 in an enlarged application window. This issue occurs because Notification Center maintains input focus.
- We have fixed an issue that may occur when using netdom.exe or the Active Directory Domains and Trusts snap-in to list or modify directive name suffixes. These actions may fail. The error message is, “Insufficient 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).
- We have fixed an issue that causes the root domain PDC to generate warning events and errors in the system log. This problem occurs when the PDC incorrectly tries to examine only outbound trust relationships.
- We have fixed an issue when mapping a network drive to a Server Message Block Version 1 (SMBv1) share. After restarting the operating system, you cannot access this network drive.
- We’ve fixed an issue affecting a multichannel SMB connection and could result in a 13A or C2 error.
- We fixed an issue that damages a collector when the client-side cache cleanup (CSC) method fails to delete a generated resource.
- We fixed an issue that could cause the server to shutdown because the non-paged pool is growing and consuming all memory. After the restart, the same problem occurs again when trying to fix the corruption.
- We have reduced the burden of resource contention in high IOPS scenarios that have many competing threads in a single file.
As you can see, it’s quite the list. For now, you will only see this update if you are using the Windows Insider Program Release Preview channel. And it will expand to more users in the coming weeks, as always.
If you are still using 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’re limited by system requirements, the Release Preview channel will take you straight to Windows 11. You’ll be offered a preview update when it comes to production, as if you’re using an earlier, supported version of the operating system.
Source: Microsoft (1) (2)[2)