Resolved issues in Windows 10, version 21H2

See a list of known issues that have been resolved for Windows 10, version 21H2 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.


Resolved issues

SummaryOriginating updateStatusDate resolved
Possible issues caused by new Daylight Savings Time in Chile
Chilean government announced a Daylight Saving Time (DST) change for 2022.
N/A

Resolved
KB5017380
2022-09-20
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
Resolved
KB5017380
2022-09-20
10:00 PT
IE mode tabs in Microsoft Edge might stop responding
When a site is viewed in IE mode in Edge and the site uses certain calls, all IE mode tabs might stop responding.
OS Build 19044.1741
KB5014023
2022-06-02
Resolved
KB5016688
2022-08-26
14:00 PT
Audio might stop working
Some Windows devices might have no audio after installing updates released August 9, 2022.
OS Build 19044.1865
KB5015878
2022-07-26
Resolved
2022-08-19
19:46 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
Resolved
KB5016616
2022-08-09
10:00 PT
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
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
Unable to connect to internet when using Wi-Fi hotspot feature
After installing updates released June 14, 2022, you might have issues using Wi-Fi hotspot on Windows device.
OS Build 19044.1766
KB5014699
2022-06-14
Resolved
KB5014666
2022-06-28
14:00 PT
Microsoft Store apps might fail to install on some Windows devices
You might receive Error code: 0xC002001B when attempting to install apps from the Microsoft Store.
OS Build 19044.1682
KB5011831
2022-04-25
Resolved
KB5014023
2022-06-02
14:00 PT
Azure Active Directory and Microsoft 365 services might be unable to sign in
Windows Arm-based devices might have issues signing into some services after installing updates released June 14, 2022
OS Build 19044.1766
KB5014699
2022-06-14
Resolved
KB5016139
2022-06-20
14:00 PT
Some apps using Direct3D 9 might have issues on certain GPUs
You might have intermittent issues, apps might close unexpectedly, or you might receive an error.
OS Build 19044.1682
KB5011831
2022-04-25
Resolved
KB5014023
2022-06-02
14:00 PT
You might see authentication failures on the server or client for services
Network Policy Server (NPS), Routing and Remote access Service (RRAS), Radius, and other services might fail.
OS Build 19044.1706
KB5013942
2022-05-10
Resolved
2022-05-27
14:24 PT
Some apps might render images outside the app's window or expected location
Apps using WebView2 to display content might render incorrectly, with some content rendering outside the app's window.
OS Build 19044.1620
KB5011543
2022-03-22
Resolved
2022-04-04
15:51 PT

Issue details

September 2022

Possible issues caused by new Daylight Savings Time in Chile

StatusOriginating updateHistory
Resolved KB5017380N/A

Resolved: 2022-09-20, 10:00 PT
Opened: 2022-09-02, 13:17 PT

Starting at 12:00 a.m. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by Chilean government about a Daylight Saving Time (DST) time zone change. This moves the DST change which was previously September 4 to September 10.

Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022:

  • ​Time shown in Windows and apps will not be correct.
  • ​Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off.
  • ​Automation using date and time, such as Scheduled tasks, might not run at the expected time.
  • ​Timestamp on transactions, files, and logs will be 60 minutes off.
  • ​Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources.
  • ​Windows devices and apps outside of Chile might also be affected if they are connecting to servers or devices in Chile or if they are scheduling or attending meetings taking place in Chile from another location or time zone. Windows devices outside of Chile should not use the workaround, as it would change their local time on the device.

Workaround: This issue is now resolved in KB5017380 but you should undo the workaround, if it is still being used.

You can mitigate this issue on devices in Chile by doing either of the following on September 4, 2022 and undoing on September 11, 2022:

  • ​Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to Off.
  • ​Go to Control Panel Clock and Region Date and Time Change time zone and uncheck the option for “Automatically adjust clock for Daylight Saving Time”.

To mitigate this issue in the Santiago time zone, after 12:00 a.m. on September 11, 2022, and for those in the Easter Islands time zone, after 10:00 p.m. on September 10, 2022, follow the steps below to re-enable automatic DST adjustments and ensure accurate time switching with future DST transitions. This can be done by doing either of the following:

  • ​Select the Windows logo key, type "Date and time", and select Date and time settings. From the Date & time settings page, toggle Adjust for daylight saving time automatically to On.
  • ​Go to Control Panel Clock and Region Date and Time Change time zone and check the option for “Automatically adjust clock for Daylight Saving Time”.

Important: We recommend using ONLY the above workaround to mitigate the issue with time created by the new Daylight Savings Time in Chile. We do NOT recommend using any other workaround, as they can create inconsistent results and might create serious issues if not done correctly.

Resolution: This issue was resolved in KB5017380. Note: If the workaround above was used, it should have been undone on September 11, 2022. Installation of KB5017380 will not change the "Automatically adjust clock for Daylight Saving Time" setting.

Affected platforms:

  • ​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

August 2022

XPS documents with non-English language characters might not open

StatusOriginating updateHistory
Resolved KB5017380OS Build 19044.1806
KB5014666
2022-06-28
Resolved: 2022-09-20, 10:00 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.

Resolution: This issue was resolved in KB5017380.

Affected platforms:

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

Audio might stop working

StatusOriginating updateHistory
ResolvedOS Build 19044.1865
KB5015878
2022-07-26
Resolved: 2022-08-19, 19:46 PT
Opened: 2022-08-19, 19:36 PT

After installing KB5015878 or later updates, some Windows devices might have issues with audio not working. Some affected Windows devices might have no audio, but other affected Windows devices might only have issues on certain ports, certain audio devices or only within certain applications. Most affected audio devices drivers have the "audio enhancements" setting disabled before installing KB5015878 or the sound device driver has issues with the "audio enhancements" feature.

Workaround: This issue can be mitigated differently depending on your symptoms and if you have installed the update already.

If you have not yet installed the update, you can do the following to prevent the issue:

  • ​Updating your audio device driver (also called "sound drivers" or "sound card drivers") might prevent this issue. If there are updated drivers available on Windows Update or from your Windows device manufacturer's (OEM) webpage, installing them might prevent this issue.
  • ​If you are using any advanced audio applications such as Open Broadcaster Software (OBS), it is recommended that you backup all your settings before installing the update.

If only certain apps are impacted, you can try the following to mitigate the issue:

  • ​Verify that the audio devices set within those apps are the expected devices. Audio endpoints might be reinitialized after KB5015878 is installed and some apps might set the audio devices for microphone and speakers to default.
  • ​If the device settings within the app are as expected, the apps might be caching the Windows Multimedia Device (MMDevice) ID. Caching the MMDevice ID is not recommended and might require reinstallation of the affected app or contacting support for the developer of the app for how to resolve the issue when audio endpoints are reinitialized and have new MMDevice IDs.

If you have already installed the update and are experiencing issues with audio on all apps, you can try the following to mitigate the issue:

  1. ​The Windows audio or sound troubleshooter might be able to resolve the issue for you. You can launch the troubleshooter from Fix sound or audio problems in Windows by selecting the Open Get Help button in the article. The Get Help dialog window should open, and you will need to select yes to open the troubleshooter.
  2. ​If your device's audio is still not working as expected, follow the instructions in Disable Audio Enhancements. Note: The article uses the microphone as an example, but you will need to do the steps for any affected audio device.

Resolution: This issue is resolved using Known Issue Rollback (KIR). Note: This KIR will prevent the issue on Windows devices which have not installed KB5015878 but will have no effect on devices already affected by this known issue. 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 can resolve it by installing and configuring a special Group Policy. 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 Policy, 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.

Affected platforms:

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

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

July 2022

Printing to USB-connected printers might fail

StatusOriginating updateHistory
Resolved KB5016616OS Build 19044.1806
KB5014666
2022-06-28
Resolved: 2022-08-09, 10:00 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 

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.

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

June 2022

IE mode tabs in Microsoft Edge might stop responding

StatusOriginating updateHistory
Resolved KB5016688OS Build 19044.1741
KB5014023
2022-06-02
Resolved: 2022-08-26, 14:00 PT
Opened: 2022-06-24, 19:21 PT

After installing KB5014023 and later updates, IE mode tabs in Microsoft Edge might stop responding when a site displays a modal dialog box. A modal dialog box is a form or dialog box which requires the user to respond before continuing or interacting with other portions of the webpage or app. Developer Note: Sites affected by this issue call window.focus.

Resolution: This issue was resolved in updates released August 26, 2022 ( KB5016688) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one. If you install an update released August 26, 2022 ( KB5016688) 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 26, 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 in below list>. For information on deploying and configuring these special Group Policy, 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.

Affected platforms:

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

Unable to connect to internet when using Wi-Fi hotspot feature

StatusOriginating updateHistory
Resolved KB5014666OS Build 19044.1766
KB5014699
2022-06-14
Resolved: 2022-06-28, 14:00 PT
Opened: 2022-06-16, 14:12 PT

After installing KB5014699, Windows devices might be unable to use the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the internet after a client device connects.

Workaround: To mitigate the issue and restore internet access on the host device, you can disable the Wi-Fi hotspot feature. For instructions, please see Use your Windows PC as a mobile hotspot.

Resolution: This issue was resolved in KB5014666.

Affected platforms:

  • ​​Client: Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • ​​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Azure Active Directory and Microsoft 365 services might be unable to sign in

StatusOriginating updateHistory
Resolved KB5016139OS Build 19044.1766
KB5014699
2022-06-14
Resolved: 2022-06-20, 14:00 PT
Opened: 2022-06-17, 09:56 PT

After installing KB5014699 on a Windows Arm-based devices, you might be unable to sign in using Azure Active Directory (AAD). Apps and services which use Azure Active Directory to sign in, might also be affected. Some scenarios which might be affected are VPN connections, Microsoft Teams, OneDrive, and Outlook. Note: This issue only affects Windows devices which are using Arm processors.

Workaround: To mitigate the issue, you can use the web versions of the affected apps, such as OneDrive, Microsoft Teams and Outlook.com.

Resolution: This issue was resolved in the out-of-band security update KB5016139, released June 20, 2022. This update is available only for Arm-based Windows devices. This update is not needed for x86-based or x64-based devices using AMD or Intel CPUs, so it is not available for those architectures. It is available via Windows Update, Windows Update for Business, Windows Server Update Services (WSUS) and Microsoft Update Catalog. 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 before it is installed automatically, you will need to Check for updates. To get the standalone package for KB5016139, search for it in the Microsoft Update Catalog.

Affected platforms:

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

May 2022

Microsoft Store apps might fail to install on some Windows devices

StatusOriginating updateHistory
Resolved KB5014023OS Build 19044.1682
KB5011831
2022-04-25
Resolved: 2022-06-02, 14:00 PT
Opened: 2022-05-19, 12:53 PT

After installing KB5011831 or later updates, you might receive an error code: 0xC002001B when attempting to install from the Microsoft Store. Some Microsoft Store apps might also fail to open. Affected Windows devices use a processor (CPU) which supports Control-flow Enforcement Technology (CET), such as such as 11th Gen and later Intel® Core™ Processors or later and certain AMD processors.

This issue can also affect devices registered in the Autopilot deployment process, which is commonly used to deploy and maintain devices in corporate environments. Profiles can fail to be applied to the device, resulting in settings not being configured correctly.

Resolution: This issue was resolved in updates released June 2, 2022 ( KB5014023) and later. We recommend you install the latest security update for your device.

Affected platforms:

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

Some apps using Direct3D 9 might have issues on certain GPUs

StatusOriginating updateHistory
Resolved KB5014023OS Build 19044.1682
KB5011831
2022-04-25
Resolved: 2022-06-02, 14:00 PT
Opened: 2022-05-10, 09:41 PT

After installing KB5011831, Windows devices using certain GPUs might have apps close unexpectedly or intermittent issues with some apps which use Direct3D 9. You might also receive an error in Event Log in Windows Logs/Applications with faulting module d3d9on12.dll and exception code 0xc0000094.

Resolution: This issue was resolved in updates released June 2, 2022 ( KB5014023) 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 June 2, 2022 ( KB5014023) 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 June 2, 2022, and have this issue, you can resolve it by installing and configuring the special Group Policy 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 Group Policies to resolve this issue. Please see, How to use Group Policy to deploy a Known Issue Rollback.

Affected platforms:

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

You might see authentication failures on the server or client for services

StatusOriginating updateHistory
ResolvedOS Build 19044.1706
KB5013942
2022-05-10
Resolved: 2022-05-27, 14:24 PT
Opened: 2022-05-11, 18:38 PT

Resolution guidance updated May 27, 2022

After installing updates released May 10, 2022 on your domain controllers, you might see machine certificate authentication failures on the server or client for services such as Network Policy Server (NPS), Routing and Remote access Service (RRAS), Radius, Extensible Authentication Protocol (EAP), and Protected Extensible Authentication Protocol (PEAP). An issue has been found related to how the mapping of certificates to machine accounts is being handled by the domain controller.

Note: Installation of updates released May 10, 2022, on client Windows devices and non-domain controller Windows Servers will not cause this issue. This issue only affects installation of May 10, 2022, updates installed on servers used as domain controllers.

Workaround: The preferred mitigation for this issue is to manually map certificates to a machine account in Active Directory. For instructions, please see Certificate Mapping. Note: The instructions are the same for mapping certificates to user or machine accounts in Active Directory. If the preferred mitigation will not work in your environment, please see KB5014754—Certificate-based authentication changes on Windows domain controllers for other possible mitigations in the SChannel registry key section. Note: Any other mitigation except the preferred mitigations might lower or disable security hardening.

Resolution: This issue was resolved in out-of-band updates released May 19, 2022 for installation on all Domain Controllers in your environment, as well as all intermediary application servers such as Network Policy Servers (NPS), RADIUS, Certification Authority (CA), or web servers which passes the authentication certificate from the client being authenticated to the authenticating DC. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them. This includes the removal of the registry key (CertificateMappingMethods = 0x1F) documented in the SChannel registry key section of KB5014754. There is no action needed on the client side to resolve this authentication issue.

To get the standalone package for these out-of-band updates, search for the KB number in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note The below updates are not available from Windows Update and will not install automatically.

Cumulative updates:

Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released May 10, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

Standalone Updates:

Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of May 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released May 10, 2022 to receive the quality updates for May 2022. If you have already installed updates released May 10, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

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; Windows 8.1; Windows 7 SP1
  • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

April 2022

Some apps might render images outside the app's window or expected location

StatusOriginating updateHistory
ResolvedOS Build 19044.1620
KB5011543
2022-03-22
Resolved: 2022-04-04, 15:51 PT
Opened: 2022-04-04, 12:03 PT

After installing KB5011543, some apps might render content incorrectly or outside of the app's window. Affected apps are using WebView2 to render content generated locally or downloaded from the internet.

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 can resolve it by installing and configuring a special Group Policies listed below. Important Verify that you are using the correct Group Policy for your version of Windows.

Group Policy downloads with Group Policy name:

Important: You will need to install and configure the Group Policies specific to your version of Windows to resolve this issue.

To configure the special Group Policy use the following steps:

  1. ​If the KIR Group Policy has not been installed, install it from the link above.
  2. ​Open Group Policy Editor, navigate to either Local Computer Policy or the Domain policy on your domain controller then: Administrative Templates -> <Name as listed above>, then select the version of Windows you want to use this group policy on. Note: You might need to select the Windows 10 version that use the same update as a version of Server you are using. For example, you might need to select Windows 10, version 1809 if you are using Windows Server 2019.
  3. ​Set it to, "Disabled".
  4. ​If you are setting this on a domain controller, you will need to wait for the Group Policy to replicate group policy changes in Active Directory and the SYSVOL.
  5. ​Devices applying a KIR GP in local or domain policy must either apply a background or manual group policy refresh.
  6. ​Restart the affected device. Note: You should not need to restart the domain controller after installing this KIR Group Policy.
  7. ​Allow Group Policy to refresh on affected devices before installing the affected Windows update.

For information on deploying and configuring these special Group Policies, please see How to use Group Policy to deploy a Known Issue Rollback.

Affected platforms:

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