Windows 10 Cumulative Updates KB5001330 & KB5001337 Released

As part of the April Patch cycle, Microsoft is rolling out a new cumulative update for all supported version of Windows, including KB5001330 for Windows 10 20H2/2004 and KB5001337 for Windows 10 1909.

The cumulative update with security fixes is rolling out to PCs with October 2020 Update, May 2020 Update and November 2019 Update. In this month’s update, there are only security enhancements for the system, browsers, core components and other basic functions.

Like every Windows Update, you can open the Settings app and click on the Windows Update option to install the patches. If you own multiple PCs or if you would like to patch the PCs manually, you can learn more about it here.

Below is the list of all new cumulative updates available today for Windows 10:

• Windows 10 version 1507 — KB5001340 (OS Build 10240.18906)
• Windows 10 version 1607 — KB5001347 (OS Build 14393.4350)
• Windows 10 version 1703 — EOS
• Windows 10 version 1709 — EOS
• Windows 10 version 1803 — KB5001339 (OS Build 17134.2145)
• Windows 10 version 1809 — KB5001342 (OS Build 17763.1879)
• Windows 10 version 1909 — KB5001337 (OS Build 18363.1500) (1903 is EOS)
• Windows 10 version 2004 and 20H2 — KB5001330 (OS Builds 19041.928 and 19042.928)

Also Read: Compliance Course Singapore: Spotlight On The 3 Offerings

What’s new in OS Builds 19041.928 and 19042.928

The cumulative update for Windows 10, version 2004 and 20H2 is known as KB5001330 and comes with numerous fixes, improvements, and security updates. 

After installing these updates, Windows 10 20H2 will be build 19042.928 and Windows 10 2004 will be build 19041.928.

Below are the highlighted fixes and improvements with this update:

• Microsoft 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.

• Microsoft fixed an issue with security vulnerabilities identified by a security researcher. Because of these security vulnerabilities, this and all future Windows updates will no longer contain the RemoteFX vGPU.For more information about the vulnerability and its removal, see CVE-2020-1036 and KB4570006. Secure vGPU alternatives are available using Discrete Device Assignment (DDA) in Windows Server LTSC releases (Windows Server 2016 and Windows Server 2019) and Windows Server SAC releases (Windows Server, version 1803 and later versions).
  
• Microsoft fixed potential elevation of privilege vulnerability in the way Azure Active Directory web sign-in allows arbitrary browsing from the third-party endpoints used for federated authentication. For more information, see CVE-2021-27092 and Policy CSP – Authentication.
• Security updates to Windows App Platform and Frameworks, Windows Apps, Windows Input and Composition, Windows Office Media, Windows Fundamentals, Windows Cryptography, the Windows AI Platform, Windows Kernel, Windows Virtualization, Internet Explorer, and Windows Media.

This release also includes March’s OOB printer updates that fix printer crashes and problems printing graphics.

It should be noted that Microsoft now combines the cumulative updates with the latest servicing stack updates, so it is not necessary to install them independently.

What’s new in OS Build 18363.1500

For those still using Windows 10 version 1909, they’ll be getting KB5001337 with the following improvements:

• Updates to improve security when Windows performs basic operations.
• Updates to improve security when using input devices such as a mouse, keyboard, or pen.

The changelog for version 1909 is the same as version 20H2/2004.

Known issues in these updates

Symptom

Workaround

System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.Note Devices using Windows Update for Business or that connect directly to Windows Update are not impacted. Any device connecting to Windows Update should always receive the latest versions of the feature update, including the latest LCU, without any extra steps.

If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options.We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks.

Legacy Microsoft Edge is going away

With this cumulative update, Microsoft Edge Legacy (based on EdgeHTML) will be permanently removed and replaced with the Chromium Microsoft Edge (based on Blink).

Also Read: Considering Enterprise Risk Management Certification Singapore? Here Are 7 Best Outcomes

After applying the April Patch Tuesday, Microsoft Edge will replace the legacy Edge and become a mandatory component of the operating system in all supported versions of Windows 10. Microsoft has also confirmed that all your group policies and registry settings to block Chromium Edge will be ignored.