This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This is a summary of the cumulative updates released on June 8th for all the supported consumer releases of Windows 10.
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:
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.)
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Oh, I see, take the Install.esd from a Win 11 Installation media & put it into Win 10 Installation media. Then do the install using the altered Win 10 media to end up with Win 11. It seems to be ingenious because the requirement checks are outside the .esd. But -- even if the installation process doesn't need TPM to be present during the install -- what about afterward when running Win 11? What happens when it tries to use it?
Thanks for all that information, fg2001. Yea for Backup & Restore! A Legacy install does not use Secure Boot which is another requirement for Win 11 (or maybe it's the same one). Interesting you could bypass those requirements. Does the computer also not have TPM 2.0? That's what I lack. What does TPM.msc (type into Search) say...?...
There's no mention of it in my BIOS. But I'm unsure I'd want Win 11 anyway (presuming a non-insider can clean install it) owing to the recommendation against it. But maybe I'll try it in a dual-boot to see for myself, if your reports are good. Is that how to bypass the requirements -- clean install it?
Hello PCR,
Well , I also have an older UEFI machine (Dell XPS 8700) that does not have TPM, so that does not meet the requirements either even if it is UEFI and has Secure Boot on.
As for Installing win 11 on Legacy BIOS you can find some workarounds on the web, just search "How to install Windows 11 on Legacy Bios machine".
Just doing a clean install using the Win 11 installation media will not work because it enforces the checks for the requirements.
One method that works is by replacing the install.wim or install.esd taken from windows 11 on a USB installation media of Windows 10 (21H1), then you can do the clean install from that and it will defeat the checks for the install requirements. All the files needed for windows 11 are in the install.wim in the Sources folder, everything else is just used for installing.
I'm sure MS can bypass the checks of the requirements for the windows insiders on development channels.
We'll just have to wait next week to see what MS will do.
As for fully supported machines, I have a Dell XPS 8930 Desktop and a Lenovo Yoga 920 which are both good to go for Windows 11. Still I'll keep the Backup of the current Public build so I can always go back to a stable system if anything goes wrong. Already tried and upgraded from 21H1 to win 11 with a win 11 ISO and it worked fine, then I restored my 21H1, I will be waiting for the official MS build, I don't really trust the leaked ones :-(
Thanks for all that information, fg2001. Yea for Backup & Restore! A Legacy install does not use Secure Boot which is another requirement for Win 11 (or maybe it's the same one). Interesting you could bypass those requirements. Does the computer also not have TPM 2.0? That's what I lack. What does TPM.msc (type into Search) say...?...
There's no mention of it in my BIOS. But I'm unsure I'd want Win 11 anyway (presuming a non-insider can clean install it) owing to the recommendation against it. But maybe I'll try it in a dual-boot to see for myself, if your reports are good. Is that how to bypass the requirements -- clean install it?
I'm glad I'm not alone using Windows Backup & Restore (B&R). Good to know it works for you too & for so long. IIRC, we discovered together in an old thread the computername folder could be renamed. Thanks for experiments with that. Until then, I was renaming the WindowsImageBackup folder itself which then had to be renamed back to use. MSFT did remove B&R from Win 8, but returned it in Win 8.1. I wonder whether it is in Win 11, but this computer won't ever know. It doesn't have TPM 2.0 which is a requirement. Too bad about that extra step for a clean Legacy install. I think I read Win 11 won't allow Legacy installs at all.
Hi PCR,
Already tried B&R With windows 11, still worked fine assuming they don't mess it up later.
As for Legacy Bios, is no longer officially supported by Win 11, but it still works using a workaround that bypasses the checks for the installation. I did a clean install of Win 11 on two Legacy Bios Machines and it seems to work fine.
According to this message on this current insider build 21390.1025 they still will allow to run Win 11 if you are already in the development channel at least until Win 11 goes GA, after that it will be the end of the game for old machines. 😒
Will see what happens next week when we get an official Win 11 Build from MS.
The way I read the red message below, I think it should let me go on with Win 11 on this machine even if it does not meet the requirements.
I'm glad I'm not alone using Windows Backup & Restore (B&R). Good to know it works for you too & for so long. IIRC, we discovered together in an old thread the computername folder could be renamed. Thanks for experiments with that. Until then, I was renaming the WindowsImageBackup folder itself which then had to be renamed back to use. MSFT did remove B&R from Win 8, but returned it in Win 8.1. I wonder whether it is in Win 11, but this computer won't ever know. It doesn't have TPM 2.0 which is a requirement. Too bad about that extra step for a clean Legacy install. I think I read Win 11 won't allow Legacy installs at all.
