This is a summary of the cumulative updates released on April 13th for all the supported consumer releases of Windows 10. Windows 10 version 2004 and version 20H2 - KB5001330, Build 19041.928 and 19042.928 Windows 10 versions 1909 - KB5001337, Build 18363.1500 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 . NEW 4/13/21REMINDER Microsoft removed the Microsoft Edge Legacy desktop application that is out of support in March 2021. In this April 13, 2021 release, we will install the new Microsoft Edge. For more information, see New Microsoft Edge to replace Microsoft Edge Legacy with April’s Windows 10 Update Tuesday release . 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 KB5001330 and KB5001337 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. 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. Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps. To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the using SSU: <ol style="margin-left: 40px"><li style="margin-right: 0; margin-left: 0">Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path></li><li style="margin-right: 0; margin-left: 0">Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path></li><li style="margin-right: 0; margin-left: 0">You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU.</li></ol> If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge . If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business KB5001337 for version 1909 DDL Download KB5001337 MSU for Windows 10 v1909 32-bit (x86) Download KB5001337 MSU for Windows 10 v1909 64-bit (x64) Download KB5001337 MSU for Windows 10 v1909 ARM64 KB5001330 for Windows 10 2004 and 20H2 DDL Download KB5001330 MSU for Windows 10 v2004 and 20H2 32-bit (x86) Download KB5001330 MSU for Windows 10 v2004 and v20H2 64-bit (x64) Download KB5001330 MSU for Windows 10 v2004 and v20H2 ARM64 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.)

KB5001408: Compatibility update for installing and recovering Windows 10, version 1909: April 13, 2021 https://support.microsoft.com/en-us/topic/kb5001408-compatibility-update-for-installaing-and-recovering-windows-10-version-1909-april-13-2021-120d1922-4c71-4880-bb9c-6a3126a2623c

i'm wondering if my problem maybe is having pro as my mom has home on her laptop and has had no problem with updates

Hi Coby, What error are you having? I suggest <a href="https://answers.microsoft.com/en-us/newthread?threadtype=Questions&cancelurl=%2Fen-us%2Fwindows%2Fforum%2Fwindows_10-update%2Fcumulative-updates-april-2021%2F6bf05faa-f9d6-4090-b7db-77b6505ff3c7%3Ftm%3D1618365107142%26rtAction%3D1618367883165&forum=windows&filter=windows_10-update" title="https://answers.microsoft.com/en-us/newthread?threadtype=Questions&cancelurl=%2Fen-us%2Fwindows%2Fforum%2Fwindows_10-update%2Fcumulative-updates-april-2021%2F6bf05faa-f9d6-4090-b7db-77b6505ff3c7%3Ftm%3D1618365107142%26rtAction%3D1618367883165&forum=windows&filter=windows_10-update" rel="ugc nofollow">starting a new thread for help.

system info says i have Version 10.0.19042 Build 19042 (home) I just bought win 10 pro from the store and tried to upgrade. upgrade failed. i installed some windows updates. now update always says: 2021-03 Cumulative Update Preview for Windows 10 Version 20H2 for x64-based Systems (KB5000842) status pending restart even after many restarts.

Cumulative updates April 2021

Sumit 44,316 Volunteer Moderator

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

Windows 10 version 2004 and version 20H2 - KB5001330, Build 19041.928 and 19042.928
Windows 10 versions 1909 - KB5001337, Build 18363.1500

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.

NEW 4/13/21REMINDERMicrosoft removed the Microsoft Edge Legacy desktop application that is out of support in March 2021. In this April 13, 2021 release, we will install the new Microsoft Edge. For more information, see New Microsoft Edge to replace Microsoft Edge Legacy with April’s Windows 10 Update Tuesday release.

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 KB5001330 and KB5001337

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.
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.
Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. <br> <br>NoteDevices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps.	To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the using SSU: <br> <br><br><ol style="margin-left: 40px"><li style="margin-right: 0; margin-left: 0"><p>Extract the cab from the msu via this command line (using the package for KB5000842 as an example): <strong>expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path></strong></p></li><li style="margin-right: 0; margin-left: 0"><p>Extract the SSU from the previously extracted cab via this command line: <strong>expand Windows10.0-KB5000842-x64.cab /f:* <destination path></strong></p></li><li style="margin-right: 0; margin-left: 0"><p>You will then have the SSU cab, in this example named <strong>SSU-19041.903-x64.cab</strong>. Slipstream this file into your offline image first, then the LCU.</p></li></ol><br> <br>If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business

KB5001337 for version 1909 DDL

Download KB5001337 MSU for Windows 10 v1909 32-bit (x86)
Download KB5001337 MSU for Windows 10 v1909 64-bit (x64)
Download KB5001337 MSU for Windows 10 v1909 ARM64

KB5001330 for Windows 10 2004 and 20H2 DDL

Download KB5001330 MSU for Windows 10 v2004 and 20H2 32-bit (x86)
Download KB5001330 MSU for Windows 10 v2004 and v20H2 64-bit (x64)
Download KB5001330 MSU for Windows 10 v2004 and v20H2 ARM64

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

172 answers

Sumit 44,316 Reputation points Volunteer Moderator

2021-04-14T01:52:29+00:00

KB5001408: Compatibility update for installing and recovering Windows 10, version 1909: April 13, 2021

https://support.microsoft.com/en-us/topic/kb5001408-compatibility-update-for-installaing-and-recovering-windows-10-version-1909-april-13-2021-120d1922-4c71-4880-bb9c-6a3126a2623c
Was this answer helpful?

7 people found this answer helpful.

0 comments No comments
Anonymous

2021-04-14T02:01:48+00:00

i'm wondering if my problem maybe is having pro as my mom has home on her laptop and has had no problem with updates
Was this answer helpful?

4 people found this answer helpful.

0 comments No comments
Sumit 44,316 Reputation points Volunteer Moderator

2021-04-14T02:40:23+00:00

Hi Coby,

What error are you having? I suggest starting a new thread for help.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-04-14T03:58:56+00:00

system info says i have Version 10.0.19042 Build 19042 (home)

I just bought win 10 pro from the store and tried to upgrade. upgrade failed.

i installed some windows updates.

now update always says:

2021-03 Cumulative Update Preview for Windows 10 Version 20H2 for x64-based Systems (KB5000842)

status pending restart

even after many restarts.
Was this answer helpful?

8 people found this answer helpful.

0 comments No comments
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