Well, Microsoft just released the April Patch Tuesday updates, and it includes security update KB5001330 which applies to Windows 10 v20H2 and v2004. This update stands out compared to the other ones released today because it affects the way Microsoft Edge (Legacy) is being handled from certain Windows installations.

Microsoft Edge Legacy may not be properly replaced

According to Microsoft’s official changelog covering KB5001330, it seems that the process of replacing Microsoft Edge Legacy with the new version is being hindered when applying this security update: However, they did note that devices that connect directly to Windows Update to receive updates are not affected, including those using Windows Update for Business, and that devices connecting to Windows Update should always receive the latest versions of the SSU and the latest cumulative update without issues. 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. As such, if you plan to install a fresh new copy of Windows 10 v20H2 or v2004 from an offline source, such as an ISO created with the Media Creation Tool, it is better that you wait until this issue is fixed. We hope that this brief intro into what security update KB5001330 brings will make it clearer for you whether you should update now, or wait for the patch fixes that are to come in 2 weeks. Keep in mind that the option of postponing Windows 10 updates is also available, as you can do it for up to 35 days. However, keep in mind that not updating your PC comes with its own downsides, especially given the overall purpose of Patch Tuesday. To ensure that the update process goes smoothly, we recommend that you follow certain steps to ensure an error-free system upgrade. What do you think about this security update? Let us know whether you’ll apply it to your PC or not by leaving us your feedback in the comments section below.

Name * Email * Commenting as . Not you? Save information for future comments
Comment

Δ