Windows 11, version 24H2 known issues and notifications

Find information on known issues and the status of the Windows 11, version 24H2 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 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 the Windows 11 2024 Update

• 

  Copilot+ PCs: more AI features that empower you every day

Known issues

Issue details

September 2025

Non-admins might receive unexpected UAC prompts when doing MSI repair operations

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.

Resolution:

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. 

Since UAC prompts will still be required for apps that perform custom actions, after installing this 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 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

August 2025

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

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 resolution is gradually rolling out for commercial devices that have Windows updates managed by Microsoft and consumer devices (Home and Pro editions) and will be automatically enabled on devices with KB5064081, released on August 29, 2025.

The rollout is expected to complete in approximately 4 weeks. After that, all subsequent security and non-security updates will include this resolution by default.

Next steps: This resolution will be available for commercial customers devices managed by the IT departments in the coming month. 

Affected platforms:

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

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.

Workaround: To work around this issue, save 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.

Mitigation: This issue is addressed using Known Issue Rollback (KIR) and is 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

Next steps: We are working on releasing a resolution for this issue in a future Windows update. We will provide an update when more information is available.

Affected platforms:

• ​Client: Windows 11, version 24H2
• ​Server: Windows Server 2025

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 (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 11, version 22H2; Windows 10, version 22H2
• ​Server: None

April 2025

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.

Next Steps: SenseShield is currently investigating this issue. Microsoft is collaborating with SenseShield, and we will provide more information when it is available.

Affected platforms:

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

December 2024

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: A new version of the driver has been made available via Windows Update, which addresses this issue. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one.

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

October 2024

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.

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.

Next Steps: We are working on a resolution and will provide more information when it is available.

Affected platforms:

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

September 2024

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: We have started to gradually remove this safeguard hold. If you try to install version 24H2 using Windows Update under Settings, Windows 11 Installation Assistant, or Media Creation Tool, you might receive a message requesting you to uninstall your wallpaper app. We also recommend updating the app, since a newer version might be compatible. Or you may uninstall, instead. After you complete this action, you will be able to finish installing version 24H2.

Note that several wallpaper applications are currently included in this compatibility hold. For this reason, the specific timing of the resolution of this issue on a given device may depend on the application being used and the timing of that application's update. As new versions and updates are released for these applications by their respective developers, it's expected that these issues will be resolved.

Affected platforms:

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

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. It 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
• ​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.