Resolved issues in Windows 11, version 21H2

See a list of known issues that have been resolved for Windows 11, 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
KB5017383
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 22000.778
KB5014668
2022-06-23
Resolved
KB5017383
2022-09-20
10:00 PT
Voice typing might fail to open
When using Windows key + h to open voice typing, you might receive an error.
N/A

Resolved
2022-09-13
16:52 PT
Unable to sign in after adding a new Microsoft Account user in Windows
A newly added Microsoft account user might be unable to sign in after restarting or logging off.
OS Build 22000.918
KB5016691
2022-08-25
Resolved
2022-09-07
13:56 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 22000.708
KB5014019
2022-05-24
Resolved
KB5016691
2022-08-25
14:00 PT
Start menu might not open
A small number of devices are unable to open the Start menu after installing updates released June 23, 2022 or later.
OS Build 22000.778
KB5014668
2022-06-23
Resolved
KB5016629
2022-08-09
10:00 PT
Some .NET Framework 3.5 apps might have issues
Apps using optional components such as Windows Communication Foundation (WCF) and Windows Workflow (WWF) might fail.
OS Build 22000.652
KB5012643
2022-04-25
Resolved
2022-07-19
13:54 PT
PowerShell Desired State Configuration resources might fail to apply successfully
DSC resources in environments which require the PSCredential property might fail.
OS Build 22000.739
KB5014697
2022-06-14
Resolved
KB5015814
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 22000.739
KB5014697
2022-06-14
Resolved
KB5014668
2022-06-23
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 22000.739
KB5014697
2022-06-14
Resolved
KB5016138
2022-06-20
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 22000.675
KB5013943
2022-05-10
Resolved
2022-05-27
14:24 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 22000.652
KB5012643
2022-04-25
Resolved
KB5014019
2022-05-24
14:00 PT
Devices might experience display issues when entering Safe Mode
Components that rely on Explorer.exe can appear unstable when running in Safe Mode without Networking
OS Build 22000.652
KB5012643
2022-04-25
Resolved
KB5013943
2022-05-10
10:00 PT
IE11 data might not be accessible after upgrading to Windows 11
User data in IE11 which was not already imported into Microsoft Edge before upgrading might not be available.
N/A

Resolved
2022-04-04
15:42 PT

Issue details

September 2022

Possible issues caused by new Daylight Savings Time in Chile

StatusOriginating updateHistory
Resolved KB5017383N/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 KB5017383 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 KB5017383. Note: If the workaround above was used, it should have been undone on September 11, 2022. Installation of KB5017383 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

Voice typing might fail to open

StatusOriginating updateHistory
ResolvedN/A

Resolved: 2022-09-13, 16:52 PT
Opened: 2022-09-13, 16:38 PT

When attempting to open voice typing by using the keyboard shortcut of Windows key + h, you might receive the error "Something went wrong." If this error is received, voice typing will not open.

Resolution: This issue has been resolved with a server-side change. Voice typing should now open and function as expected.

Affected platforms:

  • ​Client: Windows 11, version 21H2
  • ​Server: None

Unable to sign in after adding a new Microsoft Account user in Windows

StatusOriginating updateHistory
ResolvedOS Build 22000.918
KB5016691
2022-08-25
Resolved: 2022-09-07, 13:56 PT
Opened: 2022-09-07, 13:56 PT

After installing KB5016691 and adding a new Microsoft account user in Windows, you might be unable to sign in for a brief time after the first restart or sign out. The issue only affects the newly added Microsoft account user and only for the first sign in.

This issue only affects devices after adding a Microsoft account. It does not affect Active Directory domain users accounts or Azure Active Directory accounts.

Workaround: If you encounter this issue, it will automatically resolve itself after a brief time. You will need to wait for the lock screen to appear again, you should be able to login as expected.

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 Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> KB5016691 220722_051525 Known Issue Rollback -> Windows 11 (original release).

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
  • ​Server: None

August 2022

XPS documents with non-English language characters might not open

StatusOriginating updateHistory
Resolved KB5017383OS Build 22000.778
KB5014668
2022-06-23
Resolved: 2022-09-20, 10:00 PT
Opened: 2022-08-08, 17:58 PT

After installing KB5014668 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 KB5017383.

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

Start menu might not open

StatusOriginating updateHistory
Resolved KB5016629OS Build 22000.778
KB5014668
2022-06-23
Resolved: 2022-08-09, 10:00 PT
Opened: 2022-07-22, 15:33 PT

After installing KB5014668 or later updates, we have received reports that a small number of devices might be unable to open the Start menu. On affected devices, clicking or selecting the Start button, or using the Windows key on your keyboard might have no effect.

Resolution: This issue was resolved in updates released August 9, 2022 ( KB5016629) 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 9, 2022 ( KB5016629) 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 -> KB5014668 220721_04201 Known Issue Rollback -> Windows 11 (original release). 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
  • ​Server: None

PowerShell Desired State Configuration resources might fail to apply successfully

StatusOriginating updateHistory
Resolved KB5015814OS Build 22000.739
KB5014697
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 ( KB5014697), 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 KB5015814.

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 KB5016691OS Build 22000.708
KB5014019
2022-05-24
Resolved: 2022-08-25, 14:00 PT
Opened: 2022-06-24, 19:21 PT

After installing KB5014019 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 25, 2022 ( KB5016691) 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 25, 2022 ( KB5016691) 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 25, 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 KB5014668OS Build 22000.739
KB5014697
2022-06-14
Resolved: 2022-06-23, 14:00 PT
Opened: 2022-06-16, 14:12 PT

After installing KB5014697, 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 KB5014668.

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 KB5016138OS Build 22000.739
KB5014697
2022-06-14
Resolved: 2022-06-20, 14:00 PT
Opened: 2022-06-17, 09:56 PT

After installing KB5014697 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 KB5016138, 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 KB5016138, 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

Some .NET Framework 3.5 apps might have issues

StatusOriginating updateHistory
ResolvedOS Build 22000.652
KB5012643
2022-04-25
Resolved: 2022-07-19, 13:54 PT
Opened: 2022-05-03, 13:20 PT

After installing KB5012643, some .NET Framework 3.5 apps might have issues or might fail to open. Affected apps are using certain optional components in .NET Framework 3.5, such as Windows Communication Foundation (WCF) and Windows Workflow (WWF) components.

Workaround: You can mitigate this issue by re-enabling .NET Framework 3.5 and the Windows Communication Foundation in Windows Features. For instructions, please see Enable the .NET Framework 3.5 in Control Panel. Advanced users or IT admins can do this programmatically using an elevated Command Prompt (run as administrator) and running the following commands:

dism /online /enable-feature /featurename:netfx3 /all
dism /online /enable-feature /featurename:WCF-HTTP-Activation
dism /online /enable-feature /featurename:WCF-NonHTTP-Activation

Resolution: This issue should be resolved automatically via a Troubleshooter on affected unmanaged devices. If your device is managed by an IT department or with enterprise management tools, you might not get the troubleshooter automatically and might require the above workaround to resolve the issue. For more information on this troubleshooter, please see Windows Update Troubleshooter for repairing .NET Framework components.

Affected platforms:

  • ​Client: Windows 11, version 21H2
  • ​Server: None

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

StatusOriginating updateHistory
ResolvedOS Build 22000.675
KB5013943
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

Some apps using Direct3D 9 might have issues on certain GPUs

StatusOriginating updateHistory
Resolved KB5014019OS Build 22000.652
KB5012643
2022-04-25
Resolved: 2022-05-24, 14:00 PT
Opened: 2022-05-10, 09:41 PT

After installing KB5012643, 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 May 24, 2022 ( KB5014019) 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 May 24, 2022 ( KB5014019) 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 May 24, 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

April 2022

Devices might experience display issues when entering Safe Mode

StatusOriginating updateHistory
Resolved KB5013943OS Build 22000.652
KB5012643
2022-04-25
Resolved: 2022-05-10, 10:00 PT
Opened: 2022-04-29, 15:07 PT

After installing KB5012643, devices starting in Safe Mode might show a flickering screen. Components that rely on Explorer.exe, such as File Explorer, Start Menu, and Taskbar, can be affected and appear unstable.

Devices experiencing this issue can log a System error on the Windows Event Log, with Source “Winlogon” and the following description: “The shell stopped unexpectedly and explorer.exe was restarted”.

Workaround: This issue happens when the device is started using the “Safe Mode without Networking” option. If Safe Mode needs to be engaged, please select “Safe Mode with Networking” option as a workaround. Please refer to this document for more details on how to start your device in Safe Mode with Networking: Start your PC in safe mode in Windows (microsoft.com)

Resolution: This issue was resolved in updates released May 10, 2022, and later. We recommend you install the latest security update for your device as it contains important improvements and issues resolutions, including this one. If you install an update released May 10, 2022 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 May 10, 2022, you can resolve this issue using KIR. Enterprise-managed devices that have installed an affected update and encountered this issue 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.

Affected platforms:

  • ​Client: Windows 11, version 21H2
  • ​Server: None

March 2022

IE11 data might not be accessible after upgrading to Windows 11

StatusOriginating updateHistory
ResolvedN/A

Resolved: 2022-04-04, 15:42 PT
Opened: 2022-03-31, 16:01 PT

After upgrading to Windows 11, saved information and data from Internet Explorer 11 (IE11) might not be accessible if you did not accept to import it into Microsoft Edge before the upgrade. Note: If you have accepted to import your IE11 information and data into Microsoft Edge in Windows 10 before upgrading to Windows 11, your device should not be affected by this issue.

To safeguard your upgrade experience, we have applied a compatibility hold on devices affected by this issue to prevent them from installing or being offered Windows 11. Affected devices are those in which IE11 is the primary browser used or IE11 is set as the default browser. If your organization is using Update Compliance, the safeguard ID is 37820326.

Resolution: This issue was resolved in Microsoft Edge 99.0 for devices upgrading to Windows 11 and devices that have already upgraded to Windows 11. The safeguard hold has been removed as of March 31, 2022 for devices which have updated to Microsoft Edge 99.0 and later. If you would like to verify your version of Microsoft Edge or check for updates, follow the "Update once" section in Microsoft Edge update settings. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 11, version 21H2 is offered. 

Affected platforms:

  • ​Client: Windows 11, version 21H2
  • ​Server: None