Windows 10, version 21H2

Find information on known issues and the status of the Windows 10, version 21H2 rollout. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates.

Current status as of June 13, 2023

As of June 13, 2023, Home, Pro, Pro Education and Pro for Workstations editions of Windows 10, version 21H2 have reached end of servicing. The June 2023 security update, released on June 13, 2023, is the last update available for these editions. Devices running these editions will no longer receive monthly security and preview updates containing protections from the latest security threats. Enterprise, Education, and Enterprise multi-session editions for this version will reach end of servicing on June 11, 2024 and will receive security updates until then.

To help keep you protected and productive, Windows Update will automatically initiate a feature update for Windows 10 consumer devices and non-managed business devices that are at, or within several months of reaching, end of servicing. This keeps your device supported and receiving monthly updates that are critical to security and ecosystem health. For these devices, you will be able to choose a convenient time for your device to restart and complete the update.

As always, we recommend that you update your devices to the latest version of Windows 10 or upgrade eligible devices to Windows 11. For detailed information, see the Windows 10, version 21H2 end of servicing (Home & Pro) lifecycle page. For information about servicing timelines and lifecycle, see Windows 10 release informationWindows 11 release informationLifecycle FAQ - Windows, and Microsoft Lifecycle Policy search tool.

    Known issues

    See open issues, content updated in the last 30 days, and information on safeguard holds. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge).

    SummaryOriginating updateStatusLast updated
    The January 2024 Windows RE update might fail to install
    WinRE is the Windows Recovery Environment. The update fails if there's insufficient free space in the WinRE partition.
    N/A
    KB5034441
    2024-01-09
    Mitigated
    2024-02-09
    17:04 PT
    BitLocker might incorrectly receive a 65000 error in MDMs
    "Requires Device Encryption" might incorrectly report as an error in some managed environments.
    N/A

    Mitigated
    2023-10-31
    10:06 PT
    Devices with locale set to Croatia might not utilize the expected currency
    This can affect applications which retrieve the device's currency for purchases or other transactions
    N/A

    Confirmed
    2023-10-31
    10:06 PT

    Issue details

    January 2024

    The January 2024 Windows RE update might fail to install

    StatusOriginating updateHistory
    MitigatedN/A
    KB5034441
    2024-01-09
    Last updated: 2024-02-09, 17:04 PT
    Opened: 2024-01-12, 14:10 PT

    Devices attempting to install the January 2024 Windows Recovery Environment update ( KB5034441) might display an error related to the size of the Recovery Environment's partition. The Windows Recovery Environment (WinRE) is used to repair or recover from issues affecting Windows.

    Resulting from this error, the following message might be displayed.

    • ​"0x80070643 - ERROR_INSTALL_FAILURE"

    Important: If your Windows device does not have a recovery environment configured, you do not need this update ( KB5034441). In this case, the error can be ignored.

    To determine whether your device has a recovery environment configured, inspect the WinRE status by following these steps:

    1. ​Open a Command Prompt window (cmd) as admin.
    2. ​To check the WinRE status, run reagentc /info. If the WinRE is configured, a "Windows RE status" field will appear in the output, with value "Enabled". If WinRE is not configured, this field will have the value "Disabled".

    Workaround: It might be necessary to increase the size of the WinRE partition in order to avoid this issue and complete the installation. Note that 250 megabytes of free space is required in the recovery partition. Devices which do not have sufficient free space in the recovery partition can use a script to extend the partition size. A sample script has been provided in the documentation for adding an update package to WinRE, Extend the Windows RE Partition. Guidance to manually change the WinRE partition size can additionally be found in KB5028997: Instructions to manually resize your partition to install the WinRE update.

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    Affected platforms:

    • ​Client: Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2
    • ​Server: Windows Server 2022

    October 2023

    BitLocker might incorrectly receive a 65000 error in MDMs

    StatusOriginating updateHistory
    MitigatedN/A

    Last updated: 2023-10-31, 10:06 PT
    Opened: 2023-10-09, 14:51 PT

    Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important: This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

    Workaround: To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured.

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    Affected platforms:

    • ​Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019
    • ​Server: None

    February 2023

    Devices with locale set to Croatia might not utilize the expected currency

    StatusOriginating updateHistory
    ConfirmedN/A

    Last updated: 2023-10-31, 10:06 PT
    Opened: 2023-02-23, 13:22 PT

    The correct default currency might not display or be used in Windows devices which have locale set to Croatia. This can affect applications which retrieve the device's currency for purchases or other transactions. 

    Earlier this year, Croatia joined the Eurozone, changing its currency from the Kuna to Euro. Windows Locale data for Croatia will be updated for this change in the short term.

    Workaround: Changing the currency in Windows can help. This can be accomplished via the Windows Control Panel.

    1. ​Open the "Windows Region" settings. This can be done in one of the following ways:
      1. ​Open "Control Panel" from the start menu and select "Change date, time, or number formats" under "Clock and Region"
      2. ​On your keyboard, press and hold the Windows key, then press the letter R. This will open the "Run" window. Type INTL.CPL into the Open field,
    2. ​In the Region settings, choose one of the 2 locales for Croatia:
      1. Croatian (Bosnia & Herzegovina)
      2. Croatian (Croatia)
    3. ​In this same window, click the "Additional settings" button. Once there, click the "Currency" tab.
    4. ​Change the currency symbol from "KN" to Euro, ""

    Additional information can be seen here: Currency formatting - Globalization | Microsoft Learn.

    Manually changing currency might also be an option in some applications. Although this won't change the device’s default currency, this could allow usage of the application with the desired currency preference. Some applications might not allow this manual change. Please view the settings and documentation for your applications.

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    Affected platforms:

    • ​Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2; 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, version 1809; Windows Server 2019; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Report a problem with Windows updates

    To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.

    Need help with Windows updates?

    Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.

    For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.

    View this site in your language

    This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.