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. Sumit 44,316 Reputation points Volunteer Moderator
    2021-04-16T13:20:35+00:00

    For anyone logging into the temporary profile issue.

    This happens often after a feature update. Somehow there is a problem with your profile which is the reason why Windows logs you into a temporary one. Your data should be there in C:/Users/<username> folder. Do not copy them over to temporary profile otherwise, it may be lost forever. Backup the files to an external drive if needed. <br> <br>Via the support doc <br><br><br><br> https://support.microsoft.com/en-us/windows/windows-10-error-message-we-can-t-sign-in-to-your-account-18d55f00-a6e7-9106-29ee-54fa223c0ca8<br><br> <br> <br>If you try to sign in to Windows 10 and receive the error message, "We can't sign in to your account" or you see an action center notification saying “You’ve been signed in with a temporary profile,” Windows will create a temporary profile and sign you in to that one. (Note: Any settings or new files created within that temporary profile will be removed after you sign out, so it is important to try to resolve this issue, either by restarting your PC or with the following steps.) Here are some things to try to get signed back in to your Windows profile: <br> <br>Important: Before doing anything, use an external storage device to save any work you’ve done since your last successful sign in. Any files you have created or changed while in the temporary profile will be lost when you sign out. <br> <br>Restart your device in safe mode and sign in with your original profile. Check to see if your settings and files are restored. <br> <br>Restart your device in normal mode and sign in again with your original profile. Check to see if your settings and files are restored. (You might need to restart your device more than once.). <br> <br>If that doesn't help, we would try to uninstall the update. Keep us posted.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2021-04-16T17:01:47+00:00

    FIXED!!!!!!!   A lot of troubleshooting went into this! I hope this process helps fix a lot of people's issues. 
    # Issue debugging and resolution path:

    Running Windows update troubleshooter: finds things wrong and make some changes

    Update still fails.

    # From CMD (Admin Prompt)

    SFC /scannow

    - Passes:

    DISM /Online /Cleanup-Image /CheckHealth

    - Passes:

    DISM /Online /Cleanup-Image /ScanHealth

    - Passes saying can be repaired. 

    DISM /Online /Cleanup-Image /RestoreHealth

    and 

    DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\Sources\install.wim

    - BOTH options FAIL for the same reason!!!!

    # DISM Log Errors:

    2021-04-15 23:58:20, Error                 DISM   DISM Package Manager: PID=6620 TID=21340 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

    2021-04-15 23:58:20, info                  dism   dism package manager: pid=6620 tid=21340 further logs for online package and feature related operations can be found at %windir%\logs\cbs\cbs.log - cpackagemanagerclihandler::executecmdline

    # CBS.Log errors:

    2021-04-15 22:37:55, Error                 CSI    00000bdd (F) STATUS_OBJECT_NAME_NOT_FOUND#48580# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ|DELETE), oa = @0xc4a887d130->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[97]'??\C:\WINDOWS\Servicing\Packages\Package_1_for_KB4601050~31bf3856ad364e35~amd64~~10.0.4330.6.cat'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xc4a887d190, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHA[gle=0xd0000034]

    # Missing:

    C:\WINDOWS\Servicing\Packages*Package_1_for_KB4601050~31bf3856ad364e35~amd64~~10.0.4330.6.cat*';

    # Grab the Windows update number from the package name:

    "KB4601050"

    #note: this update is not part of the ISO yet downloaded from website or built with Windows media creation tool. 

    # Download the package from the MS Update Catalog:

    https://www.catalog.update.microsoft.com/Search.aspx?q=4601050

    # Upon trying to install, you will get a message that says your system does not qualify for this package.

    # note: The Issue is "KB4601050" does not install by default on Intel-based systems. This is why it is ignored by the Windows Update and DISM tool when doing a "/RestoreHealth"

    # To get around the automatic installer saying "NO" do the following:

    1. use 7zIp to extract the MSU file into a folder. (right-click and extract to...)

    2. find the largest CAB file and rename it something manageable like "KB4601050"

    3. Copy the file to a root folder on your OS drive. (c:/packages/...)

    4. from a CMD (admin) prompt install the package:

          dism /Online /Add-Package /PackagePath:"PATH\TO\CAB"

    #Now perform a "/RestoreHealth" 

    DISM /Online /Cleanup-Image /RestoreHealth

    If it completes continue to the next step.

    If it fails again, verify logs and see if the same or different package is missing, and repeat the process.

    # Reboot the computer.

    # Perform Standard Windows update check and install. (It should complete properly now)

    Was this answer helpful?

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

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

  5. Anonymous
    2021-04-17T12:28:19+00:00

    KB5001330 has destroyed our WIFI connections.  Laptops disconnected 1 by 1 as update installed over a couple of days.  Can connect to internet with ethernet easily but WIFI repeatedly drops out. Have uninstalled update after several attempts.  Repeatedly failed to uninstall.  Have reset ipconfig, flushed dns, reset network adapters.  All laptop internal WIFI units now do not work at all.  Some success with USB WIFI adapters but connection is unreliable and can drop out at anytime.  Appalling.

    Printer keeps printing same thing again and again and again.  All printer queues cleared, printers rebooted.  All laptops and desktops rebooted. Still doing it.  All printers turned off. Appalling.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments