Windows 10, version 22H2
Find information on known issues and the status of the Windows 10, 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. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
- Check if your current Windows 10 PC can upgrade to Windows 11.
- Purchase a new Windows 11 PC.
- Purchase Extended Security Updates (ESU) for organizations of all sizes as previously announced in April of this year.
- For the first time, purchase an ESU option for individuals.
Known issues
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| AVD users might experience extended black screen during logon and SSO failures This issue affects enterprise users using FSLogix user profile containers on multi-session environments. | OS Build 19045.4717 KB5040525 2024-07-23 | Confirmed | 2024-11-01 14:25 PT |
| Apps that set UIAccess=true might fail to start for non-admin users This issue is due to child processes of these apps running with Integrity level low instead of Integrity level medium | OS Build 19045.4957 KB5043131 2024-09-24 | Mitigated | 2024-10-30 13:19 PT |
| Azure Virtual Desktop users might experience black screen during login This issue affects enterprise users with multi-session environments due to issues with AppX Deployment Service | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved KB5045594 | 2024-10-22 10:16 PT |
| August 2024 security update might impact Linux boot in dual-boot setup devices This issue might impact devices with dual-boot setup for Windows and Linux when SBAT setting is applied | OS Build 19045.4780 KB5041580 2024-08-13 | Mitigated | 2024-09-20 12:41 PT |
Issue details
November 2024
AVD users might experience extended black screen during logon and SSO failures
| Status | Originating update | History |
|---|---|---|
| Confirmed | OS Build 19045.4717 KB5040525 2024-07-23 | Last updated: 2024-11-01, 14:25 PT Opened: 2024-11-01, 14:11 PT |
After installing the July 2024 non-security preview update (KB5040525), released July 23, 2024, or subsequent updates, you might experience an extended black screen that stays between 10 to 30 mins when you login to Azure Virtual Desktop (AVD). Additional symptoms you might experience include:
- Failures related to single sign-on (SSO) experience on Office applications such as Outlook and Teams, which could prevent you from connecting to backend services or synchronizing data.
- Office apps display losing network connectivity even though other applications, such as Edge, retain intranet and internet access.
This issue is caused by a deadlock in the interactions between the Azure Active Directory(AAD) broker and the underlying AppX deployment service(AppxSvc) and Background tasks infrastructure service.You are more likely to experience this issue if you are using FSLogix user profile containers on multi-session environments. FSLogix is a Microsoft tool that helps manage and speed up user profiles on computers, especially in virtual environments like remote desktops.
Please note that this issue is different from the scenario where the AppX Deployment Service (AppxSvc) was in an invalid state, causing a black screen. That issue was resolved with Windows updates released on October 22, 2024 (KB5045594), and later.
Windows 10 Education edition users and home users of Windows using Home or Pro editions are unlikely to face this issue as Azure Virtual Desktop is more commonly used in enterprise environments.
Next Steps: We are investigating the issue and provide an update where more information is available.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
October 2024
Apps that set UIAccess=true might fail to start for non-admin users
| Status | Originating update | History |
|---|---|---|
| Mitigated | OS Build 19045.4957 KB5043131 2024-09-24 | Last updated: 2024-10-30, 13:19 PT Opened: 2024-10-30, 12:45 PT |
After installing the September 2024 preview update (KB5043131), released September 24, 2024 or later, you might observe that apps such as Quick Assist, Microsoft Teams, Windows Narrator, etc might fail to start if you are a non-admin user. You might experience this issue on any app that sets UIAccess=true while trying to run the app as a non-admin user. The uiAccess=true attribute in an application's manifest file is used to request that the application be granted higher privileges. Apps using this attribute launch from a secure path, such as :
- %ProgramFiles% (including subdirectories)
- %ProgramFiles(x86)% (including subdirectories for 64-bit versions of Windows)
- %systemroot%\system32
- %systemroot%\syswow64 (for 64-bit versions of Windows)
If you have the Procmon monitoring tool installed in your device, you will observe that the application runs with the wrong integrity level, Integrity:Low instead of the expected Integrity:Medium. You are less likely to encounter this issue if you are running the application as an administrator.
Resolution: This issue is mitigated 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 and business devices that are not managed by IT departments. Restarting your Windows device might help the resolution apply to your device faster.
For enterprise-managed devices managed by IT departments that have installed the affected update and encountered this issue, IT administrators can resolve it by installing and configuring the 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 10, version 22H2 – Windows 10 20H2, 21H1, 21H2 and 22H2 KB5041582 241027_11353 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.
Note: The below steps apply to enterprise devices that are domain joined.
- Wait for the KIR group policy changes to replicate in Active Directory and the SYSVOL
- Follow one of the steps below before applying the KIR:
- Wait for group policy to refresh in the background then restart your device (or)
- Run ‘gpupdate /force’ from a command prompt then restart your device
Next Steps: We are working on a resolution and will provide more information when it is available.
Affected platforms:
- Client: Windows 10, version 22H2
- Server: None
Azure Virtual Desktop users might experience black screen during login
| Status | Originating update | History |
|---|---|---|
| Resolved KB5045594 | OS Build 19045.4717 KB5040525 2024-07-23 | Resolved: 2024-10-22, 10:00 PT Opened: 2024-10-14, 11:48 PT |
After installing the July 2024 non-security preview update (KB5040525), released July 23, 2024 or subsequent updates, you might experience a black screen when you login to Azure Virtual Desktop (AVD). You might also notice that you are unable to log out of your account and the black screen persists even after disconnecting and reconnecting to AVD. Resulting from this issue, the application event log in Event viewer will show an application error with Event ID:1000 indicating a fault with the application ‘svchost.exe_AppXSvc’.
Please note that AppX Deployment Service (AppxSvc) being in an invalid state could also cause other symptoms like the Start Menu to close unexpectedly due to registration issues.
Windows 10 Education edition users and home users of Windows using Home or Pro editions are unlikely to face this issue as Azure Virtual Desktop is more commonly used in enterprise environments.
Resolution: This issue was resolved by Windows updates released October 22, 2024 (KB5045594), and later. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one.
If you install an update released October 22, 2024 (KB5045594) 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 October 22, 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 10, version 22H2 - Windows 10 20H2, 21H1, 21H2 and 22H2 KB5040525 241001_01051 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 10, version 22H2
- Server: None
August 2024
August 2024 security update might impact Linux boot in dual-boot setup devices
| Status | Originating update | History |
|---|---|---|
| Mitigated | OS Build 19045.4780 KB5041580 2024-08-13 | Last updated: 2024-09-20, 12:41 PT Opened: 2024-08-21, 18:33 PT |
After installing the August 2024 Windows security update, (KB5041580) or the August 2024 preview update, you might face issues with booting Linux if you have enabled the dual-boot setup for Windows and Linux in your device. Resulting from this issue, your device might fail to boot Linux and show the error message “Verifying shim SBAT data failed: Security Policy Violation. Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation.”
The August 2024 Windows security and preview updates apply a Secure Boot Advanced Targeting (SBAT) setting to devices that run Windows to block old, vulnerable boot managers. This SBAT update will not be applied to devices where dual booting is detected. On some devices, the dual-boot detection did not detect some customized methods of dual-booting and applied the SBAT value when it should not have been applied.
IMPORTANT: This known issue only occurs with the installation of the August 2024 security and preview updates. The September 2024 security update (KB5043064) and later updates do not contain the settings that caused this issue. If you install the September 2024 update, you don’t need to apply the workaround below.
Workaround:
If your Linux becomes unbootable after installing the August 2024 security or preview updates, you can recover your Linux system by following these instructions.
Important: This documentation contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see How to back up and restore the registry in Windows. Also, note that modifying firmware settings incorrectly might prevent your device from starting correctly. Follow these instructions carefully and only proceed if you are confident in your ability to do so.
- Boot into your device’s firmware settings.
- Disable Secure Boot (steps vary by manufacturer).
- Boot into Linux.
- Open the terminal and run the below command:
sudo mokutil --set-sbat-policy delete
- Enter your root password if prompted.
- Boot into Linux once more.
- In the terminal, run the below command:
mokutil --list-sbat-revocations
- Ensure the list shows no revocations.
- Reboot into the firmware settings.
- Re-enable Secure Boot.
- Boot into Linux. Run the below command:
mokutil --sb-state
- The output should be “SecureBoot enabled”. If not, retry step d).
- Boot into Windows.
- Open Command Prompt as Administrator and run:
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\SBAT /v OptOut /d 1 /t REG_DWORD
At this point, you should now be able to boot into Linux or Windows as before. It’s a good time to install any pending Linux updates to ensure your system is secure.
NOTE: On Windows-only systems, after installing the September 2024 or later updates, you can set the registry key documented in CVE-2022-2601 and CVE-2023-40547 to ensure the SBAT security update is applied. On systems that dual-boot Linux and Windows, there are no additional steps necessary after installing the September 2024 or later updates.
Next Steps: We are working on a final resolution that will be available in a future Windows update. We recommend you install the September 2024 update or later Windows updates to avoid this issue.
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 Enterprise 2015 LTSB
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
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.