KB5007186 Windows 10 2004 19041.1348, 20H2 19042.1348, 21H1 19043.1348 Win Update

Page 1 of 12 12311 ... LastLast
    KB5007186 Windows 10 2004 19041.1348, 20H2 19042.1348, 21H1 19043.1348

    KB5007186 Windows 10 2004 19041.1348, 20H2 19042.1348, 21H1 19043.1348

    Cumulative Update - November 9, 2021
    Category: Win Update
    Last Updated: 22 Nov 2021 at 21:49
    UPDATE 11/22: KB5007253 Windows 10 19041.1382, 19042.1382, 19043.1382, 19044.1382

    The KB5003791 Enablement Package allows you to go from 2004, 20H2, or 21H1 to 19044 (v21H2).

    Download KB5003791 MSU for Windows 10 v21H2 32-bit (x86) - 165 KB
    Download KB5003791 MSU for Windows 10 v21H2 64-bit (x64) - 165 KB
    Download KB5003791 MSU for Windows 10 v21H2 ARM64 - 165 KB


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

    The KB5000736 Enablement Package allows you to go from build 19042 (v20H2) to 19043 (v21H1).




    November 9, 2021 - KB5007186 (OS Builds 19041.1348, 19042.1348, and 19043.1348)

    NEW 11/9/2021
    IMPORTANT Because of minimal operations during the holidays and the upcoming Western new year, there wont be a preview release (known as a C release) for the month of December 2021. There will be a monthly security release (known as a B release) for December 2021. Normal monthly servicing for both B and C releases will resume in January 2022.

    10/12/21
    IMPORTANT Windows 10, version 2004 will reach end of servicing on December 14, 2021. To continue receiving security and quality updates, Microsoft recommends that you update to the latest version of Windows 10.

    11/17/20
    For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. For an overview of Windows 10, version 2004, see its update history page.

    Note Follow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

    Highlights

    • Updates security for your Windows operating system.

    Improvements and fixes

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

    Windows 10, version 21H1

    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 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.1169) released November 9, 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 of a 0 (zero) width Pen to render one pixel regardless of transformation.

    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 and the November 2021 Security Updates.

    Windows 10 servicing stack update - 19041.1310, 19042.1310, and 19043.1310

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

    Known issues in this update

    Symptom Workaround
    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.
    After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING". For more information and a workaround, see KB5005322.
    After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red. 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 non-managed personal devices and non-managed business devices. Restarting your Windows 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 linked below.

    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.

    Group Policy installation files:


    Important Verify that you are using the correct Group Policy for your version of Windows.
    After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:

    • 0x000006e4 (RPC_S_CANNOT_SUPPORT)
    • 0x0000007c (ERROR_INVALID_LEVEL)
    • 0x00000709 (ERROR_INVALID_PRINTER_NAME)

    Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.
    For workarounds and the latest status for this issue, please see Windows release health:


    We are presently investigating and will provide an update in an upcoming release.
    After installing this update, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted. To mitigate this issue, you will need to uninstall the affected app, then install the latest version of the app.

    We are working on a resolution and will provide an update in an upcoming release.

    How to get this update

    Before installing this update

    Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

    Prerequisite:

    For Windows Server Update Services (WSUS) deployment or when installing the standalone package from Microsoft Update Catalog:

    If your devices do not have the May 11, 2021 update (KB5003173) or later LCU, you must install the special standalone August 10, 2021 SSU (KB5005260).

    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.
    Windows Update for Business Yes None. This update will be downloaded and installed automatically from Windows Update in accordance with configured policies.
    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 5007186.

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


    Source: https://support.microsoft.com/en-us/help/5007186


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

    Download KB5007186 MSU for Windows 10 v2004, v20H2, and v21H1 32-bit (x86) - 301.9 MB

    Download KB5007186 MSU for Windows 10 v2004, v20H2, and v21H1 64-bit (x64) - 643.2 MB

    Download KB5007186 MSU for Windows 10 v2004, v20H2, and v21H1 ARM64 - 673.4 MB
    Brink's Avatar Posted By: Brink
    09 Nov 2021

  1. Ghot's Avatar
    Posts : 15,732
    Win 10 Home 10.0.19044.1469 (x64) [21H2]
       #1

    Downloaded and installed, no issues.


    KB5007186 Windows 10 2004 19041.1348, 20H2 19042.1348, 21H1 19043.1348-image1.png



    KB5007186 Windows 10 2004 19041.1348, 20H2 19042.1348, 21H1 19043.1348-image2.png
      My Computer

  2. AndreTen's Avatar
    Posts : 26,017
    Windows 10 (Pro and Insider Pro)
       #2

    Installed on 2 systems for now. Went fine. Also installing on Insider RP system (why do I have one there??) Oh, it's 21H2 system
      My Computers

  3. IronZorg89's Avatar
    Posts : 2,557
    Windows 10 pro x64-bit
       #3

    Downloading + installing now.
      My Computers

  4. kado897's Avatar
    Posts : 44,459
    Windows 10 Home 64bit 21H1 and insider builds
       #4

    First one done.
      My Computer

  5. steve108's Avatar
    Posts : 18,747
    19041.1466 - 2004/20H1 Pro x64
       #5

    Microsoft Windows [Version 10.0.19041.1348] - no issues so far
      My Computer

  6. larc919's Avatar
    Posts : 3,275
    Windows 10 Pro x64
       #6

    Already on 19044.1320, but this smoothly took it to 19044.1348.
      My Computer


  7. Posts : 2
    Windows 11
       #7

    Isn't 21H2 enablement package released today also?
      My Computer

  8. Brink's Avatar
    Posts : 60,436
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #8

    KB5007186 Windows 10 2004 19041.1348, 20H2 19042.1348, 21H1 19043.1348-kb5007186.jpg
      My Computers

  9. IronZorg89's Avatar
    Posts : 2,557
    Windows 10 pro x64-bit
       #9

    Any word or idea yet on 21H2's official release?
      My Computers


 

  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 09:33.
Find Us




Windows 10 Forums