since i installed this update kb5001330 my laptop always crashed on start up and freezing on tthe middle of using the machine.any help how stop these crashing and freezing.
Cumulative updates April 2021
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
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.)
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.
172 answers
Sort by: Most helpful
-
Anonymous
2021-05-09T21:12:09+00:00 -
Anonymous
2021-05-08T03:52:21+00:00 Ever since the April update, Windows Defender definition updates will not work from windows updates and must be done manually from within windows defender itself.
The error code that is being produced is error 0x80070643
I am still on version 1.339.179.0 for windows defender, and from searching microsoft it seems that there was a new version released with the april updates,
New version: 4.18.2104.9
Update for Microsoft Defender antimalware platform
So I don't know what is going on, why my machine is not updating with the new version properly and windows update is not doing its job. The troubleshooter says nothing is wrong. I've manually tried to download Defender and it says I have the latest version but of course the page for that shows
1.339.179.04.18.2103.7 as being current.- Platform Version: 4.18.2103.7
This incremented to 1.339.180.0 in the time I started writing this.(edited to correct for grabbing security intelligence version accidentally and not platform version, which is the issue.)
Soooo what's going on. Should I just keep updating via Defender until Windows Update sorts itself out in May in a few days? Hopefully?
- Platform Version: 4.18.2103.7
-
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
-
Anonymous
2021-04-19T22:27:07+00:00 My Win-7-64 rarely gives a problem and it does not do my thinking.
-
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
andDISM /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)