Today, Microsoft announced that they have started to roll out a preview of the Windows 10 21H1 feature update to Windows Insiders in the Beta channel.
Microsoft also confirmed that the Windows 10 21H1 feature update would be delivered as an enablement package, allow Windows 10 2004 and 20H2 users to install the feature update very quickly.
However, users on earlier versions of Windows will need to install the full update and take much longer to install.
“Customers running either Windows 10, version 2004 or version 20H2 who choose to update to the new release will have a fast installation experience because the update will install like a monthly update.” Microsoft’s John Cable announced today.
“For consumer or commercial users coming from versions of Windows 10 earlier than the May 2020 Update (version 2004), the process of updating to the new release will be the same as it has been and will work in a similar manner to previous Windows 10 feature updates, using the same tools and processes,”
Microsoft further states as Windows 10 21H1 release is targeted for the first half of 2021, all versions will receive 18 months of servicing.
Some of the new features announced in Windows 10 21H1 include Windows Hello multicamera support, Windows Defender Application Guard improvements, and Windows Management Instrumentation (WMI) Group Policy Service (GPSVC) performance improvements.
A preview release of Windows 10 21H1 is available now to Windows Insiders in the Beta channel.
If you are on the Windows Insider ‘Release’ channel, you can install Windows 10 21H1 by switching to the ‘Beta’ channel and performing a ‘Check for Update’ in Windows Update.
This update includes the following improvements:
- We fixed an issue with a memory leak in Internet Explorer 11 that occurs when you use the Chinese language pack.
- We fixed an issue with certain COM+ callout policies that cause a deadlock in certain applications.
- We fixed an issue that prevents certain Win32 apps from opening as a different user when you use the runas
- We fixed an issue that displays unexpected screens during the Windows Out of Box Experience (OOBE).
- We fixed an issue that might cause a deadlock when a COM server delivers an event to multiple subscribers in parallel.
- We fixed an issue in Advanced display settings that shows the incorrect refresh rates available for high dynamic range (HDR) displays.
- We fixed an issue that might prevent certain CAD applications from opening if those applications rely on OpenGL.
- We fixed an issue that might cause video playback to flicker when rendering on certain low-latency capable monitors.
- We fixed an issue that sometimes prevents the input of strings into the Input Method Editor (IME).
- We fixed an issue that exhausts resources because Desktop Windows Manager (DWM) leaks handles and virtual memory in Remote Desktop sessions.
- We fixed an issue with a stop error that occurs at start up.
- We fixed an issue that might delay a Windows Hello for Business (WHfB) Certificate Trust deployment when you open the Settings-> Accounts-> Sign-in Options page.
- We fixed an issue that might sometimes prevent some keyboard keys from working, such as the home, Ctrl, or left arrow keys. This issue occurs when you set the Japanese IME input mode to Kana.
- We removed the history of previously used pictures from a user account profile.
- We fixed an issue that displays the wrong language on a console after you change the system locale.
- We fixed an issue that causes the host process of Windows Remote Management (WinRM) to stop working when it formats messages from a PowerShell plugin.
- We fixed an issue in the Windows Management Instrumentation (WMI) service that causes a heap leak each time security settings are applied to WMI namespace permissions.
- We fixed an issue with screen rendering after opening games with certain hardware configurations.
- We improved startup times for applications that have roaming settings when User Experience Virtualization (UE-V) is turned on.
- We fixed an issue in which a principal in a trusted MIT realm fails to obtain a Kerberos service ticket from Active Directory domain controllers (DC). This occurs on devices that installed Windows Updates that contain CVE-2020-17049 protections and configured PerfromTicketSignature to 1 or higher. These updates were released between November 10, 2020 and December 8, 2020. Ticket acquisition also fails with the error, “KRB_GENERIC_ERROR”, if callers submit a PAC-less Ticket Granting Ticket (TGT) as an evidence ticket without providing the USER_NO_AUTH_DATA_REQUIRED flag.
- We fixed high memory and CPU utilization in Microsoft Defender for Endpoint.
- We enhanced data loss prevention and insider risk management solution functionalities in Microsoft 365 endpoints.
- We fixed an issue that displays an error when you attempt to open an untrusted webpage using Microsoft Edge or open an untrusted Microsoft Office document. The error is, “WDAG Report – Container: Error: 0x80070003, Ext error: 0x00000001”. This issue occurs after installing the .NET update KB4565627.
- We fixed an issue that prevents wevtutil from parsing an XML file.
- We fixed an issue that fails to report an error when the Elliptic Curve Digital Signature Algorithm (ECDSA) generates invalid keys of 163 bytes instead of 165 bytes.
- We added support for using the new Chromium-based Microsoft Edge as the assigned access single kiosk app. Now, you can also customize a breakout key sequence for single app kiosks. For more information, see Configure Microsoft Edge kiosk mode.
- We fixed an issue with User Datagram Protocol (UDP) broadcast packets that are larger than the maximum transmission unit (MTU). Devices that receive these packets discard them because the checksum is not valid.
- We fixed an issue in which the WinHTTP AutoProxy service does not comply with the value set for the maximum Time To Live (TTL) on the Proxy Auto-Configuration (PAC) file. This prevents the cached file from updating dynamically.
- We improved the ability of the WinHTTP Web Proxy Auto-Discovery Service to ignore invalid Web Proxy Auto-Discovery Protocol (WPAD) URLs that the Dynamic Host Configuration Protocol (DHCP) server returns.
- We displayed the proper Envelope media type as a selectable output paper type for Universal Print queues.
- We ended the display of a random paper size for a printer when it uses the Microsoft Internet Printing Protocol (IPP) Class Driver.
- We enabled Windows to retrieve updated printer capabilities to ensure that users have the proper set of selectable print options.
- We updated support for hole punch and stapling locations for print jobs with long edge first paper feed direction on certain printers.
- We fixed an issue that might cause the IKEEXT service to stop working intermittently.
- We fixed an issue that might prevent a Non-Volatile Memory Express (NVMe) device from entering the proper power state.
- We fixed an issue that might cause stop error 7E in sys on servers running the Network File System (NFS) service.
- We fixed an issue that prevents the User Profile Service from detecting a slow or a fast link reliably.
- We fixed an issue that causes contention for a metadata lock when using Work Folders.
- We added a new dfslogkey as described below:
- Keypath: HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/dfslog.
- The RootShareAcquireSuccessEvent field has the following possible values:
- Default value = 1; enables the log.
- Value other than 1; disables the log.
If this key does not exist, it will be created automatically. To take effect, any change to dfslog/RootShareAcquireSuccessEvent in the registry requires that you restart the DFSN service.
- We updated the Open Mobile Alliance (OMA) Device Management (DM) sync protocol by adding a check-in reason for requests from the client to the server. The check-in reason will allow the mobile device management (MDM) service to make better decisions about sync sessions. With this change, the OMA-DM service must negotiate a protocol version of 4.0 with the Windows OMA-DM client.
- We turned off token binding by default in Windows Internet (WinINet).
- We fixed an issue that might prevent the correct Furigana characters from appearing in apps that automatically allow the input of Furigana characters. You might need to enter the Furigana characters manually. This issue occurs when using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in these apps.