KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928 Win Update

Page 1 of 32 12311 ... LastLast
    KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928

    KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928

    Cumulative Update - April 13, 2021
    Category: Win Update
    Last Updated: 28 Apr 2021 at 17:21
    UPDATE 4/28: KB5001391 CU Windows 10 v2004 build 19041.964 and v20H2 19042.964


    The KB4562830 Enablement Package allows you to go from build 19041 (v2004) to 19042 (v20H2).



    April 13, 2021 - KB5001330 (OS Builds 19041.928 and 19042.928)

    NEW 4/13/21
    REMINDER 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.

    2/24/21
    IMPORTANT As part of the end of support for Adobe Flash, KB4577586 is now available as an optional update from Windows Update (WU) and Windows Server Update Services (WSUS). Installing KB4577586 will remove Adobe Flash Player permanently from your Windows device. Once installed, you cannot uninstall KB4577586. For more details about Microsoft’s plans, see Update on Adobe Flash Player End of Support.

    11/17/20
    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.
    Note Follow @WindowsUpdate to find out when new content is published to the release information dashboard.

    Highlights

    • Updates to improve security when Windows performs basic operations.
    • Updates to improve security when using input devices such as a mouse, keyboard, or pen.

    Improvements and fixes

    Note To view the list of addressed issues, click or tap the OS name to expand the collapsible section.

    Windows 10 servicing stack update - 19041.925 and 19042.925

    • This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

    Windows 10, version 20H2

    This security update includes quality improvements. Key changes include:

    • This build includes all the improvements from Windows 10, version 2004.
    • No additional issues were documented for this release.

    Windows 10, version 2004

    Note: This release also contains updates for Microsoft HoloLens (OS Build 19041.1144) released April 13, 2021. Microsoft will release an update directly to the Windows Update Client to improve Windows Update reliability on Microsoft HoloLens that have not updated to this most recent OS Build.

    This security update includes quality improvements. Key changes include:

    • Addresses an issue in which a principal in a trusted MIT realm fails to obtain a Kerberos service ticket from Active Directory domain controllers (DC). This occurs on devices that installed Windows Updates that contain CVE-2020-17049 protections and configured PerfromTicketSignature to 1 or higher. These updates were released between November 10, 2020 and December 8, 2020. Ticket acquisition also fails with the error, “KRB_GENERIC_ERROR”, if callers submit a PAC-less Ticket Granting Ticket (TGT) as an evidence ticket without providing the USER_NO_AUTH_DATA_REQUIRED flag.
    • Addresses an issue with security vulnerabilities identified by a security researcher. Because of these security vulnerabilities, this and all future Windows updates will no longer contain the RemoteFX vGPU feature. For more information about the vulnerability and its removal, see CVE-2020-1036 and KB4570006. Secure vGPU alternatives are available using Discrete Device Assignment (DDA) in Windows Server LTSC releases (Windows Server 2016 and Windows Server 2019) and Windows Server SAC releases (Windows Server, version 1803 and later versions).
    • Addresses a potential elevation of privilege vulnerability in the way Azure Active Directory web sign-in allows arbitrary browsing from the third-party endpoints used for federated authentication. For more information, see CVE-2021-27092 and Policy CSP - Authentication.
    • Addresses an issue that causes Windows Back up using File History to stop working for a few users. This issue occurs after installing the February 9, 2021 update. The error message is, “Failed to start the backup of user links (error 8007005)”.
    • Security updates to Windows App Platform and Frameworks, Windows Apps, Windows Input and Composition, Windows Office Media, Windows Fundamentals, Windows Cryptography, the Windows AI Platform, Windows Kernel, Windows Virtualization, and Windows Media.

    If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

    For more information about the resolved security vulnerabilities, please refer to the new Security Update Guide website.

    Windows Update Improvements
    Microsoft has released an update directly to the Windows Update client to improve reliability. Any device running Windows 10 configured to receive updates automatically from Windows Update, including Enterprise and Pro editions, will be offered the latest Windows 10 feature update based on device compatibility and Windows Update for Business deferral policy. This doesn't apply to long-term servicing editions.

    Known issues in this update

    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:

    1. 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>
    2. Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>
    3. 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.

    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
    A small subset of users have reported lower than expected performance in games after installing this update. Most users affected by this issue are running games full screen or borderless windowed modes and using two or more monitors. This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy.

    Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.

    How to get this update

    Before installing this update

    Prerequisite:

    Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). If you encounter the error, 0x800f0823 – CBS_E_NEW_SERVICING_STACK_REQUIRED, close the error message and install the last standalone SSU (KB4598481) before installing this LCU. You will not need to install this SSU (KB4598481) again for future updates.

    For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

    Install this update

    Release Channel Available Next Step
    Windows Update and Microsoft Update Yes None. This update will be downloaded and installed automatically from Windows Update.
    Microsoft Update Catalog Yes To get the standalone package for this update, go to the Microsoft Update Catalog website.
    Windows Server Update Services (WSUS) Yes This update will automatically sync with WSUS if you configure Products and Classifications as follows:

    Product: Windows 10, version 1903 and later

    Classification: Security Updates

    If you want to remove the LCU
    To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages.

    Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

    File information

    For a list of the files that are provided in this update, download the file information for cumulative update 5001330.

    For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 19041.925 and 19042.925.


    Source: https://support.microsoft.com/en-us/...f-d67fec538490

    See also: https://techcommunity.microsoft.com/...ce/ba-p/222376


    Direct download links for KB5001330 MSU file from Microsoft Update Catalog:

    Download KB5001330 MSU for Windows 10 v2004 and v20H2 32-bit (x86) - 252.5 MB

    Download KB5001330 MSU for Windows 10 v2004 and v20H2 64-bit (x64) - 555.4 MB

    Download KB5001330 MSU for Windows 10 v2004 and v20H2 ARM64 - 601.0 MB


    Brink's Avatar Posted By:

  1. Brink's Avatar
    Posts : 58,411
    64-bit Windows 11 Pro for Workstations
       #1

    KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928-kb5001330.jpg
      My Computers

  2. CountMike's Avatar
    Posts : 18,858
    W10+Developer Insider + Linux
       #2

    KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928-image.png
      My Computers

  3. RingTailCoon's Avatar
    Posts : 1,388
    Windows 10 HOME 64-BIT
       #3

    Updating... :)

    KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928-untitled-1.jpg
      My Computer

  4. CountMike's Avatar
    Posts : 18,858
    W10+Developer Insider + Linux
       #4

    KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928-image.png
      My Computers

  5. Fabler2's Avatar
    Posts : 3,313
    Windows 10 preview 64-bit Home
       #5

    Downloading.
      My Computers


  6. Posts : 190
    Windows 10 Pro 21H1
       #6

    Also on 21H1, installed no problem. Took about 5 minutes - much better than last month when I had to make a new ISO and do an in-place upgrade to get to .906.

    I was in a state of panic for a few minutes when it hung at 20% before getting to 44%!

    KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928-screenshot-2021-04-13-181655.jpg
      My Computer

  7. CountMike's Avatar
    Posts : 18,858
    W10+Developer Insider + Linux
       #7

    KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928-image.png
      My Computers

  8. kado897's Avatar
    Posts : 41,291
    Windows 10 Home 64bit 21H1 and insider builds
       #8

    Done on my main machine.
      My Computer

  9. CountMike's Avatar
    Posts : 18,858
    W10+Developer Insider + Linux
       #9

    KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928-image.png
      My Computers


 
Page 1 of 32 12311 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:58.
Find Us




Windows 10 Forums