Another month, another patch. Discussion is here for July ones:
Cumulative updates June 2021
This is a summary of the cumulative updates released on June 8th for all the supported consumer releases of Windows 10.
- Windows 10 version 2004, version 20H2 and version 21H1 KB5003637 -, Build 19041.1052, 19042.1052 and 19043.1052.
For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types.
Download KB5003637 from the Microsoft Update Catalog.
Windows 10 release dashboard
https://docs.microsoft.com/en-us/windows/release-health/
Windows 10 update history
Windows 10 Lifecycle FAQ
Lifecycle FAQ - Windows - Microsoft Lifecycle | Microsoft Docs
Windows 10 message center
https://docs.microsoft.com/en-us/windows/release-information/windows-message-center#407
Follow @WindowsUpdate to find out when new content is published to the release information dashboard.
12/06/2021 A new out of band update KB5004476 released for version 2004, 20H2 and 21H1. Build number incremented to 19041.1022, 19042.1022, and 19043.1022. Changelog:
This non-security update includes quality improvements. Key changes include:
- Addresses an issue that might redirect you to the Microsoft Store page for Gaming Services when you try to install or start an Xbox Game Pass game on your Windows 10 device. Additionally, you receive error 0x80073D26 or 0x8007139F. For more information, see KB5004327.
This update is available as an optional update in Windows update.
Known issues as per the release info.
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| News and interests button on the Windows taskbar might have blurry text <br>Certain display configurations might cause blurry text on the news and interests button in the Windows taskbar. | OS Build 19042.964 <br>KB5001391 <br>2021-04-28 | Confirmed | 2021-06-14 <br>17:57 PT |
| Apps might have issues accessing event logs on remote devices <br>Event logs might not be accessible from remote devices unless both devices have updates released June 8, 2021 or later. | OS Build 19042.10000 <br>KB5003637 <br>2021-06-08 | Resolved <br>KB5003637 | 2021-06-08 <br>10:00 PT |
| A high-pitched noise might be heard when using 5.1 audio with certain settings <br>Certain combinations of apps, audio devices and Windows settings might produce a high-pitched noise when using 5.1 audio | OS Build 19042.906 <br>KB5000842 <br>2021-03-29 | Mitigated | 2021-05-18 <br>10:21 PT |
| Automatic input of Furigana might not work as expected <br>In certain circumstances, the automatic Furigana input/conversion feature may not work as expected in apps. | N/A | Mitigated | 2021-05-18 <br>10:21 PT |
Join us on June 24th at 11 am ET for the #MicrosoftEvent to see what’s next for Windows.
https://www.microsoft.com/en-us/windows/event
Important: Users posting replies referring to their own websites would be considered as Spam and would be suspended from this community.
(If you have recommended this discussion and are looking for the unsubscribe button, please hit subscribe below, and a dialogue will open with the unsubscribe choice.)
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
189 answers
Sort by: Most helpful
-
Anonymous
2021-06-30T05:16:32+00:00 Well, I learned a lot from you. I'm encouraged to try it all myself when Win 11 is officially released. I have hopes it will work from what you've done. If it won't work for me, I'll wait awhile & get a new computer near 2025 when Win 10 is retired. Thanks really a lot for blazing my trail, fg2001.
-
Anonymous
2021-06-30T05:00:08+00:00 Thanks for the additional information after experimentation. Maybe the appreiserres.dll replacement will work in certain situations but not others, like maybe just to thwart the TPM requirement not the Secure Boot. Or maybe it used to work but doesn't anymore. Or maybe Mayank Parmer (the author of that article) did it on a computer that didn't need thwarting. Deleting/renaming appreiserres.dll sounds risky because when needed & called you'd think there would be a crash. But apparently the installation process just ignores its absence. Can you do it on a USB Installation drive, then do an upgrade-install with it instead of a clean install? But I guess, if it works on an .ISO, it must also work on an Installation drive.
But I'll probably go with the Registry hack when the time comes & do it during the install. Are you sure it has to be a clean-install? Won't the opportunity arise during an upgrade-install too?
You may need both hacks.
Yes, I did it with the USB installation media at build 22000.1, it is much easier to rename appreiserres.dll on the USB media than editing the ISO file.
There are other articles on the web stating that just replacing the file with an older one doesn't work and I experience that myself.
I did both, clean install and upgrade of an existing Win 10 system using the same USB media.
Clearly it works fine from the ISO file if you have all the hardware requirements, but if you have a machine without the requirements you need the hacks.
There are no ISOs available yet from MS, I just got it because I created it myself.
Also not available from uup-dump yet, at the moment it just fails to download.
-
Anonymous
2021-06-30T02:53:35+00:00 Thanks for the additional information after experimentation. Maybe the appreiserres.dll replacement will work in certain situations but not others, like maybe just to thwart the TPM requirement not the Secure Boot. Or maybe it used to work but doesn't anymore. Or maybe Mayank Parmer (the author of that article) did it on a computer that didn't need thwarting. Deleting/renaming appreiserres.dll sounds risky because when needed & called you'd think there would be a crash. But apparently the installation process just ignores its absence. Can you do it on a USB Installation drive, then do an upgrade-install with it instead of a clean install? But I guess, if it works on an .ISO, it must also work on an Installation drive.
But I'll probably go with the Registry hack when the time comes & do it during the install. Are you sure it has to be a clean-install? Won't the opportunity arise during an upgrade-install too?