This is a summary of the cumulative updates released on March 9th for all the supported consumer releases of Windows 10. 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 https://docs.microsoft.com/en-us/windows/release-health/ Windows 10 update history https://support.microsoft.com/en-us/topic/windows-10-update-history-7dd3071a-3906-fa2c-c342-f7f86728a6e3 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 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. After installing this update, you might receive an APC_INDEX_MISMATCH error with a blue screen when attempting to print to certain printers in some apps. Issue resolved with an out-of-band update. After installing updates released March 9, 2021 or March 15, 2021, you might get unexpected results when printing from some apps. Issues might include: <ul style="margin-right: 0; margin-left: 0; color: rgba(54, 54, 54, 1)"><li style="margin-left: 0">Elements of the document might print as solid black/color boxes or might be missing, including barcodes, QR codes, and graphics elements, such as logos.</li><li style="margin-left: 0">Table lines might be missing. Other alignment or formatting issues might also be present.</li><li style="margin-left: 0">Printing from some apps or to some printers might result in a blank page or label.</li></ul> Resolved - Install KB5001649 from the links below. KB5000808 Direct Download Links KB5000808 for Windows 10 1909 32-bit KB5000808 for Windows 10 1909 64 bit KB5000802 Direct Download Links KB5000802 for Windows 10 v2004 and v20H2 32-bit KB5000802 for Windows 10 v2004 and v20H2 64-bit KB5001649 Direct Download Links 19042.870 Out of Band 32-bit: http://download.windowsupdate.com/d/msdownload/update/software/updt/2021/03/windows10.0-kb5001649-x86_781a5706e11026c9fc48013e86e38a3fc83aeef7.msu 64-bit: windows10.0-kb5001649-x64_aca549448414a5ad559c742c39e9342468a23eb5.msu (windowsupdate.com) ARM: windows10.0-kb5001649-arm64_5281e77c8079d122aed8b41a88775abaae10abea.msu (windowsupdate.com) 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.)

Cumulative updates March 2021

Sumit 44,226 Volunteer Moderator

This is a summary of the cumulative updates released on March 9th for all the supported consumer releases of Windows 10.

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

https://docs.microsoft.com/en-us/windows/release-health/

Windows 10 update history

https://support.microsoft.com/en-us/topic/windows-10-update-history-7dd3071a-3906-fa2c-c342-f7f86728a6e3

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

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. <br> <br>NoteDevices 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. NoteWithin 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 beforethe default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options. <br> <br>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. <br> <br>NoteThe affected apps are using the ImmGetCompositionString() function.	We are working on a resolution and will provide an update in an upcoming release.
After installing this update, you might receive an APC_INDEX_MISMATCH error with a blue screen when attempting to print to certain printers in some apps.	Issue resolved with an out-of-band update.
After installing updates released March 9, 2021 or March 15, 2021, you might get unexpected results when printing from some apps. Issues might include:<br><ul style="margin-right: 0; margin-left: 0; color: rgba(54, 54, 54, 1)"><li style="margin-left: 0"><p style="color: rgba(30, 30, 30, 1)">Elements of the document might print as solid black/color boxes or might be missing, including barcodes, QR codes, and graphics elements, such as logos.</p></li><li style="margin-left: 0"><p style="color: rgba(30, 30, 30, 1)">Table lines might be missing. Other alignment or formatting issues might also be present.</p></li><li style="margin-left: 0"><p style="color: rgba(30, 30, 30, 1)">Printing from some apps or to some printers might result in a blank page or label.</p></li></ul>	Resolved - Install KB5001649 from the links below.

KB5000808 Direct Download Links

KB5000808 for Windows 10 1909 32-bit
KB5000808 for Windows 10 1909 64 bit

KB5000802 Direct Download Links

KB5000802 for Windows 10 v2004 and v20H2 32-bit
KB5000802 for Windows 10 v2004 and v20H2 64-bit

KB5001649 Direct Download Links 19042.870 Out of Band

32-bit:http://download.windowsupdate.com/d/msdownload/update/software/updt/2021/03/windows10.0-kb5001649-x86_781a5706e11026c9fc48013e86e38a3fc83aeef7.msu
64-bit:windows10.0-kb5001649-x64_aca549448414a5ad559c742c39e9342468a23eb5.msu (windowsupdate.com)
ARM: windows10.0-kb5001649-arm64_5281e77c8079d122aed8b41a88775abaae10abea.msu (windowsupdate.com)

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.)

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.

0 comments

283 answers

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more