Skip to the content
The Update Bureau
Windows 10 22H2 Windows 10 22H2 Optional preview
Preview

KB5041582

KB5041582: Cumulative update for Windows 10, version 22H2, August 2024. Fixes system hangs; dual-boot Linux may fail to start

In short

Addresses memory leaks and hangs in Windows 10, version 22H2. Devices that dual-boot Linux might have trouble starting Linux after the update.

Does it affect you? Applies to: Devices running Windows 10, version 22H2. The update is available for x64, Arm64, and x86 systems; the page does not specify editions.

Build
19045.4842
Restart
Required
Review notes Additional details from the official release notes (1) Read note
  • Known issues For Windows-only systems, the page describes setting the documented registry key to ensure the SBAT security update is applied; it does not give a Group Policy workaround.

The official sources are linked at the end of the page.

What changes

Fixes 4 changes

Input Method Editor (IME)

  • Addresses a memory leak that might occur when you close a window after a combo box has input focus.1

Bluetooth

  • Addresses a memory leak in a device that might cause an app to stop responding.1

Bind Filter Driver

For: devices accessing symbolic links

  • Addresses a problem that might cause the system to stop responding when it accesses symbolic links.1

Unified Write Filter (UWF) and Microsoft System Center Configuration Manager (SCCM)

For: devices managed with SCCM and UWF

  • Addresses a deadlock that can make an SCCM task to re-enable UWF fail, so the device does not restart when expected.1

Improvements 2 changes

Country and Operator Settings Asset

Verified in package
  • COSA profiles are updated for certain mobile operators.2

Servicing stack

  • The update includes quality improvements to the component that installs Windows updates.3
    The combined package includes servicing stack update KB5041581, build 19045.4840.

Known issues

  1. Resolved Affects: Organizations and IT administrators Resolved by KB5045594

    After installing this update, or subsequent updates, a small subset of Azure Virtual Desktop customers using multi-session hosts (AVD) may experience the following issues: - An extended 10-to-30-minu…

    A small subset of Azure Virtual Desktop customers using multi-session hosts might experience a 10-to-30-minute black-screen hang after sign-in and single sign-on failures in Office apps. KB5045594 or later, together with one of the resolution options in KB5048864, resolves the issue; both actions are required.4

    Resolution Fixed in KB5045594

    Install KB5045594 (or a later cumulative update) on affected devices. No manual workaround is required after updating.

  2. Resolved Affects: Organizations and IT administrators Resolved by KB5045594

    After installing this update, you might experience a black screen when you login to Azure Virtual Desktop (AVD).

    Azure Virtual Desktop users might see a black screen when signing in and be unable to log out. KB5045594 or later, together with one of the resolution options in KB5048864, resolves the issue; both actions are required.4

    Resolution Fixed in KB5045594

    Install KB5045594 (or a later cumulative update) on affected devices. No manual workaround is required after updating.

  3. Open Affects: Everyone

    After installing this update, you might be unable to [change your user account profile picture](https://support.microsoft.com/en-us/windows/change-your-account-picture-3645cdc7-acab-49d2-76a9-4ce7e5e…

    After installing this update, changing your user account profile picture might fail with error 0x80070520. Microsoft says the issue has very limited or no impact for this Windows version.5

    How to apply the workaround Workaround

    Contact Windows support for help if the issue occurs.5

  4. Open Affects: Everyone

    After installing this security update, you might face issues with booting Linux if you have enabled the dual-boot setup for Windows and Linux in your device.

    On some devices with a Windows-and-Linux dual-boot setup, Linux might fail to start and display “Verifying shim SBAT data failed: Security Policy Violation.” Customized dual-boot methods might not be detected, causing the SBAT setting to be applied when it should not be.6

    How to apply the workaround Registry / GPO

    Install the September 2024 security update or later. Dual-boot systems need no additional steps after that; Windows-only systems can set the registry key documented in the cited CVE articles.6

    Step-by-step workaround instructions
    2 steps
    Show steps Hide steps
    Step-by-step procedure
    1. Install the September 2024 security update or a later update.
    2. On Windows-only systems, set the registry key documented in CVE-2022-2601 and CVE-2023-40547.

Technical details

Data sheet · Security · Downloads · Components Click to collapse or expand

Data sheet

Released
2024-08-29
Classification
Updates
Type
Cumulative update
Restart
Required
Replaces
KB5040525, KB5039299, KB5037849, KB5036979
+3 earlier KB5035941, KB5034843, KB5034203
Replaced by
KB5043131
VersionBuildChannel
22H2 19045.4842 General availability

Security

No vulnerabilities are listed for this update.

Updated components

1,827 files changed since the previous update for the same versions.

Top changed componentsFiles
Graphics and display35
Remote Desktop30
File Explorer and shell24
Secure Boot24
Settings17
Search14
Hyper-V and virtualization11
Kernel11
Security and sign-in11
Emoji and input10
Networking7
Printing7

Verified in package: changed files confirm Country and Operator Settings Asset.

Sources

Updated
Cited passages from Microsoft's official notes (6)
  1. 1. [Input Method Editor (IME)] When a combo box has input focus, a memory leak might occur when you close that window. support.microsoft.com
  2. 2. [Country and Operator Settings Asset] This update brings COSA profiles up to date for certain mobile operators. support.microsoft.com
  3. 3. This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. support.microsoft.com
  4. 4. Note that you need to perform both actions to resolve the issue. support.microsoft.com
  5. 5. After further investigation, we concluded this issue has very limited or no impact for this Windows version.If you encounter this issue on your device, please contact Windows support for help support.microsoft.com
  6. 6. Additional improvements to resolve this issue were included in the May 2025 Windows security update (KB5058379) and later updates. support.microsoft.com
Checked automatically: 8 of 8 checks passed, 6 quoted passages · compared with Microsoft's page on Oct 20, 2026
  • Quotes found in the official pages: passed
  • Numbers found in the sources: passed
  • Vulnerabilities from the dossier only: passed
  • Links to allowed domains only: passed
  • Every official change covered: passed
  • Readable plain text: passed
  • Changes confirmed by the file list: passed
  • Sources agree: passed

A second AI read the text against the sources: correctness 4/5, clarity 4/5, completeness 5/5. How we work

Published by The Update Bureau. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake