Resolved issues in Windows 11, version 21H2
Find information on recently resolved issues for Windows 11, version 21H2. 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 (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.
Resolved issues
Summary | Originating update | Status | Date resolved |
---|---|---|---|
Edge updates might cause Microsoft Copilot app to show up in Installed apps Edge updates might install a new package and users might see Microsoft Copilot app among the device's Installed apps | N/A | Resolved | 2024-06-13 14:21 PT |
BitLocker might incorrectly receive a 65000 error in MDMs "Requires Device Encryption" might incorrectly report as an error in some managed environments. | N/A | Resolved KB5039213 | 2024-06-11 10:00 PT |
VPN connections might fail after installing the April 2024 security update We are investigating user reports, and we will provide more information in the coming days | OS Build 22000.2899 KB5036894 2024-04-09 | Resolved KB5037770 | 2024-05-14 10:00 PT |
The January 2024 Windows RE update might fail to install WinRE is the Windows Recovery Environment. The update fails if there's insufficient free space in the WinRE partition. | N/A KB5034440 2024-01-09 | Resolved | 2024-04-30 14:07 PT |
Compatibility issues with Intel Smart Sound Technology drivers and Windows 11 Windows 11 devices with the affected Intel SST driver might receive an error with a blue screen. | N/A | Resolved External | 2024-04-12 15:36 PT |
Some apps might fail to playback, record, or capture video Apps and cameras using WVC1 codec might fail to function as expected. | OS Build 22000.30000 KB5028245 2023-07-25 | Resolved KB5034766 | 2024-02-13 10:00 PT |
Printer names and icons might be changed and HP Smart app automatically installs In most cases, it is possible to use the printer for printing jobs and other features such as copy, scan, or fax. | N/A | Resolved | 2023-12-22 15:53 PT |
Microsoft received reports about an “UNSUPPORTED_PROCESSOR” error Investigation concluded that the error reported by users was not caused by the August 2023 preview updates. | OS Build 22000.2360 KB5029332 2023-08-22 | Resolved External | 2023-09-07 16:51 PT |
Computing effective access might not show results You might be unable to view effective access and explorer.exe might continue to use CPU after closing the dialog. | OS Build 22000.1936 KB5026368 2023-05-09 | Resolved KB5027292 | 2023-06-28 14:00 PT |
When using Outlook, opening links in emails might display an error Office updates released July 11, 2023 introduce this behavior by design due to the new security protections | N/A | Resolved | 2023-07-25 18:26 PT |
"Local Security Authority protection is off." with persistent restart Once enabled, your Windows device might persistently notify you that it is vulnerable, and a restart is required. | N/A | Resolved | 2023-07-05 17:46 PT |
Integrated camera might not work as expected on some Arm-based devices Starting May 23, 2023, some Arm-based devices might be unable to use the integrated webcam due to a driver issue. | N/A | Resolved External | 2023-07-10 11:21 PT |
Microsoft Outlook and some apps might not open 32-bit apps from Microsoft or third-parties might fail to open with certain security software installed. | OS Build 22000.2057 KB5027223 2023-06-13 | Resolved External | 2023-06-28 17:36 PT |
Start menu, Windows Search and UWP apps might have issues opening Affected devices have apps installed which integrate with Windows, Microsoft Office, or Microsoft Outlook. | N/A | Resolved KB5027292 | 2023-06-28 14:00 PT |
Issue details
April 2024
Edge updates might cause Microsoft Copilot app to show up in Installed apps
Status | Originating update | History |
---|---|---|
Resolved | N/A | Resolved: 2024-06-13, 14:21 PT Opened: 2024-04-16, 18:23 PT |
Updates to Edge browser version 123.0.2420.65, released on March 28, 2024, and later, might incorrectly install a new package (MSIX) called ‘Microsoft chat provider for Copilot in Windows’ on Windows devices. Resulting from this, the Microsoft Copilot app might appear in the Installed apps in Settings menu.
It is important to note that the Microsoft chat provider for Copilot in Windows does not execute any code or process, and does not acquire, analyze, or transmit device or environment data in any capacity.
This package was intended to prepare some Windows devices for future Windows Copilot enablement and was not intended for all devices. Although the component installed as part of this issue can cause the Microsoft Copilot app to be shown as part of the Installed apps, this component does not fully install or enable Microsoft Copilot.
Note: Edge browser version 124.0.2478.51, released on April 18, 2024, contains a change by which the chat provider for Copilot in Windows will not continue to be installed on every device.
Resolution: This issue is now resolved with Edge browser updates released on April 26, 2024, and June 13, 2024. Edge version 124.0.2478.67 was released on April 26 and removed the package ‘Microsoft chat provider for Copilot in Windows’ from all servers affected by this issue. Edge version 126.0.2592.56 was released on June 13, 2024, and removed the same package from all Windows client versions affected by this issue. The ‘Microsoft Copilot’ entry will not show in the Installed apps list in the Settings menu once the Edge browser is updated.
Affected platforms:
Client: Windows 11, version 23H2, Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2
Server: Windows Server 2022
VPN connections might fail after installing the April 2024 security update
Status | Originating update | History |
---|---|---|
Resolved KB5037770 | OS Build 22000.2899 KB5036894 2024-04-09 | Resolved: 2024-05-14, 10:00 PT Opened: 2024-04-30, 20:15 PT |
Windows devices might face VPN connection failures after installing the April 2024 security update (KB5036894) or the April 2024 non-security preview update.
Resolution: This issue was resolved by Windows updates released May 14, 2024 (KB5037770), and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
Client: Windows 11, version 23H2; Windows 11, version 22H2, Windows 11, version 21H2, Windows 10, version 22H2, Windows 10, version 21H2.
Server: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008.
January 2024
The January 2024 Windows RE update might fail to install
Status | Originating update | History |
---|---|---|
Resolved | N/A KB5034440 2024-01-09 | Resolved: 2024-04-30, 14:07 PT Opened: 2024-01-12, 14:10 PT |
Devices attempting to install the January 2024 Windows Recovery Environment update (KB5034440) might display an error related to the size of the Recovery Environment's partition. The Windows Recovery Environment (WinRE) is used to repair or recover from issues affecting Windows.
Resulting from this error, the following message might be displayed.
- "0x80070643 - ERROR_INSTALL_FAILURE"
Important: If your Windows device does not have a recovery environment configured, you do not need this update (KB5034440). In this case, the error can be ignored.
To determine whether your device has a recovery environment configured, inspect the WinRE status by following these steps:
- Open a Command Prompt window (cmd) as admin.
- To check the WinRE status, run reagentc /info. If the WinRE is configured, a "Windows RE status" field will appear in the output, with value "Enabled". If WinRE is not configured, this field will have the value "Disabled".
Resolution: Automatic resolution of this issue won't be available in a future Windows update. Manual steps are necessary to complete the installation of this update on devices which are experiencing this error.
The WinRE partition requires 250 megabytes of free space. Devices which do not have sufficient free space will need to increase the size of the partition via manual action. For guidance on making this change, review the following resources:
- A code script can be used to extend the partition size. A sample script has been provided in the documentation for adding an update package to WinRE. See Extend the Windows RE Partition.
- Guidance to manually change the WinRE partition size can additionally be found in KB5028997: Instructions to manually resize your partition to install the WinRE update.
Completion of these manual steps will allow the installation of this update to succeed.
Affected platforms:
- Client: Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2
- Server: Windows Server 2022
December 2023
Printer names and icons might be changed and HP Smart app automatically installs
Status | Originating update | History |
---|---|---|
Resolved | N/A | Resolved: 2023-12-22, 15:53 PT Opened: 2023-12-04, 18:46 PT |
Some issues related to printer configurations are being observed on Windows devices. Microsoft is investigating this issue and coordinating with partners on a solution.
Symptoms can include the following:
- Some Windows devices are installing the HP Smart app.
- Printers may show LaserJet M101-M106 model information regardless of their manufacturer. Printer icons might also be changed.
- Double clicking on a printer displays the on-screen error "No tasks are available for this page".
Note: Our investigations indicate that this issue is not caused by an HP update. In most cases, it should be possible to use the printer as expected, including queueing printing jobs, as well as other features such as copy, scan, or fax. Printers on the device will continue to use the expected drivers for printer operations. However, this issue might affect associations with other manufacturer-supplied printer apps used to extend basic printer capabilities. If this is the case, some or all of those extended functions might not work.
Resolution: You can resolve this issue by downloading and executing one of the files listed in the article KB5034510 Printer Metadata Remediation Tool – December 2023. In addition to this tool, a critical troubleshooter is being gradually rolled out to all affected Home and non-managed business devices. Critical troubleshooting happens automatically in the background and won’t get in the way of using your device. To learn more about critical and recommended troubleshooters, see Keep your device running smoothly with recommended troubleshooting.
If you need support to resolve this issue, go to https://support.microsoft.com/contactus, and select Windows.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 11, version 21H2; 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 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
October 2023
BitLocker might incorrectly receive a 65000 error in MDMs
Status | Originating update | History |
---|---|---|
Resolved KB5039213 | N/A | Resolved: 2024-06-11, 10:00 PT Opened: 2023-10-09, 14:51 PT |
Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important: This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.
Workaround: To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured.
Resolution: This issue was resolved by Windows updates released June 11, 2024 (KB5039213), and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
Affected platforms:
- Client: Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019
- Server: None
August 2023
Microsoft received reports about an “UNSUPPORTED_PROCESSOR” error
Status | Originating update | History |
---|---|---|
Resolved External | OS Build 22000.2360 KB5029332 2023-08-22 | Last updated: 2023-09-07, 16:51 PT Opened: 2023-08-23, 19:44 PT |
Microsoft has received reports of an issue in which users are receiving an “UNSUPPORTED_PROCESSOR” error message on a blue screen after installing updates released on August 22, 2023 (KB5029332) and then restarting their device. KB5029332 might automatically uninstall to allow Windows to start up as expected. If this occurs, we recommend that you do not attempt to reinstall KB5029332.
Resolution: After investigating these reports, we have found that the “UNSUPPORTED_PROCESSOR” error was not caused by issues in KB5029332 and is limited to a specific subset of processors. For more information on this issue, please see 13th Gen Intel® Core™ Processor Families with Performance Hybrid Architecture Blue Screen Hang Issue with Windows* Preview Updates. This issue will not affect future monthly updates released for Windows. KB5029332 will not be offered to Windows devices that might be affected by this issue and it is recommended that you do not attempt to manually install it on affected devices.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2
- Server: None
July 2023
Some apps might fail to playback, record, or capture video
Status | Originating update | History |
---|---|---|
Resolved KB5034766 | OS Build 22000.30000 KB5028245 2023-07-25 | Resolved: 2024-02-13, 10:00 PT Opened: 2023-07-25, 14:47 PT |
After installing KB5028245 or later updates, some apps might fail to playback, record, or capture video when using the WVC1 codec (VC-1). Certain cameras or webcams might also fail to work if they use the WVC1 codec by default.
Resolution: This issue was resolved in updates released February 13, 2024 (KB5034766) and later. We recommend you install the latest security update for your device. It contains important improvements and issue resolutions, including this one.
If you install an update released February 13, 2024 (KB5034766) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before February 13, 2024, and have this issue, you can resolve it by installing and configuring the special Group Policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates > <Group Policy name listed below>.
For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.
Group Policy downloads with Group Policy name:
- Download for Windows 11, version 22H2 - Windows 11 22H2 KB5027303 230528_03453 Known Issue Rollback
- Download for Windows 11, version 21H2 - Windows 11 (original release) KB5028245 230630_032045 Known Issue Rollback
Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2
- Server: None
When using Outlook, opening links in emails might display an error
Status | Originating update | History |
---|---|---|
Resolved | N/A | Resolved: 2023-07-25, 18:26 PT Opened: 2023-07-25, 18:14 PT |
When clicking on links in emails in Microsoft Outlook, you might receive an error message with the text “Something unexpected went wrong with this URL”. Opening links in emails on Microsoft Outlook may also display an error stating "Microsoft Office has identified a potential security concern. This location may be unsafe."
As a result of Microsoft Office security hardening changes, hyperlinks which contain fully-qualified domain name (FQDN) or IP address will display this message. This is due to protections released July 11, 2023.
Please note: This behavior is caused by a protection update in Outlook released July 11, 2023. It is not caused by Windows Updates.
Resolution: These messages are displayed as part of recent Office security changes. Details can be seen in KB article Outlook blocks opening FQDN and IP address hyperlinks after installing protections for Microsoft Outlook Security Feature Bypass Vulnerability released July 11, 2023.
In order to ensure continued access to files on FQDN or IP address paths, add those URLs to the Trusted Sites zone in accordance with Windows guidance. An Intranet site is identified as an Internet site when you use an FQDN or an IP address. This can be accomplished with the following steps:
- Open the "Internet Properties" settings. This can be done in one of the following ways:
- Open "Control Panel" from the start menu and select "Internet Options" under "Network and Internet"
- On your keyboard, press and hold the Windows key, then press the letter S. In the search dialog that appears, type "Internet Properties" and select the first result.
- Click the Security tab, then select Trusted Sites.
- Under "Add this website to the zone", add the URL, UNC, FQDN path that you want to allow. For example, add: file://server.usa.corp.com
Note: If the entry you wish to add does not explicitly start with ‘https:’, you must first uncheck the ‘Require server verification (https) for all sites in this zone’ checkbox before it can be saved.
This workaround can also be deployed via group policy. See policy: \\Windows Components\Internet Explorer\Internet Control Panel\Security Page\Site to Zone Assignment List on the Group Policy Search site.
For additional information see the respective CVEs below.
- MSRC CVE-2023-33151: Microsoft Outlook Spoofing Vulnerability
- MSRC CVE-2023-35311: Microsoft Outlook Security Feature Bypass Vulnerability
- KB5002427: Description of the security update for Outlook 2016: July 11, 2023 (KB5002427)
- KB5002432: Description of the security update for Outlook 2013: July 11, 2023 (KB5002432)
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2
- Server: None
June 2023
Computing effective access might not show results
Status | Originating update | History |
---|---|---|
Resolved KB5027292 | OS Build 22000.1936 KB5026368 2023-05-09 | Resolved: 2023-06-28, 14:00 PT Opened: 2023-06-21, 16:37 PT |
After installing updates released on May 9, 2023 or later updates, you might be unable to view Effective Access in the "Advanced Security Settings" dialog for shared files or folders. On affected devices, when the "View effective access" button is selected, you will receive the message "Computing effective access...." but the results of the query might not be displayed and explorer.exe might continue to use CPU after the Advanced Security settings dialog is closed. This issue is unlikely to be experienced by consumers using Windows devices in their home.
Workaround: If you have attempted to view effective access, you can mitigate the CPU usage issue by restarting your device or by signing out for the affected user. Note: Locking Windows will not mitigate this issue, you must sign out.
Resolution: This issue was resolved in KB5027292.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2
- Server: Windows Server 2022
Microsoft Outlook and some apps might not open
Status | Originating update | History |
---|---|---|
Resolved External | OS Build 22000.2057 KB5027223 2023-06-13 | Last updated: 2023-06-28, 17:36 PT Opened: 2023-06-28, 17:14 PT |
After installing KB5027223 or later updates on Windows devices with certain antivirus, antimalware or security software installed, you might not be able to open Microsoft or third-party apps. Some known affected apps are Microsoft Outlook and other Microsoft Office apps. This issue only occurs with 32-bit apps running on 64-bit Windows with Trellix Endpoint Security version earlier than 35.31.25. When attempting to open an affected app, Event Log indicates an access violation with the error "module is unknown". This issue is not likely to be encountered by consumers using Windows devices in their home.
Resolution: This issue has been resolved by Trellix in Endpoint Security Agent (HX) 35.31.25 and later. If you are experiencing this issue with other security software installed or after installing the latest version of Trellix Endpoint Security Agent, please contact customer support of the security software you are using.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2
- Server: Windows Server 2022
May 2023
Integrated camera might not work as expected on some Arm-based devices
Status | Originating update | History |
---|---|---|
Resolved External | N/A | Last updated: 2023-07-10, 11:21 PT Opened: 2023-05-26, 18:02 PT |
Windows devices using certain Arm-based processors might have issues using integrated cameras starting on May 23, 2023. When encountering this issue, you might receive an “0xA00F4271<MediaCaptureFailedEvent> (0x80004005)” error when attempting to use the Camera app. Affected devices use these processors: Qualcomm 8cx Gen 1, Qualcomm 8cx Gen 2, Microsoft SQ1, and Microsoft SQ2. Note: This issue does not affect USB cameras or webcams, even when attached to an affected Windows devices.
Workaround: Microsoft is deploying a critical troubleshooter to mitigate this issue on most affected Windows devices. Troubleshooters are applied automatically and can't be run manually. For more information about troubleshooting, see keep your device running smoothly with recommended troubleshooting. To check if the troubleshooter has been applied, look for the following in troubleshooter history:
To mitigate this issue on managed devices where troubleshooters are disabled by your organization or if you want the mitigation before the troubleshooter has run automatically, use the following steps to disable the affected feature of the camera driver. Important: You should apply this workaround only on devices experiencing this issue. Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk:
- Select the Start button and type cmd, then right click or long press on Command Prompt and select Run as administrator.
- Copy and paste the following command and run the command by pressing Enter: reg add "HKLM\SYSTEM\CurrentControlSet\Control\Qualcomm\Camera" /v EnableQCOMFD /t REG_DWORD /d 0 /f
- Restart any app which uses the camera or restart your Windows device.
- The integrated camera should now function as expected.
Note: This workaround might disable some features of the camera or lower the image quality but should allow the camera to function until the issue is resolved by the device manufacturer with an updated camera driver. An updated driver should restore full camera functionality and the workaround should not need to be undone.
Resolution: This issue was resolved with the release of updated camera drivers. The updated drivers should offer and install automatically from Windows Update in the coming weeks. If you would like to check if updated drivers are available for your device, you can manually check for updates. If updated camera drivers are not already installed and not offered when manually checking Windows Update, they might not be available yet for affected devices from your Windows device manufacturer (OEM).
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2
- Server: None
March 2023
"Local Security Authority protection is off." with persistent restart
Status | Originating update | History |
---|---|---|
Resolved | N/A | Resolved: 2023-07-05, 17:46 PT Opened: 2023-03-21, 11:18 PT |
After installing "Update for Microsoft Defender Antivirus antimalware platform - KB5007651 (Version 1.0.2302.21002)", you might receive a security notification or warning stating that "Local Security protection is off. Your device may be vulnerable." and once protections are enabled, your Windows device might persistently prompt that a restart is required. Important: This issue affects only "Update for Microsoft Defender Antivirus antimalware platform - KB5007651 (Version 1.0.2302.21002)". All other Windows updates released on March 14, 2023 for affected platforms (KB5023706 and KB5023698), do not cause this issue.
Workaround: If you have enabled Local Security Authority (LSA) protection and have restarted your device at least once, you can dismiss warning notifications and ignore any additional notifications prompting for a restart. You can verify that LSA protection is enabled by looking in Event Viewer using the information available here. Important: Currently, we do not recommend any other workaround for this issue.
Resolution: This issue was resolved in an update for Windows Security platform antimalware platform KB5007651 (Version 1.0.2306.10002). If you would like to install the update before it is installed automatically, you will need to check for updates.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 11, version 21H2
- Server: None
January 2023
Start menu, Windows Search and UWP apps might have issues opening
Status | Originating update | History |
---|---|---|
Resolved KB5027292 | N/A | Resolved: 2023-06-28, 14:00 PT Opened: 2023-01-24, 09:47 PT |
The Start menu, Windows search, and Universal Windows Platform (UWP) apps might not work as expected or might have issues opening. Affected Windows devices might have damaged registry keys or data which might affect apps using Microsoft Office APIs to integrate with Windows, Microsoft Office, or Microsoft Outlook or Outlook Calendar. An example of an app affected by this issue is ClickShare. The underlying Issue is not caused by the installation of an update to Windows and might be exposed by an update to an affected app.
Workaround: To mitigate this issue, you can uninstall apps which integrate with Windows, Microsoft Office, Microsoft Outlook or Outlook Calendar. Updates to affected apps or guidance from the developer of the app might also be available. If you are using ClickShare by Barco, please see Symptom: Start Menu and other shell components fail when Apps including Barco's ClickShare access Office APIs and Unresponsive Windows taskbar or user shell folder permissions issues with ClickShare App Calendar integration.
Resolution: This issue was resolved in KB5027292.
Affected platforms:
- Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 20H2
- Server: None
November 2021
Compatibility issues with Intel Smart Sound Technology drivers and Windows 11
Status | Originating update | History |
---|---|---|
Resolved External | N/A | Last updated: 2024-04-12, 15:36 PT Opened: 2021-11-15, 16:40 PT |
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. Windows 11 devices 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 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 upgrade experience, we have applied a compatibility hold on Windows 10 devices which have Intel SST driver versions 10.29.0.5152 or 10.30.0.5152. This will prevent those devices from being offered any version of Windows 11. If your organization is using Update Compliance, the safeguard IDs are:
- Windows 11, version 21H2: 36899911
- Windows 11, version 22H2: 41291788
- Windows 11, version 23H2: 49561482
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. 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 customers: Deploy drivers and firmware updates - Windows Update for Business deployment service
- Intune: Learn about Windows Driver updates policy for Windows 10 Windows 11 devices in Intune
- Autopatch: Manage driver and firmware updates - Windows Deployment
Once you have updated to a compatible version of the Intel® Smart Sound Technology drivers, you should be able to upgrade to Windows 11. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. We recommend that you do not attempt to manually upgrade using the 'Update now' button or the Media Creation Tool until you have performed the necessary driver updates.
Affected platforms:
- Client: Windows 11, version 23H2, Windows 11, version 22H2; Windows 11, version 21H2
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.