Windows 11, version 22H2 known issues and notifications

Find information on known issues and the status of the Windows 11, version 22H2 rollout. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates.

Current status as of September 26, 2023

Microsoft is delivering a new wave of continuous innovation to eligible Windows 11, version 22H2 devices with new experiences and AI capabilities. You can access these experiences as soon as they’re ready for your device by navigating to Settings > Windows Update and turning on the toggle to Get the latest updates as soon as they're available.  

Note: To see the toggle, you must be using a Home or Pro device running Windows 11, version 22H2 with all the latest updates installed. The toggle won't be enabled for devices managed by an organization unless the IT department has enabled optional updates (including CFRs) using policy. 

Known issues

See open issues, content updated in the last 30 days, and information on safeguard holds. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge).

Summary Originating update Status Last updated
The February 2024 security update might fail to install
Some users reported the update’s download stops at 96% and fails to install on Windows 11 versions 22H2 and 23H2.
OS Build 22621.3155
KB5034765
2024-02-13
Resolved
KB5035853
2024-03-14
17:32 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 22621.1928
KB5027303
2023-06-27
Resolved
KB5034204
2024-02-28
11:09 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

Mitigated
2023-10-31
10:06 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
2023-10-31
10:06 PT

Issue details

February 2024

The February 2024 security update might fail to install

Status Originating update History
Resolved KB5035853 OS Build 22621.3155
KB5034765
2024-02-13
Resolved: 2024-03-12, 10:00 PT
Opened: 2024-02-26, 12:58 PT

Windows 11 devices attempting to install the February 2024 security update, released February 13, 2024 (KB5034765), and the non-security preview update, released February 29, 2024 (KB5034848), might face issues during the update process. The installation might fail when the update's download reaches 96% of completion, and the device might roll back to the previous update installed.

Resulting from this error, the following message might be displayed:

  • ​“Something didn’t go as planned. No need to worry – undoing changes. Please keep your computer on”.

This issue might be reflected in the Windows Event Viewer with error code ‘0x800F0922’.

Resolution: This issue was resolved in updates released March 12, 2024 (KB5035853) 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 are using an update released before March 12, 2024, and have this issue, you can resolve it by applying the workaround listed below.

Workaround:

This issue can be prevented by deleting the hidden folder C:\$WinREAgent. A restart might be required. After following these steps, installing the February 2024 security update should succeed.  

Below are two possible ways to delete the C:\$WinREAgent folder.

1) Manually delete the folder: To delete a hidden folder in Windows 11, you need to first make the folder visible and then delete it.

  1. Open File Explorer from the Taskbar, or by pressing Windows key + E.
  2. ​Click on the three-dotted icon and select Options.
  3. ​Go to the View tab and select the Show hidden files, folders, and drives option. Click the OK button to save the change.
  4. ​Now, you should be able to see the hidden folder C:\$WinREAgent in File Explorer. Right-click the hidden folder C:\$WinREAgent and select Delete.

2) Run a script to delete the folder:

  1. ​Open the start menu and type command prompt.
  2. ​From the results displayed at the right side of the start menu, select ‘Run as administrator’.
  3. ​On the command prompt, type the command rd /s /q "C:\$WinREAgent" and press enter.
  4. ​If no message is displayed, it means the command has succeeded and the folder has been deleted. You can proceed to close the command prompt window.
    1. ​Note that a message is only displayed if an error was encountered. In this case, we recommend deleting the folder manually.

Affected platforms:

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

October 2023

BitLocker might incorrectly receive a 65000 error in MDMs

Status Originating update History
Mitigated N/A

Last updated: 2023-10-31, 10:06 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.

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

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

July 2023

Some apps might fail to playback, record, or capture video

Status Originating update History
Resolved KB5034204 OS Build 22621.1928
KB5027303
2023-06-27
Resolved: 2024-01-23, 14:00 PT
Opened: 2023-07-25, 14:47 PT

After installing KB5027303 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 January 23, 2024 (KB5034204) 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 January 23, 2024 (KB5034204) 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 January 23, 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:

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

November 2021

Compatibility issues with Intel Smart Sound Technology drivers and Windows 11

Status Originating update History
Mitigated External N/A

Last updated: 2023-10-31, 10:06 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 23H2, Windows 11, version 22H2, or Windows 11, version 21H2 on devices with Windows 10. If your organization is using Update Compliance, the safeguard IDs are:

  • ​Windows 11, version 21H2: 36899911
  • ​Windows 11, version 23H2; 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 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.