Latest Windows 10 Update for Version 1909 2004 and 20H2 Released

Latest Windows 10 20H2 Update for Version 1909 2004 Released. Microsoft released its cumulative updates as usual on 13 April 2021. This update is applicable for all versions of windows 10 specially for Windows 10 version, 1909, Windows 10 version 2004 and Windows 10 20H2. If you are using Windows 10 Version 2004 and 20H2, you will receive KB5001330. This update supports OS builds 19041.928 and 19042.928.

If you are using Windows 10 version 1909, you will receive KB5001337 having OS build 18363.1500.

Also Read:

Windows 10 Version 1809 update March 2021 KB5000822 Released

Windows 10 Update 2021 Version 20H2 and 2004 released March 2021

Downlaod Windows 10 Version 1909 Update KB5000808 Released on March 2021

Latest Windows 10 20H2 Update for Version 1909 2004

Now we will see the Highlights, key features as well as Symptoms and Workarounds of this updates. You will also find direct download link of Latest windows 10 20H2 update KB5001330 and KB5001337.

Highlights of KB5001330 update

1. This update will improve security of your system when Windows performs basic operations.
2. Also improve security related to your input devices such as mouse, keyboard or pen.
3. This Latest Windows 10 update having quality improvements to the servicing stacks. As we all know, Servicing stacks is a component that installs windows updates. Servicing Stack Updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Latest Windows 10 updates.

Key Features of Latest Windows 10 Updates KB5001330 & KB5001337

The following are the main key features of Windows 10 update for version 1909, 2004 and 20H2: –

• Microsoft addresses an issue in which a principal in a trusted MIT realm fails to obtain a Kerberos service ticket from Active Directory domain controllers (DC). It occurs on devices that installed Windows Updates having CVE-2020-17049 protections and configured PerfromTicketSignature to 1 or higher. You can see these updates 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.
• Highlights an issue with security vulnerabilities identified by a security researcher. Due to these security vulnerabilities, all future Windows updates including this will no longer contain the RemoteFX vGPU feature. 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 addresses a potential elevation of privilege vulnerability. This is in the way Azure Active Directory web sign-in allows arbitrary browsing from the third-party endpoints used for federated authentication.
• Addresses an issue that causes Windows Back up using File History to stop working for a few users. This issue occurs after installing the February 9, 2021 update. The error message is, “Failed to start the backup of user links (error 8007005)”.
• Microsoft also addresses Security updates to Windows App Platform and Frameworks, Windows Apps, Windows Input and Composition, Windows Office Media. Also for Windows Fundamentals, Windows Cryptography, the Windows AI Platform, Windows Kernel, Windows Virtualization, and Windows Media.

Known issue of this Latest Windows 10 20H2 Update

Two known issues addressed by Microsoft through windows 10 update KB5001330. Here are their symptoms and workaround.

Symptom No 1

When updating a device from Windows 10, version 1809 or later to a later version of Windows 10, System and user certificates might be lost.

Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later. You can 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.

Workaround

• If you are facing this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows.
• 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.

Symptom No 2

• When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually.
• The affected apps are using the ImmGetCompositionString() function.

Workaround

Microsoft is working on a resolution and will provide an update in an upcoming release.

Symptom No 3

Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update. It not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later.

Workaround

To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10 20H2 and Windows 10 2004. You will need to extract the SSU from the combined package. Use the following steps to extract the using SSU:

• Extract the cab from the msu via this command line (using the package for KB5000842 as an example):
  • expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path>
• Extract the SSU from the previously extracted cab via this command line:
  • expand Windows10.0-KB5000842-x64.cab /f:* <destination path>

You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU.

DOWNLOAD WINDOWS 10 20H2 UPDATE KB5001330

That’s all.