NEW 03/12/24
IMPORTANT The following editions of Windows 10, version 21H2 will reach end of service on June 11, 2024:- Windows 10 Enterprise and Education- Windows 10 IoT Enterprise- Windows 10 Enterprise multi-sessionAfter that date, 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.We will continue to support Windows 10 Enterprise LTSC 2021 and Windows 10 IoT Enterprise LTSC 2021.
11/17/20For 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 22H2, see its update history page.**Note **Follow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.
NoteTo 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:
__
Windows 10, version 21H2 editions: Windows 10 Enterprise and Education, Windows 10 IoT Enterprise, Windows 10 Enterprise multi-session, Windows 10 Enterprise LTSC 2021, and
Windows 10 IoT Enterprise LTSC 2021
**Important:**Use EKB KB5003791 to update to Windows 10, version 21H2 on supported editions.
This security update includes quality improvements that were a part of update KB5034843 (released February 27, 2024). When you install this KB:
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 |
---|---|
Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview). | To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration.We are working on a resolution and will provide an update in an upcoming release. |
Copilot in Windows (in preview) is not currently supported when your taskbar is located vertically on the right or left of your screen. | To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen.We are working on a resolution and will provide an update in an upcoming release. |
After you install KB5034203 (dated 01/23/2024) or later updates, some Windows devices that use the DHCP Option 235 to discover Microsoft Connected Cache (MCC) nodes in their network might be unable to use those nodes. Instead, these Windows devices will download updates and apps from the public internet. IT administrators also see increased download traffic on their internet routes.Those of you who use the Home edition of Windows are not likely to experience this issue. MCC and DHCP Option 235 are typically used in enterprise environments. | Option****1: Configure Microsoft Connected Cache endpoint inDOCacheHostpolicy as indicated in Cache hostname. Additionally,DOCacheHostSourcehas to be set to1or removed as indicated in Cache hostname source. By default, theDOCacheHost and DOCacheHostSource policies have no value.Option****2: You can mitigate this issue using Group Policies available through our support channel. Organizations can request help at Support for business.We are working on a resolution and will provide an update in an upcoming release. |
Before installing this updateMicrosoft 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:
If you want to remove the LCUTo 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 informationFor a list of the files that are provided in this update, download the file information for cumulative update 5035845.For a list of the files that are provided in the servicing stack update, download the file information for the SSU - versions 19044.4163 and 19045.4163.