Access to this page requires authorization. You can try signing in or changing directories . Access to this page requires authorization. You can try changing directories . Find information on recently resolved issues for Windows 11, version 24H2. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge). 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 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 . Resolved issues Microsoft Teams and Outlook might fail to launch on ARM-based devices Microsoft Teams and Outlook might fail to launch on ARM-based devices After installing Windows security updates released on or after August 11, 2026, ( KB5121003 ), Microsoft Teams and the new Outlook for Windows might fail to launch or might close unexpectedly on ARM-based devices, such as Surface Pro 11 and Surface Laptop 7. Classic Outlook, Word, Excel, and other applications are not known to be affected. This issue is most likely to occur on new or freshly imaged PCs that have not yet installed any Microsoft Store updates. Resolution : This issue was resolved by Windows updates released September 8, 2026 ( KB5124008 ), and updates released after that date. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. If you install an update released September 8, 2026 ( KB5124008 ), or later, you do not need to use a workaround for this issue. If you are using an update released before September 8 and have this issue, you have the option to apply the following workaround. Workaround: To work around this issue: ​Open Microsoft Store . ​Select Downloads > Check for updates. ​Install the latest update for the Auto Super Resolution Package (version 1.0.19.0 or later). Affected platforms: ​Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2 Desktop background settings are lost or reset on some devices Desktop background settings are lost or reset on some devices Following installation of Windows updates released August 27 2026 ( KB5120998 ), some Windows Desktop settings fail to load, resulting in desktop backgrounds displaying as a solid black color. It is possible other desktop settings may be affected, such as slideshow settings or contrast themes. On affected devices, attempting to manually restore customized settings does not work. This is because the issue prevents the correct loading of settings, regardless of their value. In this case, a default black background is used instead. Resolution : This issue was resolved by Windows updates released September 8, 2026 ( KB5124008 ), and later. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one. Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 Mouse customization is reset on non-English Windows devices Mouse customization is reset on non-English Windows devices Following installation of Windows updates released August 27 2026 ( KB5120998 ), mouse personalization settings are being reverted to certain standard settings. This includes cursor and cursor animations that are selected in the Mouse Properties options under Windows. Our investigation indicates that this issue is caused by code components used in non-English Windows installations. In impacted locales, these settings will fail to load, causing a default to be used instead. Attempting to manually restore the settings values is not successful, as the issue prevents loading these settings regardless of their value. Resolution : This issue was resolved by Windows updates released September 8, 2026 ( KB5124008 ), and later. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one. Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 Some games become unresponsive when certain drivers are present Some games become unresponsive when certain drivers are present Following the release of Windows updates on August 11, 2026 ( KB5121003 ) and later, some devices may be unable to run certain games as expected. The games mentioned in reports of this issue are ARC Raiders, MARVEL Tōkon: Fighting Souls, and THE FINALS. Symptoms include: ​the game application becomes unresponsive ​the game application closes without notice ​the error "EXCEPTION_ACCESS_VIOLATION" is displayed ​the device restarts without warning Our investigation confirms that this issue is not caused by Windows updates and is related to peripherals or internal device components which have RGB lighting features. Such devices may install drivers or code components with file names similar to inpoutx64. In systems where these drivers are found, the issue is then triggered by launching certain games. Resolution : This issue is resolved by a block that prevents the inpoutx64 driver from loading. The block targets devices with this specific driver enabled and the game ARC Raiders installed. This resolution disables the inpoutx64 driver and displays a message window with information about the disablement. Following this message, the game will launch as normal. We are working to expand the block to devices with the game MARVEL Tōkon: Fighting Souls. This issue was resolved by Embark Studios for devices running THE FINALS. This resolution is propagating automatically to Windows consumer and business devices that are not managed by IT departments, and a device restart is required. Please note that it might take up to 24 hours starting from August 26, 2026, 6 PM PT for this resolution to reach all affected devices. The driver block will also be included in the September 2026 Windows security updates and subsequent releases. If you have an enterprise-managed device, this resolution will not propagate automatically. IT administrators can address this issue by following the steps mentioned in the workaround section, below. Note that it is safe to apply the workaround in conjunction with the resolution being released, in the event that the workaround below has already been applied to a device prior to receiving the block. Workaround : This issue can be prevented by temporarily disabling the inpoutx64 driver using the Windows registry. Important : This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see How to back up and restore the registry in Windows. Follow these steps to disable the driver via the Windows registry: ​​Navigate to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64 . This can be done using the folders on the left side of the window, or typing the path into the address line at the top of the window. ​​ NOTE: Ensure you have backed up the registry, as per the important note above. It may be necessary if you need to undo the change in the following steps. ​​On the right side of the window, find the registry value named Start . Double click this key and enter the number 4 under the field titled Value data . ​​Close the window and restart your computer. Ongoing investigation does not indicate that disabling this registry key can result in unintended behavior. If you want to re-enable the driver, you may do so by restoring the registry key to its previous value. This can be done following the steps provided at How to back up and restore the registry in Windows . Affected platforms: · Client: Windows 11, version 25H2; Windows 11, version 24H2 Windows Server Update Services sync operations might have issues or time out Windows Server Update Services sync operations might have issues or time out Microsoft has identified a service degradation affecting Windows Server Update Services (WSUS). Organizations might experience increased synchronization times or sync operation timeouts on WSUS servers. This issue began in recent days, with heightened impact observed starting July 13, 2026, and service-side mitigation on Saturday July 18, 2026. After this day, synchronization times and sync operations are expected to be restored to normal. This issue is related to a buildup of publishing metadata which is present on existing WSUS server installations as well as from the service side. Resolution: There are two parts to the resolution of this issue. ​Organizations with existing WSUS server installations that are experiencing long sync times can benefit from manual steps in order to clean up unneeded metadata. This metadata is present in existing WSUS installations but can be safely removed. Detailed guidance has been provided at the following KB article: https://support.microsoft.com/help/5121986 . ​On July 18, 2026, Microsoft deployed a service-side mitigation which returns synchronization times and sync operations back to normal for new WSUS installations and rebuilds. After this date, newly installed or rebuilt WSUS servers should not encounter this issue. Affected platforms: ​Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607 ​Server: Windows Server 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 Some Dell devices with a specific Intel driver might experience poor performance Some Dell devices with a specific Intel driver might experience poor performance After installing the June 23, 2026, Windows non-security preview update ( KB5095093 ), a limited number of Dell devices might display a yellow exclamation point in Device Manager next to the Intel Innovation Platform Framework Processor Participant driver (Intel IPF). In some cases, affected devices might experience changes in performance, power consumption, or system behavior. This issue was identified as an incompatibility between the Intel driver and the new Windows USB-C Connection Manager interface introduced in the June 23, 2026, Windows preview update ( KB5095093 ). To mitigate this issue, the July 14, 2026, Windows security update for Windows 11, version 25H2 and Windows 11, version 24H2 ( KB5101650 ) was temporarily not offered to affected devices while Microsoft worked with partners to resolve this issue. Resolution: This issue is resolved in the out-of-band (OOB) update released on July 18, 2026, ( KB5121767 ), and updates released after this date. This is a cumulative update, so you do not need to apply any previous updates before installing it. Devices that were temporarily prevented from receiving the July 2026 security update will now be offered this OOB update, which includes all improvements from previous security and non-security updates, along with this additional fix. For devices enrolled in hotpatching, this issue is addressed with the hotpatch update KB5121768 . If you have turned on Get the latest updates as soon as they're available in Windows Update settings ( Settings > Windows Update ), you will automatically receive this update. If the toggle is off on your device, you can install the update by going to Settings > Windows Update and selecting Download & Install . Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 GIF functionality in the Windows Emoji Panel might become unavailable GIF functionality in the Windows Emoji Panel might become unavailable Starting on June 30, 2026, you might not see GIF options in the Windows Emoji Panel on some devices and instead see a message stating “GIF service is not available.” This issue occurs because the previous GIF provider (Tenor) retired its service on that date. Resolution: This issue was resolved by Windows updates released June 23, 2026 ( KB5095093 ), and later. These updates include a new GIF provider ( GIPHY ). To restore GIF functionality in the Windows Emoji Panel, install the latest available Windows updates, which contains important improvements and issue resolutions, including this one. Affected platforms: ​Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2 Deleting a file from the Recycle Bin displays an internal filename in the dialog Deleting a file from the Recycle Bin displays an internal filename in the dialog When permanently deleting a single item from the Recycle Bin, the confirmation dialog displays the internal Recycle Bin filename (for example, $Rxxxxx.ext) instead of the original filename. The Recycle Bin itself correctly displays the original filename, and restoring the item also restores it using the original filename. This issue occurs after installing the Windows security update released on June 9, 2026 ( KB5094126 ). Resolution: This issue was resolved by Windows updates released June 23, 2026 ( KB5095093 ), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. If your organization has installed an update released on June 23, 2026, or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. Affected platforms: ​Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 ​Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 May 2026 security update might fail to install with error 0x800f0922 May 2026 security update might fail to install with error 0x800f0922 After installing the May 2026 Windows security update ( KB5089549 ), some devices might experience installation failures with error code 0x800f0922. This issue affects devices with limited free space on the EFI System Partition (ESP), especially when the device has 10 MB or less space available. On affected devices, the installation might proceed through the initial phases but fail during the reboot phase at approximately 35–36% completion. The installation then rolls back with error code, and users might see the message: “Something didn’t go as planned. Undoing changes.” Resulting from this issue, users may observe log entries similar to the following in C:\Windows\Logs\CBS\CBS.log, indicating insufficient free space on the EFI System Partition: ​“SpaceCheck: Insufficient free space” ​“ServicingBootFiles failed. Error = 0x70” ​“SpaceCheck: <value> used by third-party/OEM files outside of Microsoft boot directories” Resolution: This issue was resolved by Windows updates released May 26, 2026 ( KB5089573 ), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. If you install an update released May 26, 2026 ( KB5089573 ) or later, you do not need to use a workaround for this issue. If you are using an update released before this date, and are experiencing this issue, you can use the following workaround. Workaround: Affected customers might apply one of the following workarounds to mitigate the issue: 1. Allow update installation by modifying ESP registry setting ⚠️ Important : Editing the registry incorrectly can cause system issues. Always back up the registry before making changes. ​Open Command Prompt as Administrator ​Run the following command: ​reg add "HKLM\SYSTEM\CurrentControlSet\Control\Bfsvc" /v EspPaddingPercent /t REG_DWORD /d 0 /f ​Restart the affected device to apply the change and then retry installing the update. 2. Mitigate through Known Issue Rollback (KIR) ​ Download for Windows 11, version 25H2 and Windows 11, version 24H2: KB5089549 260514_06221 Known Issue Rollback Affected versions: ​Client: Windows 11, version 25H2; Windows 11, version 24 H2 Microsoft account sign ins might fail for Microsoft Teams Free and other apps Microsoft account sign ins might fail for Microsoft Teams Free and other apps Following installation of Windows updates released March 10, 2026 ( KB5079473 ) sign in with Microsoft accounts might fail for some Microsoft applications, including Microsoft Teams Free or OneDrive. As a result of this issue, sign in attempts will display an error message with text similar to "You'll need the Internet for this. It doesn't look like you're connected to the Internet". This appears even if the device is connected to the internet. Please note that this issue occurs only with sign in operations involving Microsoft accounts, which are commonly used for Microsoft Teams Free. Businesses using Entra ID (previously known as Azure Active Directory) for app authentication will not be affected by this issue. Other applications affected include Microsoft Edge, Excel, Word, and Microsoft 365 Copilot. Whenever a feature in these applications requires Microsoft account sign in, the same message can be encountered. Resolution : This issue was resolved by Windows updates released March 21, 2026 ( KB5085516 ), and later updates. We recommend you install the latest updates for your device as they contain important improvements and issue resolutions, including this one. If you install an update released March 21, 2026 ( KB5085516 ) or later, you do not need to use a workaround for this issue. If you are using an update released before this date, and have this issue, restarting the device while keeping it connected to the internet should prevent the issue from occurring. Please note this issue occurs when the device enters a specific network connectivity state, and may resolve on its own. However, if the device is restarted without an active internet connection, it might return to a connectivity state where the issue can occur again. In such a case, it will be necessary to restart again while keeping internet connectivity, in order to repair the connectivity state. Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 Microsoft received reports of loss of access to the C: drive and app failures Microsoft received reports of loss of access to the C: drive and app failures Microsoft has received reports of an issue in which some Samsung device models lose access to the C: drive after installing the February 2026 security update ( KB5077181 ) and subsequent updates. Users might encounter the error, “ C:\ is not accessible – Access denied ”, which prevents access to files and blocks the launch of some applications including Outlook, Office apps, web browsers, system utilities and Quick Assist. Microsoft and Samsung investigated these reports and concluded that the symptoms were caused by an issue in the Samsung Galaxy Connect app. While the reports coincided with recent March Patch Tuesday timing, investigation confirmed the issue is not caused by current or previous Windows monthly updates. The issue has been observed on Samsung Galaxy Book 4 and Samsung Desktop models running Windows 11, versions 24H2 and 25H2, including NP750XGJ, NP750XGL, NP754XGJ, NP754XFG, NP754XGK, DM500SGA, DM500TDA, DM500TGA, and DM501SGA. Affected devices encounter the issue when users execute common actions, such as accessing files, launching applications, or performing administrative tasks, and do not require any specific user action beyond routine operations. In some cases, users are also unable to elevate privileges, uninstall updates, or collect logs due to permission failures. Resolution: This issue can be resolved on affected devices by following the guidance documented in the Microsoft KB article “ Recovery steps: Samsung Galaxy Connect or Samsung Continuity Service might cause loss of access to the C: drive .” Microsoft and Samsung collaborated to validate these steps, which restore standard Windows permissions. For device-specific assistance, please contact Samsung’s support channels. Note: Mitigations to prevent additional devices from encountering this issue were implemented starting March 14, 2026 (Pacific Time). As part of these mitigations, the affected Samsung Galaxy Connect application was temporarily removed from the Microsoft Store, and Samsung republished a stable previous version of the application to prevent recurrence. Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 Connection and authentication failures in Azure Virtual Desktop and Windows 365 Connection and authentication failures in Azure Virtual Desktop and Windows 365 Updated 2026-01-24: This message was updated to reflect the availability of a new Windows out-of-band update that addresses this issue and is available via the Windows Update release channel. After installing the January 2026 Windows security update ( KB5074109 ), credential prompt failures might occur in some remote connection applications. This includes remote desktop connections using the Windows App on Windows client devices, on Azure Virtual Desktop and Windows 365. The Windows App is affected by this issue on specific Windows builds and can experience sign-in failures. Other remote connections and related applications may be similarly impacted. A new out-of-band (OOB) update was released on January 24, 2026. It can be found as KB5078127 . If you have turned on Get the latest updates as soon as they're available in Windows Update settings ( Settings > Windows Update ), you will automatically receive this update. If the toggle is off on your device, you can install the update manually by going to Settings > Windows Update and selecting Download & install . Note that this update will show up in Windows Update only if you have installed one of the updates released in January that caused this issue. We recommend using Windows Update to install this update. This OOB update is cumulative and includes all protections and improvements from the January 2026 Windows security update released January 13, 2026, and from the OOB update released January 17, 2026. If you have not yet deployed the January 2026 Windows security update and your IT environment includes the affected applications and features, we recommend applying this OOB update instead. As always, we recommend you install the latest update for your device as it contains important improvements and issue resolutions including this one. This issue was originally addressed in an out-of-band (OOB) update released January 17, 2026, in the Microsoft Update Catalog . It can be found as KB5077744 . For additional guidance, see How to download updates from the Microsoft Update Catalog . If the OOB is not installed, one of the following connection options can be used as a temporary workaround: ​Use the Remote Desktop client for Windows to connect to Azure Virtual Desktop here ( /previous-versions/remote-desktop-client/whats-new-windows?tabs=windows-msrdc-msi ) ​Connect using the Windows App Web Client at windows.cloud.microsoft Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2, Windows 10 Enterprise LTSC 2019 ​Server: Windows Server 2025; Windows Server 2022; Windows Server 2019 Apps might become unresponsive when saving files to cloud-backed storage Apps might become unresponsive when saving files to cloud-backed storage After installing Windows updates released on or after January 13, 2026 ( KB5074109 ), some applications might become unresponsive or experience unexpected errors when opening files from or saving files to cloud-backed storage, such as OneDrive or Dropbox. For example, in some configurations of Outlook that store PST files on OneDrive, Outlook might become unresponsive and fail to reopen unless its process is terminated in Task Manager, or the system is restarted. In addition, sent emails might not appear in the Sent Items folder, and previously downloaded emails might be downloaded again. The affected Outlook configurations primarily involve classic Outlook, which is commonly tied to enterprise licensing and is not included with most home installations of Windows. To check your Outlook configuration, see Feature comparison between new Outlook and classic Outlook . This issue is resolved in the out-of-band (OOB) update released on January 24, 2026, ( KB5078127 ), and updates released after this date. If you have turned on Get the latest updates as soon as they're available in Windows Update settings ( Settings > Windows Update ), you will automatically receive this update. If the toggle is off on your device, you can install the update manually by going to Settings > Windows Update and selecting Download & Install . Note that this update will show up in Windows Update only if you have installed one of the updates released in January that caused this issue. We recommend installing the latest update for your device, as it contains important improvements and issue resolutions, including this one. For devices that have not yet installed the OOB update, there is an optional workaround for Outlook-specific scenarios. Moving the Outlook PST files out of OneDrive should resolve this issue. For guidance, please see documentation at How to remove an Outlook .pst data file from OneDrive . In addition, email accounts can still be accessed via webmail, if supported by your email provider. Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019 ​Server: Windows Server 2025; Windows Server, version 23H2; Windows Server 2022; Windows Server 2019 Task Manager process might continue to run in background after app is closed Task Manager process might continue to run in background after app is closed After installing Windows Updates released on or after October 28, 2025 ( KB5067036 ), you might encounter an issue where closing Task Manager using the Close (X) button does not fully terminate the process. When you reopen Task Manager, the previous instance continues running in the background even though no window is visible. This results in multiple lingering instances of taskmgr.exe, consuming system resources and potentially degrading device performance. Additional instances appear as “Task Manager” in the Processes tab and as “Taskmgr.exe” in the Details tab. Although the impact is less if Task Manager is opened and closed a few times, many instances accumulated over time can cause noticeable slowdowns in other applications. This issue is resolved in the November Windows security update ( KB5068861 ) and later updates. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. If you have installed Windows updates released before November 11, 2025, you can use the following workaround. Workaround: You can mitigate the issue by following one of the steps below: ​When closing Task Manager, instead of closing it with the 'X' button, use End Task on the Task Manager process itself. This can be done by going to the Processes tab, selecting the Task Manager process, and clicking End Task . ​To close multiple instances of Task Manager, you can use the command line prompt: ​Click Start (Windows icon) or press the Windows key . ​Type cmd or Command Prompt in the search box. ​Click Command Prompt from the results. ​To run as Administrator: Right-click Command Prompt and select Run as administrator. ​Run the command taskkill.exe /im taskmgr.exe /f and press enter. ​This will close all instances of Task Manager ​Click Start (Windows icon) or press the Windows key . ​Type cmd or Command Prompt in the search box. ​Click Command Prompt from the results. ​To run as Administrator: Right-click Command Prompt and select Run as administrator. ​Run the command taskkill.exe /im taskmgr.exe /f and press enter. ​This will close all instances of Task Manager Affected Versions: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 IIS websites might fail to load IIS websites might fail to load After further investigation, we concluded that this issue was not applicable to Windows Server 2025. It affects only Windows 11, version 25H2 and 24H2. This issue can be disregarded by Windows Server users. To learn about the impact of this issue for Windows 11, select from the links below: ​ Windows 11, version 25H2 ​ Windows 11, version 24H2 The issue mentioned below was published prior to this finding and November 14, 2025 edits: Following installation of Windows updates releases on or after September 29, server-side applications that rely on HTTP.sys may experience issues with incoming connections. As a result, IIS websites might fail to load, displaying a message such as "Connection reset - error (ERR_CONNECTION_RESET)", or similar error. This includes websites hosted on http://localhost/, and other IIS connections.

Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 Smartcard authentication issues might occur with the October 2025 Windows update 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 ( KB5066835 ) 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 ( KB5066835 ), 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 ." 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. 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 USB mouse and keyboard not working in the Windows Recovery Environment (WinRE) USB mouse and keyboard not working in the Windows Recovery Environment (WinRE) After installing the Windows security update released on October 14, 2025 ( KB5066835 ), USB devices, such as keyboards and mice, do not function in the Windows Recovery Environment (WinRE) . This issue prevents navigation of any of the recovery options within WinRE. Note that the USB devices continue to work normally within the Windows operating system. Resolution: This issue was resolved by the Windows out-of-band update, released October 20, 2025 ( KB5070773 ), and updates released after that date. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. Workaround: If your device is impacted by this issue and is unable to boot to Windows to install the latest Windows update, you can work around this issue using one of the following methods: ​If your PC has a touchscreen, you can use the touchscreen's touch keyboard to navigate within WinRE. ​If your PC has a PS/2 port, you can use a PS/2 keyboard or mouse to navigate within WinRE. ​If you had previously created a USB recovery drive , you can boot your computer from the recovery drive. This will take you directly to WinRE with restored USB functionality. ​OEMs and enterprises can use the Preboot Execution Environment (PXE) in Configuration Manager , or can deploy push-button reset features using the Windows Assessment and Deployment Kit (Windows ADK) and Windows Preinstallation Environment (WinPE) add-on to recover affected devices. Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 ​Server: Windows Server 2025 Non-admins might receive unexpected UAC prompts when doing MSI repair operations Non-admins might receive unexpected UAC prompts when doing MSI repair operations (Updated 11/26/25: Additional improvements were added to the Resolution section.) A security improvement was included in the August 2025 Windows security update ( KB5063878 ) and later updates to enforce the requirement that User Account Control (UAC) prompt for administrator credentials when performing Windows Installer (MSI) repair and related operations. This improvement addressed security vulnerability CVE-2025-50173 . As a result, after installing the August 2025 Windows security update and later updates, UAC prompts for administrator rights can appear for standard users in the following scenarios: ​Running MSI repair commands (such as msiexec /fu ). ​Launching Autodesk applications, including some versions of AutoCAD, Civil 3D and Inventor CAM, or when installing an MSI file after a user signs into the app for the first time. ​Installing applications that configure themselves per user. ​Running Windows Installer during Active Setup. ​Deploying packages via Manager Configuration Manager (ConfigMgr) that rely on user-specific "advertising" configurations. ​Enabling Secure Desktop. If a standard user runs an app that initiates an MSI repair operation without displaying UI, it will fail with an error message. For example, installing and running Office Professional Plus 2010 as a standard user will fail with Error 1730 during the configuration process. After installing the September 2025 Windows security update ( KB5065426 ) or later updates, UAC prompts will only be required during MSI repair operations if the target MSI file contains an elevated custom action . This requirement is further refined after installing Windows updates released on and after October 28, 2025, so that UAC prompts will only be required if the elevated custom actions are executed during the repair flow. Installing the latest Windows updates will resolve this issue for apps that do not execute such elevated custom actions, such as Autodesk AutoCAD. Since UAC prompts will still be required for apps that perform custom actions, after installing the September 2025 update, IT admins will have access to a workaround to disable UAC prompts for specific apps by adding MSI files to an allowlist. For details, see the KB article: Unexpected UAC prompts when running MSI repair operations after installing the August 2025 Windows security update . A Group Policy had previously been made available from Microsoft’s Support for business using Known Issue Rollback (KIR) to work around this issue. Organizations no longer need to install and configure this Group Policy to address this issue. Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 10, version 21H2; 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 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2; Windows Server 2008 SP2 Problems playing protected content in some BluRay/DVD/Digital TV applications Problems playing protected content in some BluRay/DVD/Digital TV applications Some Digital TV and BluRay/DVD applications might experience problems playing protected content. Applications using Enhanced Video Renderer with HDCP enforcement or Digital Rights Management (DRM) for digital audio might experience copyright protection errors, frequent playback interruptions, freezing or black screens. This issue does not impact streaming services. Resolution : Problems affecting certain applications that use Enhanced Video Renderer with HDCP enforcement have been addressed in the September 2025 Windows preview update ( KB5065789 ), and later updates. Additional improvements were included in the October 2025 Windows preview update ( KB5067036 ) and later updates to resolve problems for applications using DRM for digital audio. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 Updates installed via WUSA might fail if installed from a shared folder Updates installed via WUSA might fail if installed from a shared folder Windows updates installed using the Windows Update Standalone Installer (WUSA) might fail with error ERROR_BAD_PATHNAME, when the update is installed using WUSA or double-clicking a .msu file from a network share that contains multiple .msu files. These issues might occur on devices that installed updates released May 28, 2025 ( KB5058499 ) and later. WUSA is a method of installing updates using the Windows Update Agent API which is typically only employed in enterprise environments. It is not common in personal or home settings. Please note that this issue does not occur when there is only one .msu file in the network share or when the .msu files are stored locally on the device. In addition, after installing an .msu file by double-clicking or using WUSA and restarting Windows, you might notice that the Update History page in Settings continues to indicate that a restart is required to complete the update. This is temporary and should be resolved on its own. Resolution : This issue was resolved by Windows updates released March 24, 2026 ( KB5079391 ), and later. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one. If you install an update released March 24, 2026 ( KB5079391 ) or later, you do not need to use a workaround for this issue. If you are using an update released before this date, and are experiencing this issue, you have the option to work around it by saving the .msu files locally on the device and install the update from this location. Also, if you've restarted Windows after installing an .msu file via WUSA, please wait 15 minutes or more before checking the Update History page in Settings. After this short delay, the Settings app should properly indicate if the update installed successfully. Additionally, this issue was addressed using Known Issue Rollback (KIR) beginning September 2025, and was resolved automatically for most home users and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. IT admins can resolve this issue for managed devices which have installed the affected update and encountered this issue. It can be fixed by installing and configuring the Group policy 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 . The special Group Policy can be found in Computer Configuration > Administrative Templates > [ Group Policy name]. Group Policy downloads with Group Policy name: ​ Download for Windows 11, version 24H2 and Windows Server, version 2025 - Windows 11 24H2 and Windows Server 2025 KB5062660 250806_17201 Known Issue Rollback.msi Affected platforms: ​Client: Windows 11, version 25H2; Windows 11, version 24H2 ​Server: Windows Server 2025 Error events are logged for CertificateServicesClient Error events are logged for CertificateServicesClient Following installation of the July 2025 Windows non-security preview update ( KB5062660 ) and later updates including the August 2025 Windows security update, Event Viewer may display an error related to CertificateServicesClient (CertEnroll) which can be safely ignored. The issue only manifests as an entry in the Windows Event Viewer, with Error ID 57. The event shows the message “The "Microsoft Pluton Cryptographic Provider” provider was not loaded because initialization failed” . Please note that although this event is logged in Event Viewer every time the device is restarted, it does not reflect an issue with any active Windows component. This event is related to a feature that is currently under active development. There is no impact to Windows processes associated to this event and no action is required to prevent or resolve this error. Resolution: This issue is addressed starting with Windows updates release August 29, 2025 ( KB5064081 ) and later. This resolution has been gradually rolling out throughout the past weeks, and has now reached full availability. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. For commercial customers whose devices are managed by IT administrators, this resolution is expected to be available with Windows updates released October 15, 2025. Affected platforms: ​Client: Windows 11, version 24H2 Problems with NDI streaming performance after installing the August 2025 update Problems with NDI streaming performance after installing the August 2025 update Severe stuttering, lag, and choppy audio/video might occur when using NDI (Network Device Interface) for streaming or transferring audio/video feeds between PCs after installing the August 2025 Windows security update ( KB5063878 ). The issue affects streaming apps, including OBS (Open Broadcast Software) and NDI Tools, especially when "Display Capture" is enabled on the source PC. The problem persists even under low bandwidth conditions. Resolution : This issue was resolved by Windows updates released September 9, 2025 ( KB5065426 ), and updates released after that date. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. If you install an update released September 9, 2025 ( KB5065426 ) or later, you do not need to use a workaround for this issue. If you are using an update released before September 9, 2025, and have this issue, you have the option to apply the following workaround. Workaround: NDI recommends manually changing the NDI Receive Mode to use TCP or UDP instead of RUDP. Affected platforms: ​Client: Windows 11, version 24H2; Windows 10, version 22H2; Windows 10, version 21H2 August 2025 security update might fail to install via WSUS with Error 0x80240069 August 2025 security update might fail to install via WSUS with Error 0x80240069 The August 12, 2025 Windows security update for Windows 11, version 24H2 ( KB5063878 ), might fail to install with error code 0x80240069 when installed via Windows Server Update Services (WSUS) . WSUS allows Servers with the WSUS role to defer, selectively approve, and schedule updates for specific devices or groups across an organization. Home users are unlikely to experience this issue, as WSUS is designed for use across business and enterprise environments. The problem with the Windows Update service has been resolved. If you experienced this issue, please refresh and re-sync with Windows Server Update Services to install the latest update. A Group Policy had previously been released using Known Issue Rollback (KIR) to work around this issue. If you installed the special Group Policy, it could be found in Computer Configuration -> Administrative Templates -> Windows 11 24H2 and Windows Server 2025 KB5063878 250814_00551 Known Issue Rollback. Organizations no longer need to install and configure this Group Policy to address this issue. Affected platforms: ​Client: Windows 11, version 24H2 Parental consent may not show for some browser versions with web filtering on 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. ​ Temporary access to unsupported browsers: This issue has been resolved through a service‑side fix. The rollout began early February 2026 and should reach all affected devices over the coming weeks. If your device presented this symptom, please let it connect to the internet to receive the resolution. No other action is required. For more information on how to use this feature, see Set up Microsoft Family Safety. ​ Missing parental consent prompt: Fixed in the July non-security preview update ( KB5062660 ), released July 22, 2025 . The fix is gradually rolling out and will be automatically enabled on devices with KB5062660 installed or later updates. Affected platforms: ​ Client: Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2 Devices with apps using sprotect.sys driver might stop responding Devices with apps using sprotect.sys driver might stop responding Microsoft is working with SenseShield Technology Co on a compatibility issue between Windows 11, version 24H2 and the sprotect.sys driver. This issue causes affected devices to become unresponsive and display a blue or black screen error. The sprotect.sys driver provides encryption protection and is used by specialized security software and enterprise solutions. This driver can be automatically introduced into a system as part of the installation process of many different applications. The issue impacts devices with any version of the sprotect.sys driver (1.0.2.372 and 1.0.3.48903). To safeguard your update experience, we have applied a compatibility hold on devices running the incompatible sprotect.sys driver. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update release channel. If you have a Home or Pro Windows device affected by this hold, the Windows Update page under Settings will display a message saying you don’t need to take any action now. You can click on the Learn more link for details. For more information, see KB5006965: How to check information about safeguard holds affecting your device. IT administrators using Windows Update for Business reports can check this issue using safeguard ID 56318982. Important : We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved. Resolution : Recent versions of software that employ the sprotect.sys driver have resolved the compatibility issue. Please note that many applications employ SenseShield technology and the sprotect.sys driver is automatically installed with some applications. As a result, it may be difficult to determine which update may be necessary. If an application using sprotect.sys loses functionality, updating it to a newer version can resolve the issue. The safeguard hold has been removed as of October 15, 2025. Eligible devices without other safeguard holds can install Windows 11, version 24H2 via Windows Update. Please note, it can take up to 48 hours before the update to Windows 11, version 24H2 is offered. Restarting your device might help it offer faster. Affected platforms: ​Client: Windows 11, version 24H2 Some devices that have Dirac Audio with cridspapo.dll might lose audio output Some devices that have Dirac Audio with cridspapo.dll might lose audio output A compatibility safeguard hold has been applied to a limited set of devices from one manufacturer due to an audio issue following the installation of Windows 11, version 24H2. This issue was observed on some devices containing Dirac Audio with the cridspapo.dll file. The incompatibility relates to the software component cridspapo.dll, which is part of these devices’ audio processing software. Dirac Audio is a digital sound improvement technology that enhances audio clarity and precision. After installing Windows 11, version 24H2, some users reported that their device’s integrated speakers, Bluetooth speakers, and Bluetooth headsets stopped functioning. They also reported that both first-party and third-party applications didn’t recognize these devices. To prevent you from encountering this audio issue, we have applied a compatibility hold on devices containing Dirac Audio with cridspapo.dll. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update channel until this issue is resolved. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 54283088. If you are using a Windows Home or Pro edition as your personal device, you can check whether your device has this or other safeguard holds applied. Go to Start > Settings > Windows Update > select Check for Windows updates . If your device has a compatibility hold, you will see the message “Upgrade to Window 11 is on its way to your device. There is nothing that requires your attention at the moment. Once the update is ready for your device, you’ll see it available on this page.” This message will be followed by the link “Learn More”, which will direct you to website listing safeguards applicable specifically to your device. For more information, see KB5006965 . Resolution : The issue has been resolved by the driver vendor, and a new version of the driver has been made available via Windows Update. The safeguard hold has been removed as of September 11, 2025. Eligible devices with no other safeguard hold should now be able to install Windows 11, version 24H2 via the Windows Update release channel. Please note, it can take up to 48 hours before the update to Windows 11, version 24H2 is offered. Restarting your device might help it offer faster. Affected Platforms: ​ Client: Windows 11, version 24H2 Camera use might cause some applications to become unresponsive Camera use might cause some applications to become unresponsive After installing Windows 11, version 24H2, certain devices might experience problems using the integrated camera in scenarios where object or face detection features are enabled. This can include using the Camera app, using facial recognition sign-in options with Windows Hello, and other applications that use the integrated camera. To safeguard your update experience, we have applied a compatibility hold on device models affected by this issue. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update release channel. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 53340062. Resolution : The safeguard hold has been removed as of September 18, 2025. Eligible devices with no other safeguard hold should now be able to install Windows 11, version 24H2 via the Windows Update release channel. Please note, it can take up to 48 hours before the update to Windows 11, version 24H2 is offered. Restarting your device might help it offer faster. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one. Affected platforms: ​Client: Windows 11, version 24H2 Compatibility issues with Intel Smart Sound Technology drivers Compatibility issues with Intel Smart Sound Technology drivers Intel and Microsoft have found incompatibility issues with certain versions of drivers for Intel Smart Sound Technology (Intel SST) on Intel 11th Gen Core processors and Windows 11, version 24H2. Devices running version 24H2 with the affected Intel SST driver might receive an error with a blue screen. The affected driver is named Intel® Smart Sound Technology (Intel® SST) Audio Controller , and is listed under System Devices in Device Manager and is found with the file name 'IntcAudioBus.sys' . If this file is version 10.29.0.5152 or 10.30.0.5152 , this issue can occur. Only devices with both an Intel 11th Gen Core processors and an Intel SST driver version of 10.29.0.5152 or 10.30.0.5152 are affected by this issue. To safeguard your update experience, we have applied a compatibility hold on Windows devices which have Intel SST driver versions 10.29.0.5152 or 10.30.0.5152. These devices will not be offered to install Windows 11, version 24H2 via the Windows Update release channel. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 51876952. Important : We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved. Resolution: Devices which are encountering this issue will need to install newer versions of the Intel® SST Audio Controller drivers prior to updating to Windows 11, version 24H2. The issue is resolved by updating the Intel® Smart Sound Technology drivers to version 10.30.00.5714 and later, or 10.29.00.5714 and later. Please note that later versions of this driver might refer to only the last part of the version number. For the purpose of addressing this issue, 10.30.x versions are not newer than 10.29.x versions. For most users, updated drivers can be installed via Windows Update by checking for Windows updates on your device . This is the preferred method of installing these and other drivers. If your device still encounters this safeguard hold 48 hours after updating your drivers, it's possible drivers for this Audio Controller haven't been developed for your specific device hardware configuration. In this case, you will need to contact your device manufacturer (OEM) for more information on the necessary drivers. Microsoft works to make the latest compatible drivers available under Windows Update whenever developers have released them. IT admins in organizations where devices are managed can refer to the following resources to deploy drivers using one of these tools: ​Windows Update for Business and Intune customers: Learn about Windows Driver updates policy for Windows 10 Windows 11 devices in Intune ​Autopatch: Manage driver and firmware updates Once you have updated to a compatible version of the Intel® Smart Sound Technology drivers, you should be able to upgrade to Windows 11, version 24H2. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to version 24H2 is offered. Affected platforms: ​Client: Windows 11, version 24H2 Wallpaper customization applications might not work as expected Wallpaper customization applications might not work as expected After installing Windows 11, version 24H2, some wallpaper customization applications might not launch or function correctly. Multiple applications are affected, and symptoms can include wallpapers not appearing correctly, icons disappearing from the desktop, loss of desktop preview functionality, issues with virtual desktops, or error messages displayed by the application. To safeguard your update experience, we have applied a compatibility hold on devices which are utilizing one of these applications. These devices will not be offered or install Windows 11, version 24H2 via the Windows Update release channel. IT administrators using Windows Update for Business reports can check this issue using its safeguard ID: 52754008. Resolution : The safeguard hold has been removed as of October 15, 2025. Eligible devices without other safeguard holds can install Windows 11, version 24H2 via Windows Update. Some devices might display a warning indicating that a desktop or wallpaper application may be incompatible with this version of Windows. A confirmation will be requested in order to proceed with installation. Please note that wallpaper and desktop customization applications sometimes utilize Windows functions in ways that have unintended results. If you continue to experience issues with these applications after installing Windows 11, version 24H2. we recommend updating the app, since a newer version might be compatible. You may uninstall the application instead. If problems persist, please contact the application developer for more information. Affected platforms: ​Client: Windows 11, version 24H2 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. Additional resources Last updated on 2026-09-11