Microsoft today released a new 20H2 Build 19042.508 (KB4571756) to Windows Insiders in the Beta Channel. This is a security update that includes the same changes that the KB4571756 (OS Build 19041.508) 20H1 patch has.
The change log for the update highlights the following:
- Addresses an issue with a possible elevation of privilege in windowmanagement.dll.
- Addresses a security vulnerability issue with user proxies and HTTP-based intranet servers. After installing this update, HTTP-based intranet servers cannot leverage a user proxy by default to detect updates. Scans using these servers will fail if the clients do not have a configured system proxy. If you must leverage a user proxy, you must configure the behavior using the Windows Update policy “Allow user proxy to be used as a fallback if detection using system proxy fails.” This change does not affect customers who secure their Windows Server Update Services (WSUS) servers with the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) protocols. For more information, see Improving security for devices receiving updates via WSUS.
- Security updates to Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Input and Composition, Windows Media, Windows Shell, Windows Cloud Infrastructure, Windows Fundamentals, Windows Management, Windows Kernel, Windows Virtualization, Windows Storage and Filesystems, the Microsoft Scripting Engine, and the Microsoft JET Database Engine.
Microsoft Windows 10 version 20H2 is the successor to the May 2020 Update version 2004 released in May 2020. Windows 10 version 20H2 is a minor update with a smaller set of enhancements focused primarily on select performance improvements, enterprise features, and quality enhancements.
Version 20H2 will be delivered to devices currently running Windows 10, version 2004 using the KB4562830 enablement package. This is the same technology Microsoft used to update devices from Windows 10, version 1903 to version 1909.
Starting in Windows 10 version 20H2, Microsoft is using different version numbering. Microsoft had switched to a format that represents the half of the calendar year in which the release becomes available in retail and commercial channels. The company had explained that for Windows 10 version 20H2 you will see “version 20H2” instead of “version 2009”, as you could expect. This numbering scheme is a familiar approach for Windows Insiders and is designed to provide consistency in Microsoft’s version names across releases for their commercial customers and partners. Microsoft will continue to use a friendly name, such as the May 2020 Update, in consumer communications.