KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486 Win Update

Page 1 of 5 123 ... LastLast
    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486

    Cumulative Update - January 10, 2023
    Category: Win Update
    Last Updated: 19 Jan 2023 at 18:09

    UPDATE 1/19: KB5019275 Windows 10 19042.2546, 19044.2546, and 19045.2546 - Jan. 19


    January 10, 2023 - KB5022282 (OS Builds 19042.2486, 19044.2486, and 19045.2486)

    Windows 10 Enterprise Multi-Session, version 20H2 More...

    Important: For Windows Recovery Environment (WinRE) devices, see the Special instructions for Windows Recovery Environment (WinRE) devices in the How to get this update section to address security vulnerabilities in CVE-2022-41099.

    1/3/23
    IMPORTANT The retired, out-of-support Internet Explorer 11 desktop application will be permanently turned off using a Microsoft Edge update on certain versions of Windows 10 on February 14, 2023. Go to Internet Explorer 11 desktop app retirement FAQ for more information.

    1/10/23
    REMINDER All editions of Windows 10, version 21H1 reached end of service on December 13, 2022. After December 13, 2022, these devices will not receive monthly security and quality updates. These updates contain protections from the latest security threats. To continue receiving security and quality updates, we recommend that you update to the latest version of Windows.

    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 20H2, see its update history page.

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

    Highlights

    • This update addresses security issues for your Windows operating system.

    Improvements

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

    Windows 10, version 22H2

    Important: Use EKB KB5015684 to update to Windows 10, version 22H2.

    This security update includes quality improvements. Key changes include:

    • This build includes all the improvements from the supported Windows 10, version 20H2 editions.
    • No additional issues are documented for this release.

    Windows 10, version 21H2

    Important: Use EKB KB5003791 to update to Windows 10, version 21H2.

    This security update includes quality improvements. Key changes include:

    • This build includes all the improvements from the supported Windows 10, version 20H2 editions.
    • No additional issues are documented for this release.

    Windows 10, version 20H2 editions: Windows 10 Enterprise Multi-Session, Windows 10 Enterprise and Education, Windows 10 IoT Enterprise

    Important: Use EKB KB4562830 to update to the supported editions of Windows 10, version 20H2.

    This security update includes quality improvements. When you install this KB:

    • This update addresses issues that affect the Local Session Manager (LSM). These issues might allow users who do not have admin rights to perform actions that only an admin can.
    • This update addresses a known issue that affects apps that use Microsoft Open Database Connectivity (ODBC) SQL Server Driver (sqlsrv32.dll) to connect to databases. The connection might fail. You might also receive an error in the app, or you might receive an error from the SQL Server.
    • This update addresses a known issue that might affect startup on some Windows devices. They might receive an error (0xc000021a) and have a blue screen.

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

    For more information about security vulnerabilities, please refer to the new Security Update Guide website and the January 2023 Security Updates.

    Windows 10 servicing stack update - 19042.2300, 19044.2300, and 19045.2300

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

    How to get this update

    Special instructions for Windows Recovery Environment (WinRE) devices

    Devices with Windows Recovery Environment (WinRE) will need to update both Windows and WinRE to address security vulnerabilities in CVE-2022-41099. Installing the update normally into Windows will not address this security issue in WinRE. For guidance on how to address this issue in WinRE, please see CVE-2022-41099.

    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:

    Based on your installation scenario, choose one of the following:

    1. For offline OS image servicing:
      If your image does not have the March 22, 2022 (KB5011543) or later LCU, you must install the special standalone May 10, 2022 SSU (KB5014032) before installing this update.
    2. 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 (KB5003173) or later LCU, you must install the special standalone August 10, 2021 SSU (KB5005260) before installing this update.

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

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

    Source: https://support.microsoft.com/en-us/...2-8cd9146b47fd


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

    Download KB5022282 MSU for Windows 10 v20H2, v21H1, v21H2, and v22H2 32-bit (x86) - 359.8 MB

    Download KB5022282 MSU for Windows 10 v20H2, v21H1, v21H2, and v22H2 64-bit (x64) - 693.7 MB

    Download KB5022282 MSU for Windows 10 v20H2, v21H1, v21H2, and v22H2 ARM64 - 712.5 MB


    UUP Dump:

    32-bit ISO download: Select language for Feature update to Windows 10, version 22H2 (19045.2486) x86 - UUP dump

    64-bit ISO download: Select language for Feature update to Windows 10, version 22H2 (19045.2486) amd64 - UUP dump

    ARM64 ISO download: Select language for Feature update to Windows 10, version 22H2 (19045.2486) arm64 - UUP dump

    UUP Dump - Download Windows Insider ISO Tutorial | Windows 11 Forum
    Brink's Avatar Posted By: Brink
    10 Jan 2023


  1. Posts : 69,003
    64-bit Windows 11 Pro for Workstations
       #1

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486-kb5022282.jpg
      My Computers


  2. Posts : 1,482
    W10 22H2 19045.3031
       #2

    Download from WU. Fast install, no known problems. (.2486)
      My Computers


  3. Posts : 92
    Windows 10 Home 64 bit 21H2
       #3

    Done in 10 minutes, no problems so far.
      My Computer


  4. Posts : 89
    W10 Home 22H2
       #4

    Everything updated as due:

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486-capturar.png

    But this already typical error appears but with Chinese characters:

    Code:
     System 
    
      - Provider 
    
       [ Name]  Windows Error Reporting 
     
      - EventID 1001 
    
       [ Qualifiers]  0 
     
       Version 0 
     
       Level 4 
     
       Task 0 
     
       Opcode 0 
     
       Keywords 0x80000000000000 
     
      - TimeCreated 
    
       [ SystemTime]  2023-01-10T18:09:22.1269433Z 
     
       EventRecordID 121620 
     
       Correlation 
     
      - Execution 
    
       [ ProcessID]  0 
       [ ThreadID]  0 
     
       Channel Application 
     
       Computer DESKTOP-******
     
       Security 
     
    
    - EventData 
    
       INVALID_REQUEST 
       0 
       WindowsServicingFailureInfo 
       Não disponível 
       0 
       10.0.19041.2300:1 
       0x800F0984 0x800F0984 Matching binary: LxssManager.dll missing for component: amd64_microsoft-windows-lxss-manager_31bf3856ad364e35_10.0.19041.2486_none_f31086c4800002aa 
       楆敬›瑳牯汥祡畯⹴灣⡰㘱㐹
*潃灭湯湥却潴敲㨺剃睡瑓牯䱥祡畯㩴䠺摹慲整楆敬獕湩䙧牯慷摲湁剤癥牥敳敄瑬獡 
        
        
        
        
        
        
        
       \\?\C:\WINDOWS\Logs\CBS\CBS.log \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20230106213041.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20230106211419.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20230105195528.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20221231134629.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20221227173622.cab \\?\C:\WINDOWS\servicing\Sessions\Sessions.xml \\?\C:\WINDOWS\servicing\Sessions\31008029_3823865106.xml \\?\C:\WINDOWS\Logs\Cbs\FilterList.log \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E6D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E8E.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EAC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EBD.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1ECD.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_10.0.19041.2300__8ba5aa2391d225328c13c362a3c0c66da0ae853d_00000000_cab_a589fa1d-de5e-4702-abad-23f296a3930d\memory.hdmp \\?\C:\Windows\Temp\WER1F1C.tmp.WERDataCollectionStatus.txt 
       \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.19041.2300__8ba5aa2391d225328c13c362a3c0c66da0ae853d_00000000_a589fa1d-de5e-4702-abad-23f296a3930d 
        
       0 
       a589fa1d-de5e-4702-abad-23f296a3930d 
       268435456 
        
       0 
    
    ______________________________________________________________________________________________________________
    
    - System 
    
      - Provider 
    
       [ Name]  Windows Error Reporting 
     
      - EventID 1001 
    
       [ Qualifiers]  0 
     
       Version 0 
     
       Level 4 
     
       Task 0 
     
       Opcode 0 
     
       Keywords 0x80000000000000 
     
      - TimeCreated 
    
       [ SystemTime]  2023-01-10T18:09:21.3715007Z 
     
       EventRecordID 121619 
     
       Correlation 
     
      - Execution 
    
       [ ProcessID]  0 
       [ ThreadID]  0 
     
       Channel Application 
     
       Computer DESKTOP-**************
     
       Security 
     
    
    - EventData 
    
        
       0 
       WindowsServicingFailureInfo 
       Não disponível 
       0 
       10.0.19041.2300:1 
       0x800F0984 0x800F0984 Matching binary: LxssManager.dll missing for component: amd64_microsoft-windows-lxss-manager_31bf3856ad364e35_10.0.19041.2486_none_f31086c4800002aa 
       楆敬›瑳牯汥祡畯⹴灣⡰㘱㐹
*潃灭湯湥却潴敲㨺剃睡瑓牯䱥祡畯㩴䠺摹慲整楆敬獕湩䙧牯慷摲湁剤癥牥敳敄瑬獡 
        
        
        
        
        
        
        
       \\?\C:\WINDOWS\Logs\CBS\CBS.log \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20230106213041.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20230106211419.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20230105195528.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20221231134629.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20221227173622.cab \\?\C:\WINDOWS\servicing\Sessions\Sessions.xml \\?\C:\WINDOWS\servicing\Sessions\31008029_3823865106.xml \\?\C:\WINDOWS\Logs\Cbs\FilterList.log 
        
        
       0 
       a589fa1d-de5e-4702-abad-23f296a3930d 
       262148 
        
       0 
    
    _______________________________________________________________________________________________________
    
    - System 
    
      - Provider 
    
       [ Name]  Windows Error Reporting 
     
      - EventID 1001 
    
       [ Qualifiers]  0 
     
       Version 0 
     
       Level 4 
     
       Task 0 
     
       Opcode 0 
     
       Keywords 0x80000000000000 
     
      - TimeCreated 
    
       [ SystemTime]  2023-01-10T18:09:21.3675102Z 
     
       EventRecordID 121618 
     
       Correlation 
     
      - Execution 
    
       [ ProcessID]  0 
       [ ThreadID]  0 
     
       Channel Application 
     
       Computer DESKTOP-**********
     
       Security 
     
    
    - EventData 
    
        
       0 
       WindowsServicingFailureInfo 
       Não disponível 
       0 
       10.0.19041.2300:1 
       0x800F0984 0x800F0984 Matching binary: LxssManager.dll missing for component: amd64_microsoft-windows-lxss-manager_31bf3856ad364e35_10.0.19041.2486_none_f31086c4800002aa 
       楆敬›瑳牯汥祡畯⹴灣⡰㘱㐹
*潃灭湯湥却潴敲㨺剃睡瑓牯䱥祡畯㩴䠺摹慲整楆敬獕湩䙧牯慷摲湁剤癥牥敳敄瑬獡 
        
        
        
        
        
        
        
       \\?\C:\WINDOWS\Logs\CBS\CBS.log \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20230106213041.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20230106211419.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20230105195528.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20221231134629.cab \\?\C:\WINDOWS\Logs\CBS\CbsPersist_20221227173622.cab \\?\C:\WINDOWS\servicing\Sessions\Sessions.xml \\?\C:\WINDOWS\servicing\Sessions\31008029_3823865106.xml \\?\C:\WINDOWS\Logs\Cbs\FilterList.log \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E6D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E8E.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EAC.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EBD.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1ECD.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_10.0.19041.2300__8ba5aa2391d225328c13c362a3c0c66da0ae853d_00000000_cab_a589fa1d-de5e-4702-abad-23f296a3930d\memory.hdmp \\?\C:\Windows\Temp\WER1F1C.tmp.WERDataCollectionStatus.txt 
       \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_10.0.19041.2300__8ba5aa2391d225328c13c362a3c0c66da0ae853d_00000000_cab_a589fa1d-de5e-4702-abad-23f296a3930d 
        
       0 
       a589fa1d-de5e-4702-abad-23f296a3930d 
       4 
        
       0
    But no errors detected:

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486-capturar.png
    Last edited by Brink; 10 Jan 2023 at 13:58. Reason: code box
      My Computer


  5. Posts : 1,750
    Windows 10 HOME 64-BIT
       #5

    Czecher said:
    Done in 10 minutes, no problems so far.
    Same! :)
      My Computer


  6. Posts : 128
    Windows 10 Pro
       #6

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486-100123.jpg

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486-2486.jpg

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486-sfc-dism.jpg

    First update for 2023....Happy new Year!!
    Last edited by PanosG; 10 Jan 2023 at 16:01.
      My Computer


  7. WXC
    Posts : 13,170
    Windows 10 Pro 64-bit 22H2 19045.4046
       #7

    19045.2486 ~ Quick and uneventful. 20 minutes, from start back to desktop.

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486-screenshot-238-.png

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486-screenshot-239-.png
      My Computer


  8. Posts : 235
    Win10 Pro 64 BIT
       #8

    upd comp

    KB5022282 Windows 10 19042.2486,19044.2486, 19045.2486-winver22h2.jpg
      My Computer


  9. Posts : 208
    Win 10
       #9

    So this is suppose to fix the 00021a blue screen issue of last month's patch?
      My Computer


 

  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 10:37.
Find Us




Windows 10 Forums