S
Sumit (Volunteer Moderator)
This is a summary of the cumulative updates released on March 9th 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. To view other notes and messages, see the Windows 10, version 2004 update history home page.
Important: Support for Legacy Edge ends today. See this post for more details.
Windows 10 release dashboard
Windows release health
Windows 10 update history
Windows 10 update history
Windows 10 Lifecycle FAQ
Lifecycle FAQ - Windows - Microsoft Lifecycle | Microsoft Docs
Windows 10 message center
Windows message center
Known issues with KB5000802 and KB5000808
Follow @WindowsUpdate to find out when new content is published to the release information dashboard.
----------------------------------------------
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.)
Continue reading...
Windows 10 version 2004 and version 20H2 - KB5000802, Build 19041.867 and 19042.867
Windows 10 versions 1909 - KB5000808, Build 18363.1440
For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. To view other notes and messages, see the Windows 10, version 2004 update history home page.
Important: Support for Legacy Edge ends today. See this post for more details.
Windows 10 release dashboard
Windows release health
Windows 10 update history
Windows 10 update history
Windows 10 Lifecycle FAQ
Lifecycle FAQ - Windows - Microsoft Lifecycle | Microsoft Docs
Windows 10 message center
Windows message center
Known issues with KB5000802 and KB5000808
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. |
(KB5000802 only) When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note The affected apps are using the ImmGetCompositionString() function. | We are working on a resolution and will provide an update in an upcoming release. |
Follow @WindowsUpdate to find out when new content is published to the release information dashboard.
----------------------------------------------
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.)
Continue reading...