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 April 15, 2022 (PT)

Windows 10, version 21H2 is designated for broad deployment. As always, we recommend that you update your devices to the latest version of Windows 10 as soon as possible to ensure that you can take advantage of the latest features and advanced protections from the latest security threats. For more details, see How to get the Windows 10 November 2021 Update.

If you are using Windows 10 and want to move to Windows 11, you can check if your device is eligible for the upgrade using the PC Health Check app or checking Windows 11 specs, features, and computer requirements. Note that you also need to be running Windows 10, version 2004 or later, have no safeguard holds applied to your device, and have a Microsoft Account (MSA) if using Home edition.

For more information on the Windows 11 upgrade experience, watch our video, Windows 11 Upgrade Experience.

    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
    Input Indicator and Language Bar might not appear in the notification area
    On devices with more than one language installed, the Input Indicator and Language Bar might not show as expected.
    OS Build 19044.1806
    KB5014666
    2022-06-28
    Resolved
    KB5016616
    2022-08-09
    10:00 PT
    XPS documents with non-English language characters might not open
    XPS Viewer might be unable to open files with some non-English languages, including Japanese and Chinese.
    OS Build 19044.1806
    KB5014666
    2022-06-28
    Confirmed
    2022-08-08
    18:08 PT
    Printing to USB-connected printers might fail
    Updates released after June 28 might cause printing to fail on previously-connected USB printers
    OS Build 19044.1806
    KB5014666
    2022-06-28
    Confirmed
    2022-07-22
    18:04 PT
    PowerShell Desired State Configuration resources might fail to apply successfully
    DSC resources in environments which require the PSCredential property might fail.
    OS Build 19044.1766
    KB5014699
    2022-06-14
    Resolved
    KB5015807
    2022-07-12
    10:00 PT

    Issue details

    August 2022

    Input Indicator and Language Bar might not appear in the notification area

    StatusOriginating updateHistory
    Resolved KB5016616OS Build 19044.1806
    KB5014666
    2022-06-28
    Resolved: 2022-08-09, 10:00 PT
    Opened: 2022-08-02, 17:38 PT

    After installing updates released on June 28, 2022 ( KB5014666) or later updates, the Input Indicator and Language Bar might not appear in the notification area. The notification area is normally located on the right end of the taskbar. Affected devices have more than one language installed. The Input Indicator and Language Bar is used to switch between input or keyboard languages on Windows devices and is used especially with languages that use Input Method Editors (IME).

    Resolution: This issue was resolved in updates released August 9, 2022 ( KB5016616) and later. We recommend you install the latest security update for your device. It contains important improvements and issues resolutions, including this one. If you install an update released August 9, 2022 ( KB5016616) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before August 9, 2022, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> <Group Policy name listed below>. For information on deploying and configuring these special Group Policies, please see How to use Group Policy to deploy a Known Issue Rollback.

    Group Policy downloads with Group Policy name:

    Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue on updates released before August 9, 2022.

    Affected platforms:

    • ​Client: Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
    • ​Server: Windows Server, version 20H2

    XPS documents with non-English language characters might not open

    StatusOriginating updateHistory
    ConfirmedOS Build 19044.1806
    KB5014666
    2022-06-28
    Last updated: 2022-08-08, 18:08 PT
    Opened: 2022-08-08, 17:58 PT

    After installing KB5014666 or later updates, XPS Viewer might be unable to open XML Paper Specification (XPS) documents in some non-English languages, including some Japanese and Chinese character encodings. This issue affects both XML Paper Specification (XPS) and Open XML Paper Specification (OXPS) files. When encountering this issue, you may receive an error, "This page cannot be displayed" within XPS Viewer or it might stop responding and have high CPU usage with continually increasing memory usage. When the error is encountered, if XPS Viewer is not closed it might reach up to 2.5GB of memory usage before closing unexpectedly.

    This issue does not affect most home users. The XPS Viewer is no longer installed by default as of Windows 10, version 1803 and must be manually installed.

    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 21H2; Windows 10, version 21H1; Windows 10, version 20H2
    • ​Server: Windows Server, version 20H2

    July 2022

    Printing to USB-connected printers might fail

    StatusOriginating updateHistory
    ConfirmedOS Build 19044.1806
    KB5014666
    2022-06-28
    Last updated: 2022-07-22, 18:04 PT
    Opened: 2022-07-22, 17:53 PT

    Microsoft has received reports of issues affecting some printing devices following installation of Windows updates released June 28 ( KB5014666) and later. Symptoms observed may include:

    • ​Windows might show duplicate copies of printers installed on a device, commonly with a similar name and the suffix "Copy1".
    • ​Applications that refer to the printer by a specific name cannot print.

    Normal printer usage might be interrupted for either scenario, resulting in failure of printing operations.

    If you are experiencing issues, please use feedback hub to file a report following the below steps:

    1. ​Launch Feedback Hub by opening the Start menu and typing "Feedback hub", or pressing the Windows key + F
    2. ​Fill in the "Summarize your feedback" and "Explain in more detail" boxes, then click Next.
    3. ​Under the "Choose a category" section, ensure the "Problem" button, "Devices and Drivers" category, and "Print" subcategory are all selected. Click Next.
    4. ​Under the "Find similar feedback" section, select the "Make new bug" radio button and click Next.
    5. ​Under the "Add more details" section, supply any relevant detail (Note this is not critical to addressing your issue).
    6. ​Expand the "Recreate my problem" box and press "Start recording". Reproduce the issue on your device.
    7. ​Press "Stop recording" once finished. Click the "Submit" button.

    For additional information, see Send feedback to Microsoft with the Feedback Hub app.

    Workaround: Here are some actions you can take, which might help resolve this issue:

    • ​Open the Settings app, navigate to “Bluetooth & devices”, and select “Printers & scanners”
    • ​If there appears to be a duplicate installation of an existing printer, such as with suffix "Copy1", confirm if printing works for this printer. This printer should operate as expected.
    • ​If there is a need to use the original printer installation and not the duplicate, right-click the duplicate printer, select "Printer properties" and select the "Ports" tab. Observe the port in use.
    • ​Open "Printer properties" on the original printer and select the "Ports" tab. From the list displayed, select the port option in use by the duplicate printer. If this original printer works normally, the duplicate copy printer can be removed. 

    If the issue persists, the following steps can be attempted:

    • ​Update the print driver for your device. For guidance, see Install the latest driver for your printer
      • ​If you already have the latest driver, consult the printer Manufacturer’s web site for any device firmware updates
    • ​If you are still having issues, uninstalling and reinstalling your printer might help.
      • ​Turn off your printer and disconnect any cables
      • ​Open the Settings app, navigate to “Bluetooth & devices”, and select “Printers & scanners”
      • ​Select the affected printer and select the "Remove Device" option
      • ​Restart your device
      • ​Turn on your printer and reconnect it to your device 

    Next steps: We are presently investigating and will provide an update when more information is available.

    Affected platforms:

    • ​Client: Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2
    • ​Server: Windows Server, version 20H2

    PowerShell Desired State Configuration resources might fail to apply successfully

    StatusOriginating updateHistory
    Resolved KB5015807OS Build 19044.1766
    KB5014699
    2022-06-14
    Resolved: 2022-07-12, 10:00 PT
    Opened: 2022-07-19, 17:55 PT

    After installing updates released June 14, 2022, or later ( KB5014699), PowerShell Desired State Configuration (DSC) using an encrypted the PSCredential property might fail when decrypting the credentials on the target node. This failure will result in a password related error message, similar to: “The password supplied to the Desired State Configuration resource <resource name> is not valid. The password cannot be null or empty.”. Note: Environments which use non-encrypted PSCredential properties will not experience the issue.

    DSC is a management platform in PowerShell that enables administrators to manage IT and development infrastructure with configuration as code. This issue is not likely to be experienced by home users of Windows.

    Resolution: This issue was resolved in KB5015807.

    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; Windows 10 Enterprise LTSC 2016
    • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019; Windows Server 2016