Windows 10, version 21H2

Find information on known issues and the status of the rollout for Windows 10, version 21H2. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.

Current status as of January 20, 2022 (PT)
Windows 10, version 21H2 is available for users with select devices running Windows 10, versions 2004 and higher who manually seek to “Check for updates” via Windows Update. Devices currently on Windows 10, version 2004 or newer will have a fast installation experience because the update will install like a monthly update. For more information on how to get this update, watch our video.
 
We also started the first phase in our rollout for machine learning (ML) training, targeting devices on Windows 10, version 20H2 that are approaching end of servicing to update automatically to Windows 10, version 21H2. We will continue to train our machine learning model through all phases to intelligently rollout new versions of Windows 10, and deliver a smooth update experience.
 
As always, we recommend that you update your devices to the latest version of Windows 10 or upgrade eligible devices to Windows 11 to take advantage of the latest features and advanced protections from the latest security threats.

    Known issues

    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    SummaryOriginating updateStatusLast updated
    Outlook search might not locate recent emails
    Searches on Outlook desktop app might fail when emails are stored locally in PST or OST files
    OS Build 19041.1387
    KB5007253
    2021-11-22
    Resolved
    2022-01-19
    15:56 PT
    Certain IPSEC connections might fail
    Some VPN clients using IPSEC or Layer 2 Tunneling Protocol (L2TP) might have issues connecting.
    OS Build 19041.1466
    KB5009543
    2022-01-11
    Resolved
    KB5010793
    2022-01-17
    14:00 PT
    The text cursor in some apps might move unexpectedly when using a Japanese IME
    Text input using a Japanese IME might be entered out of order or the text cursor might move unexpectedly.
    OS Build 19041.1387
    KB5007253
    2021-11-22
    Resolved
    2022-01-04
    17:58 PT

    Issue details

    January 2022

    Outlook search might not locate recent emails

    StatusOriginating updateHistory
    ResolvedOS Build 19041.1387
    KB5007253
    2021-11-22
    Resolved: 2022-01-19, 15:56 PT
    Opened: 2022-01-19, 15:40 PT
    After installing KB5007253 or later updates, recent emails might not appear in search results on Outlook desktop app. This issue is related to emails which have been stored locally in a PST or OST files. It might affect POP and IMAP accounts, as well as Microsoft Exchange and Microsoft 365 hosted accounts. If the default search in the Outlook app is set to server search, the issue will only affect the advanced search.
     
    Workaround: To mitigate the issue, you can disable Windows Desktop Search which will cause Outlook to use its built-in search. For instructions, see Outlook Search not showing recent emails after Windows update KB5008212.

    Resolution: 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 consumer 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 (preferred). Important Verify that you are using the correct Group Policy for your version of Windows.

    Group Policy:
    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
    • Server: Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019

    Certain IPSEC connections might fail

    StatusOriginating updateHistory
    Resolved KB5010793OS Build 19041.1466
    KB5009543
    2022-01-11
    Resolved: 2022-01-17, 14:00 PT
    Opened: 2022-01-13, 11:05 PT
    After installing KB5009543, IP Security (IPSEC) connections which contain a Vendor ID might fail. VPN connections using Layer 2 Tunneling Protocol (L2TP) or IP security Internet Key Exchange (IPSEC IKE) might also be affected.

    Workaround: To mitigate the issue for some VPNs, you can disable Vendor ID within the server-side settings. Note: Not all VPN servers have the option to disable Vendor ID from being used.

    Resolution: This issue was resolved in the out-of-band update KB5010793. It is a cumulative update, so you do not need to apply any previous update before installing it. If you would like to install the update, you will need to Check for updates and select "Optional updates" and then select KB5010793. To get the standalone package for KB5010793, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB5010793 will not install automatically.

    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB
    • Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016

    The text cursor in some apps might move unexpectedly when using a Japanese IME

    StatusOriginating updateHistory
    ResolvedOS Build 19041.1387
    KB5007253
    2021-11-22
    Resolved: 2022-01-04, 17:58 PT
    Opened: 2022-01-04, 17:29 PT
    After installing KB5007253, text input using a Japanese IME might be entered out of order or the text cursor might move unexpectedly in apps that use the multibyte character set (MBCS). This issue affects both the Microsoft Japanese IME and third-party Japanese IMEs.

    Resolution: 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 consumer 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 (preferred). Important Verify that you are using the correct Group Policy for your version of Windows.

    Group Policy:
    Affected platforms:
    • Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
    • Server: Windows Server 2022