Today, on June 2021 Patch Tuesday, Security updates started rolling out. KB5003637 LCU is among these having significant fixes and changes for Windows 10 21H1, 20H2, and 2004. This release will uplift the OS build to Windows 10 21H1 19043.1052, and other versions respectively. 19043.1052 is also available for the Release Preview and Beta Channel for those Insiders who are running 21H1.
KB5003637 basically brings fixes for vulerablities. You are able to install the patch both ways whether it is through the traditional Windows update method or manually using Microsoft update catalog.
Table of Contents
June 2021 CU KB5003637 Windows 10 201H1, 20H2, and 2004 update
Here is changelog –
Improvements and fixes
The update for Windows 10 19043.1052 brings Security updates to the Microsoft Scripting Engine, Windows App Platform and Frameworks, Windows Input and Composition, Windows Management, Windows Cloud Infrastructure, Windows Authentication, Windows Fundamentals, Windows Virtualization, Windows Kernel, Windows HTML Platform, and Windows Storage and Filesystems. For full update, navigate to the – Update guide see there.
Known issues
| Symptom | Workaround |
| An old problem running from multiple updates is System and user certificates might be missing when updating from Windows 10 v1809, or later to a later version. You will come across this issue if you’ve already installed CU rolled out on September 16, 2020 or later. Afterward, you proceed to update to a later version via media or an installation source that does not have a CU rolled out on October 13, 2020, or later integrated. This predominantly occurs when managed devices are updated via outdated bundles. Furthermore, this also happens when using media through an update management tool such as WSUS or Microsoft Endpoint Configuration Manager. This might also occur when ISO image or physical media or that do not contain the most recent updates. 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 come across this issue, you can mitigate it within the uninstall window by going back to your previous version. You can follow this article if necessary – How to change the roll back period to 60 days in Windows 10.
The tech giant is working on a resolution and will push updated bundles and refreshed media in the forthcoming weeks. |
| Entering Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters in Japanese IMEI. iN THIS SITUATION, You might need to enter the Furigana characters manually.
Important – The affected applications are using the “ImmGetCompositionString()” function. |
They are trying to resolve and you will get in a future update. |
| A lesser number of users have complained about lower performance in games after installing KB5003637. However, most of them are running games in full screen or borderless windowed modes and using two or more monitors. | This issue is fixed using Known Issue Rollback aka KIR. Kindly keep in mind that it might consume up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Rebooting might help the resolution working faster. If you are running enterprise-managed and installed the patch then it can be fixed by installing and changing a special Group Policy.
Important – Restarted after configuring the special Group Policy. For help, pursue – How to use Group Policy to deploy a Known Issue Rollback. |
| Some PCs with Windows installations created from custom offline media or custom ISO images might have the classic Edge browser eliminated by this update, but not automatically replaced by the new one. This problem only takes place when ISO images or custom offline media are developed by slipstreaming this update into the image. Additionally, the images or media first installed the standalone SSU which was rolled out on March 29, 2021, or later.
Remark – Devices that connect straight to Windows Update to get updates are not affected. This comprises devices using Windows Update for Business. Youst have SSU installed. |
To prevent this problem from occurring, slipstream the SSU March 29, 2021 or later before slipstreaming the LCU. To do this with the combined LCU and SSU you will have to separate the SSU. Use the underneath method to extract using SSU –
1. Extract the cab from the MSU using this command without quotes (For instance, KB5000842) – “expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path>” 2. Extract the Servicing Stack Update from the earlier extracted cab through running – “expand Windows10.0-KB5000842-x64.cab /f:* <destination path>” 3. You are now comprising the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into the offline image then into the Cumulative Update. Those who already found this issue can directly install the new Microsoft Edge. |
How to download KB5003637 and install
Since SSU/Servicing Stack update is wrapped up with Windows update according to the new policy so you don’t need to care for it unless you don’t encounter any issue. Follow the ways to download KB5003637 and install –
1. Via Windows update
- Press Winkey and type – “updates”.
- Click – Check for updates.
- Stay until the patch is downloaded and ask you to reboot. Click Restart now and finish the installation.
2. Through Microsoft update catalog
- Go to the KB5003637 direct download link – Microsoft update catalog.
- Find the correct file depending on the architecture of your computer (x64, x86, ARM64).
- Click download from the right to see a separate webpage.
- Next, Select the lone link there.
- Once the downloading of the June 2021 update for Windows 10 2004, 20H2, and 21H1 gets over, right-click on the .MSU file and select – Install.
You can also read on the Windows blog.
That’s all!!