Cumulative updates April 2021

Sumit 44,316 Reputation points Volunteer Moderator
2021-04-14T01:49:06+00:00

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

  1. Windows 10 version 2004 and version 20H2 - KB5001330, Build 19041.928 and 19042.928
  2. 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

KB5001330 for Windows 10 2004 and 20H2 DDL

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

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.

0 comments

172 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-05-06T09:49:04+00:00

    I went through all this as well (see my previous posting below) and I reinstalled W10. I lost no data, apps or programs. On my Outlook 2013 it had, however, cleared my email filters (I have several email addresses that should automatically sort to the correct in box) which took 5 minutes to sort out and my screen saver had defaulted to the W10 standard one. Other than that it booted up into my familiar home screen, with all my icons and shortcuts and taskbar shown as previously.

    "So after taking a precautionary image backup I reinstalled W10 from a virtually mounted windows.iso making sure I had the correct version - in my case 20H2, 64-bit, UK English. This took 2.5 hours but it also automatically loaded all the updates, including KB5001330, and all of the data, settings etc remain unchanged. It is now running, as far as I can tell, absolutely correctly."

    Since then there have been other updates and all went like a dream. I understand the nervousness in a reinstall but it seems to be the only solution that works. Now sfc /scannow, DISM commands all perform perfectly. Perhaps every so often, after a build up of many minor corruptions a reinstall clears it all and is the only way forward. I'd spent hours and hours trying lots of recommended solutions and they all failed. In the future, if I get this sort unsolvable issue, I will move to doing a reinstall much sooner. Bite the bullet.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-05-06T11:04:08+00:00

    Hi this is a first time i'm here and join in answer microsoft. So i have a error. my windows have problem when i update to latest version 

    "2021-04 cumulative update for windows 10 version 20h2 for x64-based systems (KB5001391)"

    and "servicing stack 10.0.19041.963" after update my  "explorer.exe" is error, i'm not sure but when i click to background or anything use explorer to run > it's always Crash, Not Responding , the screen goes light write then restart explorer.exe and it repeats every time I click

    i was do somthing hope i can fix it but can't, i was try to run new explorer task in task manager, try to uninstall update and update again, try go in safe mode, check EFI Disk, Restart, or anything i can but problem still exist. i Think maybe problem is from servicing stack 10.0.19041.963 because i can't remove that update and never check that, also after many time my Window Update have error "we couldn't complete the updates undoing" and other error , please tell me how to fix this error

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-05-06T18:09:53+00:00

    merci beaucou

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2021-05-06T19:22:07+00:00

    The Windows update KB5001330 is killing my use of my printer, HP Color LaserJet MFP M281fdw. I've tried to install new drivers, but it will NOT allow me to install any driver for this printer, rendering this printer useless. It has also remove ALL my restore point. I literally had to do a fresh install of my Windows 10 Home Edition. The only way I can continue to use my computer is to turn off updates.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  5. 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