Windows 11, version 22H2 known issues and notifications

Find information on known issues and the status of the rollout for Windows 11, version 22H2. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). Want the latest Windows release health updates? Follow @WindowsUpdate on Twitter.

The Windows release health hub is always evolving. Take our short survey and let us know how we can improve.

Current status as of October 4, 2022 (PT)

We are entering a new phase of the rollout for Windows 11, version 22H2 and we are increasing its availability to all who check for updates on eligible Windows devices. Note that, if we detect that your device might have an issue, such as an application incompatibility, we might put a safeguard hold in place and not offer the update until that issue is resolved. Information regarding safeguard holds is available below on this page.

Users who are interested in experiencing the latest feature update can choose to do so by opening Windows Update Settings and selecting Check for updates. If your device is ready, you will see the option to Download and install. For more information on this update experience, watch this video.

If you are using Windows 10, you can check if your device is eligible for the upgrade to Windows 11 by using the PC Health Check app or checking Windows 11 specs, features, and computer requirements. For more information on the Windows 11 upgrade experience for Window 10 devices, watch this video.

To learn more about the status of the Windows 11, version 22H2 rollout and safeguard holds which might be applied to your device, bookmark this page. Learn more about the ways to install Windows 11.

Known issues

This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

SummaryOriginating updateStatusLast updated
Task Manager might not display in expected colors
Task Manager should function as expected but some parts of the UI might not be readable.
OS Build 22621.900
KB5020044
2022-11-29
Mitigated
2022-11-30
12:29 PT
Changing IME input modes might cause applications to become unresponsive
Keyboard shortcuts might cause a limited set of applications to stop responding
N/A

Resolved
KB5020044
2022-11-29
10:00 PT
Lower than expected performance in some games
Some games and apps might inadvertently enable GPU performance debugging features.
N/A

Confirmed
2022-11-23
18:44 PT
Audio might be out of Sync when capturing video via Xbox Game Bar
The Xbox Game Bar app might have issues in which the audio is out of sync when capturing gameplay.
N/A

Resolved
KB5018496
2022-10-25
14:00 PT
Some installed printers might only allow default settings
Some printers might not have all features available, such as color, 2-sided printing, or high res.
N/A

Resolved
2022-11-18
17:24 PT
Sign in failures and other issues related to Kerberos authentication
After installing updates released November 2022, you might have Kerberos authentication issues.
OS Build 22621.819
KB5019980
2022-11-08
Resolved
2022-11-18
16:22 PT
Direct Access might be unable to reconnect after your device has connectivity issues
This issue might happen after losing network connectivity or transitioning between Wi-Fi networks or access points.
OS Build 22621.675
KB5019509
2022-10-18
Resolved
2022-11-13
15:34 PT
Connections may fail when using Remote Desktop Connection Brokers
Remote Desktop Services collection, RemoteApp, and Desktop Connections are affected
N/A

Confirmed
2022-11-22
11:03 PT
Domain join processes may fail with error "0xaac (2732)"
This might be encountered when an account was created by a different identity than the one used to join the domain
OS Build 22621.674
KB5018427
2022-10-11
Confirmed
2022-10-27
16:57 PT
Update might fail to install and you might receive a 0x800f0922 error
Security update for Secure Boot DBX might fail to install.
N/A

Investigating
2022-10-18
10:04 PT
Provisioning packages might not work as expected
Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart.
N/A

Investigating
2022-10-06
07:54 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

Mitigated External
2022-09-22
17:52 PT

Issue details

November 2022

Task Manager might not display in expected colors

StatusOriginating updateHistory
MitigatedOS Build 22621.900
KB5020044
2022-11-29
Last updated: 2022-11-30, 12:29 PT
Opened: 2022-11-30, 12:29 PT

After installing KB5020044, Task Manager might display certain elements in the user interface (UI) in unexpected colors. On affected devices, Task Manager should function as expected but some parts of the UI might not be readable. You might be affected by this issue if you have "Choose your mode" set to "Custom", in the Personalization -> colors section of Settings. If you are using Dark or Light for the "Choose your mode" setting, you should not be affected by this issue.

Workaround: To mitigate this issue, you can set the "Choose your mode" setting to either Dark or Light until this issue is resolved. To do this, right click or long press on the desktop, select "Personalize", select "Colors", and then select either "Dark" or "Light" for "Choose your mode".

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Affected platforms:

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

Changing IME input modes might cause applications to become unresponsive

StatusOriginating updateHistory
Resolved KB5020044N/A

Resolved: 2022-11-29, 10:00 PT
Opened: 2022-11-18, 14:07 PT

After installing Windows 11, version 22H2 (also called Windows 11 2022 Update), certain applications may become unresponsive when keyboard shortcuts are used to turn on/off or change IME (Input Method Editor) input modes.

Examples of actions that can cause this issue:

  • ​For Japanese:
    • ​Using the Hankaku/Zenkaku (半角 / 全角) key on a Japanese keyboard
    • ​Using the default keyboard shortcut: holding down the Alt key and pressing ~ (tilde)
  • ​For Chinese:
    • ​Using the default keyboard shortcut: holding down the Control key and pressing Space
  • ​For Korean:
    • ​Using the default keyboard shortcut: pressing down the right Alt key

It is possible this issue will occur silently, and not result in the display of any error messages.

This issue is observed for applications which load certain components of the Text Services Framework (TSF). Only some applications do this, not all. Applications which don't load these components should not experience this issue, and are expected to function normally when keyboard shortcuts are used.

Workaround: Changing input mode by clicking the IME mode icon in the taskbar should not trigger this issue. This issue occurs only when using keyboard shortcuts.

Resolution: This issue was resolved in updates released November 29, 2022 ( KB5020044) and later. We recommend you install the latest security update for your device.

Affected platforms:

  • ​Client: Windows 11, version 22H2

Lower than expected performance in some games

StatusOriginating updateHistory
ConfirmedN/A

Last updated: 2022-11-23, 18:44 PT
Opened: 2022-11-10, 17:41 PT

Some games and apps might experience lower than expected performance or stuttering on Windows 11, version 22H2. Affected games and apps are inadvertently enabling GPU performance debugging features not meant to be used by consumers.

To safeguard your upgrade experience, we have applied a compatibility hold on devices affected by this issue from being offered or installing Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard IDs are 41766570 and 41990091.

Workaround: If you are already on Windows 11, version 22H2 and are experiencing this issue, you might be able to resolve it by updating your games and gaming related apps to the latest version available. If you are unsure how to update the games and apps you have installed, you will need to consult the developer of those games and apps but most will update automatically through the store they were purchased from or directly when opening them.

Next steps: We are working on a resolution and will provide an update in an upcoming release. Note: We recommend that you do not attempt to manually upgrade using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed. 

Important Notes:

  • ​​November 22, 2022: The safeguard hold with the safeguard ID of 41990091 has been updated to only safeguard Windows devices which have one of the small subset of games and apps which are still affected by this issue. 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. Restarting your device and checking for updates might help it to offer sooner.

Affected platforms:

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

Audio might be out of Sync when capturing video via Xbox Game Bar

StatusOriginating updateHistory
Resolved KB5018496N/A

Resolved: 2022-10-25, 14:00 PT
Opened: 2022-11-03, 18:31 PT

The Xbox Game Bar app might have issues in which the audio is out of sync when capturing gameplay to a video file. You are more likely to encounter this issue when using the "Record last 30 seconds" feature when “Record in the background while I’m playing game” is enabled in Xbox Game Bar. Developer Note: Apps which capture or process video files using the same underlying Windows libraries or APIs as Xbox Game Bar might also be affected by this issue.

To safeguard your upgrade experience, we have applied a compatibility hold on devices which have previously used the capture feature in the Xbox Game Bar app from being offered or installing Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard ID is 41584256. 

Resolution: This issue was resolved in  KB5018496 and the safeguard hold has been removed as of November 10, 2022. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 11, version 22H2 is offered.

Affected platforms:

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

Sign in failures and other issues related to Kerberos authentication

StatusOriginating updateHistory
ResolvedOS Build 22621.819
KB5019980
2022-11-08
Resolved: 2022-11-18, 16:22 PT
Opened: 2022-11-13, 15:16 PT

Updated November 18, 2022: Added update information for Windows Server 2008 R2 SP1.

After installing updates released on November 8, 2022 or later on Windows Servers with the Domain Controller role, you might have issues with Kerberos authentication. This issue might affect any Kerberos authentication in your environment. Some scenarios which might be affected:

When this issue is encountered you might receive a Microsoft-Windows-Kerberos-Key-Distribution-Center Event ID 14 error event in the System section of Event Log on your Domain Controller with the below text. Note: affected events will have "the missing key has an ID of 1":

While processing an AS request for target service <service>, the account <account name> did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of 1). The requested etypes : 18 3. The accounts available etypes : 23 18 17. Changing or resetting the password of <account name> will generate a proper key.

Note: This issue is not an expected part of the security hardening for Netlogon and Kerberos starting with November 2022 security update. You will still need to follow the guidance in these articles even after this issue is resolved.

Windows devices used at home by consumers or devices which are not part of a on premises domain are not affected by this issue. Azure Active Directory environments that are not hybrid and do not have any on premises Active Directory servers are not affected.

Resolution: This issue was resolved in out-of-band updates released November 17, 2022 and November 18, 2022 for installation on all the Domain Controllers (DCs) in your environment. You do not need to install any update or make any changes to other servers or client devices in your environment to resolve this issue. If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them.

To get the standalone package for these out-of-band updates, search for the KB number in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog. Note The below updates are not available from Windows Update and will not install automatically.

Cumulative updates:

Note: You do not need to apply any previous update before installing these cumulative updates. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

Standalone Updates:

Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of November 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released November 8, 2022 to receive the quality updates for November 2022. If you have already installed updates released November 8, 2022, you do not need to uninstall the affected updates before installing any later updates including the updates listed above.

Affected platforms:

  • ​Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • ​Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Direct Access might be unable to reconnect after your device has connectivity issues

StatusOriginating updateHistory
ResolvedOS Build 22621.675
KB5019509
2022-10-18
Resolved: 2022-11-13, 15:34 PT
Opened: 2022-11-13, 14:49 PT

After installing KB5019509 or later updates, you might be unable to reconnect to Direct Access after temporarily losing network connectivity or transitioning between Wi-Fi networks or access points. Note: This issue should not affect other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN).

Windows devices used at home by consumers or devices in organizations which are not using Direct Access to remotely access the organization's network resources are not affected.

Workaround: If you are unable to use the resolution below, you can mitigate this issue by restarting your Windows device.

Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can be resolved by installing and configuring a special Group Policy. 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:

Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue.

Affected platforms:

  • ​Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019
  • ​Server: Windows Server 2022; Windows Server 2019

Connections may fail when using Remote Desktop Connection Brokers

StatusOriginating updateHistory
ConfirmedN/A

Last updated: 2022-11-22, 11:03 PT
Opened: 2022-11-22, 10:47 PT

After installing Windows 11, version 22H2 (also called Windows 11 2022 Update), the Windows Remote Desktop application might stop responding when connecting via a Remote Desktop gateway or Remote Desktop Connection Broker. An example of this connection scenario is when connecting to a Remote Desktop Services collection. RemoteApp and Desktop Connections are ways in which this connection is accomplished.

Home users of Windows are unlikely to experience this issue, as the connection process described here is not the default used by the Windows Remote Desktop app.

This issue can be observed when the client is at the "Loading virtual machine" or "Configuring remote connection" steps, and might occur regardless of the OS version installed on the remote computer. In some cases, the error message "Your Remote Desktop Services session has ended" can appear. If the application becomes unresponsive, it might need to be terminated using Windows Task Manager. See the Workaround section for guidance.

Workaround:

If the Remote Desktop application becomes unresponsive, Windows Task Manager can be used to terminate it.

  • ​Press and hold the Ctrl, Shift, and Esc keys on your keyboard.
  • ​Select Processes from the left-hand side menu
  • ​In the list that appears, find the process mstsc.exe
  • ​Right-click on the process name and select End task

Devices that have encountered this issue can resolve it by configuring a special Group Policy. 

Warning: Remote Desktop sessions which connect over WAN (wide-area network) might experience poor performance following the application of the below workaround. Setting this policy also disables UDP (User Datagram Protocol) for all Remote Desktop connections made from the device. We strongly recommend that this Group Policy change is reverted once this issue is resolved in a future Windows update.
  • ​Open the appropriate Group Policy editor.
    • ​For managed devices (common for enterprises and organizations), open the Group Policy Management Console and create or edit a policy that targets your clients
    • ​For unmanaged devices (common for home users), open the Group Policy Editor. This can be accomplished by opening the Start Menu and typing group policy. Select Edit group policy from the results
  • ​Using the right-side panel, browse to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client
  • ​From the left-side panel, double-click the policy setting Turn Off UDP On Client and set it to Enabled
  • ​Select OK and restart your device(s) to apply the policy setting

Next steps: We are working on a resolution and will provide an update in an upcoming release. 

Affected platforms:

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

October 2022

Domain join processes may fail with error "0xaac (2732)"

StatusOriginating updateHistory
ConfirmedOS Build 22621.674
KB5018427
2022-10-11
Last updated: 2022-10-27, 16:57 PT
Opened: 2022-10-27, 15:53 PT

Domain join operations might intentionally fail with error "0xaac (2732): NERR_AccountReuseBlockedByPolicy" and text "An account with the same name exists in Active Directory. Re-using the account was blocked by security policy."

This issue originates with the October 2022 security updates ( KB5018427) which introduced some hardening changes enabled by default for domain join. Please see KB5020276 - Netjoin: Domain join hardening changes to understand the new designed behavior.

Affected scenarios include some domain join or re-imaging operations where a computer account was created or pre-staged by a different identity than the identity used to join or re-join the computer to the domain.

Home users of Windows are unlikely to experience this issue.

 

Next steps: Please see KB5020276 to understand the designed behavior. We have added insights to this KB, and are evaluating whether optimizations can be made in a future Windows Update. This guidance will be updated once those changes have released.

Affected platforms:

  • ​Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
  • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Provisioning packages might not work as expected

StatusOriginating updateHistory
InvestigatingN/A

Last updated: 2022-10-06, 07:54 PT
Opened: 2022-10-05, 14:17 PT

Using provisioning packages on Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. For more information on provisioning packages, please see Provisioning packages for Windows. Note: Provisioning Windows devices using Windows Autopilot is not affected by this issue.

Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.

Workaround: If you can provision the Windows device before upgrading to Windows 11, version 22H2, this will prevent the issue.

Next steps: We are presently investigating and will provide an update in an upcoming release.

Affected platforms:

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

September 2022

Some installed printers might only allow default settings

StatusOriginating updateHistory
ResolvedN/A

Resolved: 2022-11-18, 17:24 PT
Opened: 2022-09-29, 17:41 PT

Microsoft has found an issue when an installed printer uses Microsoft IPP Class Driver or Universal Print Class Driver and is installed on a Windows device with connectivity issues to the printer. Windows needs connectivity to the printer to identify all the features of the printer. Without connectivity, the printer is set up with default settings and in some scenarios might not get updated once connectivity to the printer is restored. You might be affected by this issue if your printer is unable to use printer specific features such as color, two-sided/duplex printing, paper size or type settings, or resolutions higher than 300x300dpi. Currently, installed printers in this state will carry this issue forward when upgraded to Windows 11, version 22H2. 

To safeguard your upgrade experience, we have applied a compatibility hold on Windows devices with printers using Microsoft IPP Class Driver or Universal Print Class Driver from being offered Windows 11, version 22H2. If your organization is using Update Compliance, the safeguard ID is 41332279. 

Workaround: If you have an affected installed printer, you can use the below workarounds or wait for your device to be mitigated automatically. A troubleshooter has been released which will automatically download and resolve this issue on affected devices. Restarting your device and checking for updates might help the troubleshooter apply sooner. For more information, see keeping your device running smoothly with recommended troubleshooting.

To mitigate the safeguard manually and allow your Windows device to upgrade to Windows 11, version 22H2, you can remove or remove and reinstall any printers using Microsoft IPP Class Driver or Universal Print Class Driver which you have installed. Once you have removed any affected installed printers, you should be able to upgrade to Windows 11, version 22H2. For instructions on how to remove and reinstall printers, please see Download printer drivers in Windows.

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. Restarting your device and checking for updates might help it to offer sooner. 

Resolution: This issue was resolved, and the safeguard hold has been removed as of November 10, 2022. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 11, version 22H2 is offered. 

Important Notes:

  • November 10, 2022: Any printer still affected by this issue should now get resolved automatically during upgrade to Windows 11, version 22H2.
  • October 21, 2022: A troubleshooter has been released which will automatically download and resolve this issue on affected devices running Windows 11, version 22H2. Once the issue with the installed printer is resolved, the safeguard should be removed and you should be able to upgrade to Windows 11, version 22H2. 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. Restarting your device and checking for updates might help the troubleshooter apply sooner. For more information, see keeping your device running smoothly with recommended troubleshooting.
  • October 7, 2022: This safeguard hold has been updated to only safeguard Windows devices with printers using Microsoft IPP Class Driver or Universal Print Class Driver which currently only allow default settings. 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. Restarting your device and checking for updates might help it to offer sooner.

Affected platforms: 

  • ​Client: Windows 11, version 22H2

August 2022

Update might fail to install and you might receive a 0x800f0922 error

StatusOriginating updateHistory
InvestigatingN/A

Last updated: 2022-10-18, 10:04 PT
Opened: 2022-08-12, 17:08 PT

When attempting to install , it might fail to install, and you might receive an error 0x800f0922.

Note: This issue only affects the Security update for Secure Boot DBX () and does not affect the latest cumulative security updates, monthly rollups, or security only updates released on August 9, 2022.

Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install .

Next steps: We are presently investigating and will provide an update in an upcoming release.

Affected platforms:

  • ​Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
  • ​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

November 2021

Compatibility issues with Intel Smart Sound Technology drivers and Windows 11

StatusOriginating updateHistory
Mitigated ExternalN/A

Last updated: 2022-09-22, 17:52 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 will be named Intel® Smart Sound Technology (Intel® SST) Audio Controller under System Devices in Device Manager and have the file name IntcAudioBus.sys and a file version of 10.29.0.5152 or 10.30.0.5152. 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 devices with affected Intel SST drivers from being offered Windows 11, version 22H2 or Windows 11, version 21H2. If your organization is using Update Compliance, the safeguard IDs are:

  • ​Windows 11, version 21H2: 36899911
  • ​Windows 11, version 22H2: 41291788

Workaround: To mitigate the safeguard, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it. This issue is resolved by updating the Intel® Smart Sound Technology drivers to a version 10.30.00.5714 and later or 10.29.00.5714 and later. Important: Later versions refer to just the last part of the version number. For addressing this issue, 10.30.x versions are not newer than 10.29.x versions. 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.

Next Steps: If you encounter this safeguard hold and an updated driver is not yet available, you will need to contact your device manufacturer (OEM) for more information.

Note We recommend that you do not attempt to manually upgrade using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed. 

Affected platforms:

  • ​Client: Windows 11, version 22H2; Windows 11, version 21H2