KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685 Win Update

Page 1 of 47 12311 ... LastLast
    KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685

    KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685

    Cumulative Update - December 8
    Category: Win Update
    Last Updated: 12 Jan 2021 at 12:07
    UPDATE 1/12: KB4598242 CU Windows 10 v2004 build 19041.746 and v20H2 19042.746


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



    December 8, 2020 - KB4592438 (OS Builds 19041.685 and 19042.685)

    Applies to: Windows 10 version 2004 all editions, Windows Server version 2004, Windows 10 version 20H2 all editions, Windows Server version 20H2 all editions

    NEW 12/8/20
    IMPORTANT Adobe Flash Player will go out of support on December 31, 2020. For more information, see Adobe Flash end of support on December 31, 2020. Flash content will be blocked from running in Flash Player beginning January 12, 2021. For more information, see Adobe Flash Player EOL General Information Page.


    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.


    11/10/20
    IMPORTANT Because of minimal operations during the holidays and the upcoming Western new year, there won’t be a preview release (known as a “C” release) for the month of December 2020. Normal monthly servicing for both B and C releases will resume in January 2021.


    Highlights

    • Updates to improve security when using Microsoft Edge Legacy.
    • Updates to improve security when using Microsoft Office products.

    Improvements and fixes

    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.1131) released December 8, 2020. 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:
    • Security updates to Microsoft Edge Legacy, the Microsoft Graphics Component, Windows Media, Windows Fundamentals, and Windows Virtualization.

    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.
    [ADDED 12/20] A small number of devices that have installed this update have reported that when running chkdsk /f, their file system might get damaged and the device might not boot. This issue is resolved and should now be prevented automatically on non-managed devices. Please note that it can take up to 24 hours for the resolution to propagate to non-managed devices. Restarting your device might help the resolution apply to your device faster. For enterprise-managed devices that have installed this update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. To find out more about using Group Policies, see Group Policy Overview.

    To mitigate this issue on devices which have already encountered this issue and are unable to start up, use the following steps:

    1. The device should automatically start up into the Recovery Console after failing to start up a few times.
    2. Select Advanced options.
    3. Select Command Prompt from the list of actions.
    4. Once Command Prompt opens, type: chkdsk /f
    5. Allow chkdsk to complete the scan, this can take a little while. Once it has completed, type: exit
    6. The device should now start up as expected. If it restarts into Recovery Console, select Exit and continue to Windows 10.

    Note After completing these steps, the device might automatically run chkdsk again on restart. It should start up as expected once it has completed.

    How to get this update

    Before installing this update

    Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). SSUs improve the reliability of the update process to mitigate potential issues while installing the LCU and applying Microsoft security fixes. For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

    If you are using Windows Update, the latest SSU (KB4593175) will be offered to you automatically. To get the standalone package for the latest SSU, search for it in the Microsoft Update Catalog.

    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

    File information

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

    Note Some files erroneously have “Not applicable” in the “File version” column of the CSV file. This might lead to false positives or false negatives when using some third-party scan detection tools to validate the build.


    Source: https://support.microsoft.com/en-us/...date-kb4592438


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


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

    Download KB4592438 MSU for Windows 10 v2004 and v20H2 32-bit (x86) - 119.5 MB

    Download KB4592438 MSU for Windows 10 v2004 and v20H2 64-bit (x64) - 363.6 MB

    Download KB4592438 MSU for Windows 10 v2004 and v20H2 ARM64 - 398.1 MB
    Brink's Avatar Posted By:

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

    KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685-kb4592438.jpg
      My Computers

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

    KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685-image.png
    Must be some small one.
      My Computers

  3. jh30uk's Avatar
    Posts : 329
    Windows 10
       #3

    Will this install if that other .62 does not?
      My Computer

  4. Geneo's Avatar
    Posts : 1,147
    Windows 10 Pro x64 Retail 21H1
       #4

    6 minutes to download and install. Coming from .662
      My Computers

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

    jh30uk said:
    Will this install if that other .62 does not?
    You won't know until you try it.
      My Computer


  6. Posts : 614
    Windows 10 PRO 64Bit
       #6

    jh30uk said:
    Will this install if that other .62 does not?
    I just tried it and got the same error.

    Ak
      My Computer

  7. larc919's Avatar
    Posts : 3,192
    Windows 10 Pro x64
       #7

    Very fast CU.
      My Computer

  8. steve108's Avatar
    Posts : 13,257
    19041.1083 - 2004/20H1 Home x64
       #8

    KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685-kb4592438.png
      My Computer

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

    alkaufmann said:
    I just tried it and got the same error.

    Ak
    I suspected you might. The problem is with 661.
      My Computer


 
Page 1 of 47 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 04:52.
Find Us




Windows 10 Forums