Windows 10, version 22H2 known issues and notifications

Find information on known issues and the status of the Windows 10, version 22H2 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. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.

• 

  How to get new experiences for Windows 11

• 

  Get Windows known issues data in Graph API

Known issues

Issue details

November 2025

An incorrect "End of Support" message might appear in Windows Settings

The message, "Your version of Windows has reached the end of support", might incorrectly display in the Windows Update Settings page for the following OS versions:

• ​Windows 10, version 22H2 Pro, Education or Enterprise editions that are correctly enrolled in the Extended Security Updates (ESU) program and configured with an ESU product key
• ​Windows 10 Enterprise LTSC 2021
• ​Windows 10 IoT Enterprise LTSC 2021

The message might occur after installing Windows updates released on or after October 14, 2025 (KB5066791).

This issue only involves the incorrect display of the "end of support" message.

• ​Windows 10 devices that have an activated ESU license will continue to receive security updates.
• ​Windows 10 Enterprise LTSC 2021 and Windows 10 IoT Enterprise LTSC 2021 remain in support and will continue to receive security updates according to their respective lifecycles.

Workaround:

Microsoft pushed a cloud configuration update to correct this issue. However, you might not receive this update if the device:

• ​is not connected to the internet,
• ​has disabled OneSettings downloads through Group Policy,
• ​has restrictive firewall settings,
• ​or otherwise blocks dynamic updates.

If you are still seeing the incorrect "end of support" message, enterprise-managed devices managed by IT departments can resolve the issue using Known Issue Rollback (KIR) by installing and configuring the special Group Policy listed below. 

Group Policy downloads with Group Policy name:  

• ​Download for Windows 10, version 21H2 and 22H2 — KB5066791 251020_20401 Known Issue Rollback

The special Group Policy can be found in Computer Configuration > Administrative Templates > KB5066791 251020_20401 Known Issue Rollback > Windows 10, version 20H2, 21H1, 21H2 and 22H2. For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. 

Important: You will need to install and configure the Group Policy, setting the KB5066791 251020_20401 Known Issue Rollback value to Disabled, to resolve this issue. You will also need to restart your device(s) to apply the group policy setting.

Next Steps: We are working to include the resolution in a future Windows update. Once the update with the resolution is released, organizations will not need to install and configure this Group Policy to address this issue. 

Affected platforms:

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

October 2025

Windows 11 media creation tool might not work as expected on Windows 10

The Windows 11 media creation tool version 26100.6584, released September 29, 2025, might not work as expected when used on Windows 10 devices. The media creation tool might close unexpectedly, displaying no error message.

The media creation tool is used to create a bootable USB or DVD which can be utilized to perform a reinstall or clean install of Windows 11 on a new or used PC. Note that the Windows 11 media creation tool is not currently supported on Windows 10 devices that use Arm64 processors.

Resolution: The Windows 11 media creation tool has been updated to a new version on October 28, 2025. It can be downloaded at https://www.microsoft.com/software-download/windows11. As always, bootable media can also be downloaded directly at this site, under the section titled "Download Windows 11 Disk Image (ISO) for x64 devices".

Affected platforms:

• ​Client: Windows 10, version 22H2
• ​Server: None

Smartcard authentication issues might occur with the October 2025 Windows update

Smart card authentication and other certificate operations might intentionally fail after installing Windows Updates released on or after October 14, 2025 (KB5066791) that contain protections for the security vulnerability, CVE-2024-30098. As part of this cryptography improvement, RSA-based smart card certificates are required to use KSP (Key Storage Provider) instead of CSP (Cryptographic Service Provider).

Common symptoms for certificates that use CSP include:

• ​Smart cards not being recognized as CSP providers (Cryptographic Service Provider) in 32-bit applications
• ​Inability to sign documents
• ​Failures in applications relying on certificate-based authentication
• ​Users might observe error messages such as "invalid provider type specified" and "CryptAcquireCertificatePrivateKey error."

You can detect if your smart card will be affected by this security enforcement if, prior to installing the October 2025 Windows security update (KB5066791), the System log contains Smart Card Service or Microsoft-Windows-Smartcard-Server Event ID: 624 with the message text: "Audit: This system is using CAPI for RSA cryptography operations. Please refer to the following link for more detail: https://go.microsoft.com/fwlink/?linkid=2300823."

Resolution:

For a permanent resolution, developers should update their authenticating app to perform Key Storage Retrieval using Key Storage API documented at Key Storage and Retrieval. Developers should complete this change before Windows updates released in April 2026, at which time the DisableCapiOverrideForRSA workaround listed below is planned to be removed.

Workaround:

If you encounter this issue, you can temporarily resolve it by setting the DisableCapiOverrideForRSA registry key value to 0. This is documented in CVE-2024-30098. Detailed steps to modify the registry key are listed below. Note: This option will be removed in Windows updates, planned for release in April 2026.

Steps to Modify the Registry

⚠️ Important: Editing the registry incorrectly can cause system issues. Always back up the registry before making changes.

1. Open Registry Editor.

• ​Press Win + R, type regedit, and press Enter.
• ​If prompted by User Account Control, click Yes.

2. Navigate to the subkey.

• ​Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais

3. Edit the key and set the value.

• ​Inside Calais, check if key DisableCapiOverrideForRSA exists
• ​Double-click DisableCapiOverrideForRSA.
• ​In Value date, enter: 0

Note: The DisableCapiOverrideForRSA registry setting is NOT added by the default OS install or the installation of Windows Updates and must be manually added on each device.

4. Close and restart.

• ​Close Registry Editor.
• ​Restart the computer for changes to take effect.

Affected platforms:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
• ​Server: Windows Server 2025; Windows Server 23H2; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2

June 2025

Parental consent may not show for some browser versions with web filtering on

Certain laws require Microsoft to protect children from harmful and illegal content on the internet. Microsoft is committed to creating tools for parents and guardians to help them in guiding their children’s digital experiences and protect them from harmful and illegal online content.

One of the available tools is web filtering, which lets a parent or guardian filter websites. Currently, Microsoft Edge is the only supported browser that provides this functionality within Microsoft Family Safety, allowing Edge to be used by default on the child’s device after web filtering is enabled. Once web filtering is enabled, a parent or guardian needs to approve other unsupported browsers (any browser other than Edge) before they can be used. This helps parents understand that different settings apply to other browsers when it comes to blocking inappropriate websites and filtering search results for their children.

The blocking behavior continues to work for unsupported browsers, however, when unsupported browsers update to a new version, the latest version of the browser cannot be blocked until we add it to the block list. Microsoft is currently adding the latest versions of unsupported browsers, to the block list. As a result, some browsers may temporarily appear unblocked during this update process. We're actively working to ensure all latest versions of browsers are blocked, reinforcing our commitment to parents and guardians.

As Microsoft continues to update the block list, we’ve received reports of a new issue affecting Google Chrome and some browsers. When children try to open these browsers, they shut down unexpectedly. However, the standard workflow is to prompt a parental approval message stating, “You’ll need to ask to use this app”. Once the approval is consented, the browser operates as intended. This issue is only observed when the Activity reporting feature is turned off.

Workaround: The browser shutdown issue can be temporarily mitigated by turning on Activity reporting under Windows settings in Family Safety. Parents will then be able to receive approval requests as expected.

Resolution:

• ​Temporary access to unsupported browsers: As of June 25, 2025, Microsoft included the latest versions of unsupported browsers into the Family Safety’s feature, and they are now blocked as intended. However, new versions of unsupported browsers released after this date might temporarily appear unblocked. This temporary gap will be resolved in the future, and this documentation will be updated to inform you when the full resolution is available.
• ​Missing parental consent prompt: Fixed in the July non-security preview update (KB5062649), released July 22, 2025. The fix is gradually rolling out and will be automatically enabled on devices with KB5062649 installed or later updates.

Affected platforms:

• ​Client: Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2
• ​Server: None

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.