The Update BureauWindows 11, version 24H2 · Release Health
Known issues in Windows 11, version 24H2
Problems Microsoft has confirmed for this version, from its official release health notes. 38 still open or mitigated.
Active known issues
Open & Mitigated-
November security update might fail to install on some devices
Some devices might repeatedly try to install the November security update or show error 0x80070306, 0x800f0989, or 0x800f0993.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5132061 on affected systems until a fix is released.
-
Reports of certain games becoming unresponsive
Some games might freeze, close, show an error, or restart the PC on devices with certain RGB-lighting parts. A block that prevents a related driver from loading mitigates the issue; it does not reach enterprise-managed devices automatically.
How to apply the workaround WorkaroundEnterprise-managed devices do not receive the driver block automatically; IT administrators can apply the mitigation using the steps on the Windows release health site.
-
Microsoft Office applications might fail to open from certain third-party apps
Some third-party apps might fail to open Office apps or documents. Microsoft lists this issue for Windows updates released on or after June 9, 2026.
How to apply the workaround WorkaroundInstall a later Windows update; Microsoft says updates released on or after July 14, 2026 address this issue.
-
May 2026 security update fails to install with error 0x800f0922
Some devices with 10 MB or less free on the EFI System Partition might fail installation with error 0x800f0922 and roll back the update.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5089549 on affected systems until a fix is released.
-
Warnings related to Remote Desktop might not display correctly
Remote Desktop security warnings might show overlapping text or partly hidden buttons when monitors use different display scaling settings.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5082052 on affected systems until a fix is released.
-
Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
Some managed devices might ask for the BitLocker recovery key once, on the first restart after KB5082052. This requires BitLocker on the OS drive, a UEFI policy that includes PCR7, PCR7 binding reported as “Not Possible,” the Windows UEFI CA 2023 certificate in the Secure Boot Signature Database, and a device not already running the 2023-signed Windows Boot Manager.
How to apply the workaround Group PolicyRemoving explicit PCR7 settings lets BitLocker use the Windows-selected default PCR profile.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit4 steps cmd.exe · Administrator Instructions (.txt)Step-by-step procedure- In Group Policy Editor or the Group Policy Management Console, open
Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption > Operating System Drives. - Set
Configure TPM platform validation profile for native UEFI firmware configurationstoNot Configured. - Run
gpupdate /forceto apply the policy change. - If BitLocker is enabled on the C: drive, suspend it and then resume it with the commands below.
> gpupdate /force> manage-bde -protectors -disable C:> manage-bde -protectors -enable C:
- In Group Policy Editor or the Group Policy Management Console, open
-
Signing in with a Microsoft account might fail for Microsoft Teams Free and other apps
Signing in to apps with a Microsoft account might fail, even with a working internet connection. Microsoft lists this as an open issue for this update; Microsoft Entra ID sign-ins are not affected.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5079473 on affected systems until a fix is released.
-
Connection and authentication failures in Azure Virtual Desktop and Windows 365
Microsoft lists connection and sign-in failures with the Windows App on specific Windows builds, affecting Azure Virtual Desktop and Windows 365.
How to apply the workaround WorkaroundKB5077744 addresses this issue.
-
Apps might become unresponsive when saving files to cloud-based storage
Microsoft lists an issue where some apps might hang or show errors when opening or saving files in cloud storage, such as OneDrive or Dropbox.
How to apply the workaround WorkaroundKB5078127 addresses this issue.
-
File Explorer might flash with a white screen in dark mode
After installing KB5070311, File Explorer might briefly show a blank white screen in dark mode before loading files and folders. It might also happen when opening Home or Gallery, making a tab, changing the Details pane, or viewing copy details.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5070311 on affected systems until a fix is released.
-
RemoteApp sessions might fail to start on Azure Virtual Desktop
RemoteApp connections might fail in Azure Virtual Desktop environments after KB5070311. Full desktop sessions are not affected; personal Home and Pro devices are very unlikely to be affected.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5070311 on affected systems until a fix is released.
-
Task Manager might continue running in the background after the app is closed
Task Manager might keep running in the background after you close its window. Multiple lingering instances can use system resources and affect performance.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5067036 on affected systems until a fix is released.
-
Mirror networking on Windows Subsystem for Linux might fail
WSL mirrored networking might fail with some third-party VPNs, including Cisco Secure Client and OpenVPN. You might see “No route to host” and lose access to company resources over VPN; home users are unlikely to be affected.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5067036 on affected systems until a fix is released.
-
USB mouse and keyboard not working in the Windows Recovery Environment
USB keyboards and mice might not work in the Windows Recovery Environment, preventing navigation of its recovery options. They still work normally in Windows.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5066835 on affected systems until a fix is released.
-
IIS websites might fail to load
IIS websites might fail to load on some devices after the listed updates. This can affect 25H2 devices with the September preview update or 24H2 devices with this update.
How to apply the workaround WorkaroundCheck for Windows updates, install any available updates, and restart—even if no updates are available.
Step-by-step workaround instructionsShow steps Hide steps3 stepsStep-by-step procedure- Open Settings and go to Windows Update.
- Search for updates and install any that are available.
- Restart the device, even if no updates were installed.
-
PSDirect connections failing in hotpatched devices
On hotpatched devices with KB5065474 or KB5065426, PowerShell Direct connections might fail when the host and guest virtual machines are not both fully updated.
How to apply the workaround WorkaroundInstall KB5066360 on both the host and guest virtual machines.
-
SMBv1 protocol connectivity
Connections to shared files and folders using SMBv1 over NetBIOS over TCP/IP might fail if either the SMB client or server has the September 2025 security update. SMBv2 and SMBv3 are not affected.
How to apply the workaround WorkaroundInstall KB5065789 or a later update to address the connection problem.
-
Problems playing protected content in some BluRay/DVD/Digital TV apps
After KB5064081 or later, some Blu-ray/DVD or Digital TV apps might fail to play protected content. This affects apps using EVR with HDCP enforcement or DRM for digital audio; streaming services are not affected.
How to apply the workaround WorkaroundKB5065789 and later updates address some EVR and HDCP playback problems. KB5067036 adds improvements for apps using DRM for digital audio.
-
Password icon might be missing or invisible in the lock screen sign-in options
The password icon might be invisible among the lock-screen sign-in options, though its button remains available. This mainly affects enterprise or managed devices; personal Home and Pro devices are very unlikely to be affected.
How to apply the workaround WorkaroundSelect the invisible button's placeholder to open the password box, then enter your password.
-
Install error with error code 0x80240069
Devices managed through WSUS might have failed to install KB5063878 with error 0x80240069. Microsoft says the issue is resolved.
How to apply the workaround WorkaroundIf this happened, refresh and re-sync with WSUS to install the update.
-
Unexpected User Account Control (UAC) prompt when doing MSI repair operations
On this update, standard users might see unexpected UAC prompts during MSI repairs and related operations. Microsoft lists this as a known issue for KB5064080.
How to apply the workaround WorkaroundInstall KB5065431; Microsoft says it addresses this issue.
-
Network Device Interface streaming performance issue
Microsoft lists a streaming performance issue: NDI feeds might have delays or uneven audio and video after KB5063878, especially when Display Capture is enabled. Streaming apps such as OBS Studio and NDI Tools can be affected, even with low bandwidth.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5063878 on affected systems until a fix is released.
-
Error events are logged for CertificateServicesClient
CertificateServicesClient error 57 can appear each time the device restarts, but it does not affect Windows. KB5064081 addresses the event.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5062660 on affected systems until a fix is released.
-
Microsoft Changjie Input Method Editor
After installation, the Changjie input method for Traditional Chinese might not form or select words correctly. The spacebar might not respond, words might appear distorted, or the candidate window might display incorrectly.
How to apply the workaround WorkaroundThe page points to KB5062663 as addressing the issue.
-
Azure VM with Trusted Launch disabled
A small number of Generation 2 Azure virtual machines with Trusted Launch disabled and Virtualization-Based Security enforced through a registry key might fail to boot after installing KB5062553.
How to apply the workaround WorkaroundInstall KB5064489, which addresses this issue.
-
Error events are logged for Windows Firewall
Event Viewer might log Windows Firewall event 2042 after each restart. It can be ignored and has no impact on Windows processes; KB5062660 addresses the event.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5060829 on affected systems until a fix is released.
-
Update delay with deferral policies
Some devices in organizations using quality-update deferral policies might receive the June 2025 security update later than expected. This affects timing, not the update's quality or applicability.
How to apply the workaround WorkaroundAdmins can create an expedite policy with Windows Autopatch or adjust deployment rings or deferral settings to reduce the delay.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- If the organization uses Windows Autopatch, create an expedite policy to bypass deferral settings.
- Alternatively, adjust deployment rings or deferral settings to reduce the delay window.
-
Print to PDF might not work
Enterprise customers and IT admins might find that Microsoft Print to PDF is missing after KB5055627. Enabling its Windows feature might return error 0x800f0922.
How to apply the workaround PowerShellThe commands disable and then re-enable the Microsoft Print to PDF feature.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit2 steps powershell.exe · Administrator Instructions (.txt)Step-by-step procedure- As an alternative, press Windows + R, type optional features, and enable Microsoft Print to PDF in the Windows Features dialog.
- Or open PowerShell as administrator and run the commands in order.
> Disable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features> Enable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features
-
Windows Hello
On devices where System Guard Secure Launch or DRTM is enabled after KB5055523, Windows Hello facial recognition or PIN might stop working after a Push button reset or Reset this PC using Keep my Files and Local install.
How to apply the workaround WorkaroundKB5055627 is listed as addressing this issue.
-
Blue screen exception
After installing KB5053656 and restarting, a blue screen with error code 0x18B might appear.
How to apply the workaround WorkaroundKB5055627 is listed as addressing this issue.
-
Noto fonts issue
At 96 DPI (100% scaling), CJK text might look blurry in Chromium-based browsers such as Microsoft Edge and Google Chrome.
How to apply the workaround WorkaroundIncrease display scaling to improve text clarity. Report remaining Noto CJK font issues through the Google Noto Fonts GitHub repository.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- Increase display scaling to improve clarity.
- If the issue remains, report it through the Google Noto Fonts GitHub repository.
-
Microsoft Copilot
Microsoft Copilot might be removed and unpinned from the taskbar on some devices. Microsoft says the issue is fixed and affected devices are being restored.
How to apply the workaround WorkaroundReinstall Microsoft Copilot from the Microsoft Store and pin it to the taskbar.
-
Open Secure Shell service
Some customers report that the OpenSSH service fails to start after the October 2024 security update, preventing SSH connections. Microsoft lists the issue for this update and is investigating whether Home or Pro users are affected.
How to apply the workaround WorkaroundKB5052093 is listed as the response for this issue.
-
Remote Desktop
On Windows 11, version 24H2, Remote Desktop sessions might freeze shortly after connecting, leaving mouse and keyboard input unresponsive. RDP sessions might also disconnect unexpectedly, including sessions to older Remote Desktop Services hosts.
How to apply the workaround Group PolicyKB5052093 is listed for freezes, and KB5053656 is listed for disconnections. On managed devices using an update earlier than March 27, 2025, administrators can apply the special Group Policy and restart the devices.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- Download the special Group Policy for Windows 11 version 24H2 and configure it under Computer Configuration > Administrative Templates.
- Restart the devices to apply the policy.
-
Roblox
Players on Arm devices cannot download or play Roblox from the Microsoft Store. Roblox is working on a resolution.
How to apply the workaround WorkaroundDownload Roblox directly from Roblox.com.
-
Citrix
Devices with Citrix Session Recording Agent version 2411 might fail to complete installation of the January 2025 Windows security update. Home users are not expected to be affected.
How to apply the workaround WorkaroundUpdate Citrix Session Recording Agent to version 2503 or later; these versions resolve the issue.
-
After installing KB5044384, users will encounter an issue where the number of Apps, Background Processes, and Windows Processes in Task Manager display a count of zero, despite having active applic…
After installing KB5044384, Task Manager will show a count of zero for Apps, Background Processes, and Windows Processes on the Processes page when Group by Type is enabled, even while applications are running.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5044384 on affected systems until a fix is released.
-
We’re aware of an issue where players on Arm devices are unable to download and play Roblox via the Microsoft Store on Windows
Players on Arm devices cannot download or play Roblox through the Microsoft Store on Windows.
How to apply the workaround WorkaroundDownload Roblox directly from www.Roblox.com.
Recently resolved
Fixed in latest updates-
USB audio devices might fail to start or produce no sound
Some USB Audio Class 1.0 devices might fail to start or produce no sound. The 8-channel and 3D audio symptoms are resolved by KB5129194; KB5132059 and later updates resolve the remaining symptoms.
How to apply the workaround WorkaroundSome customers reported restoring audio in multichannel cases by switching to 2-channel mode.
-
Remote Desktop connections might fail for non-admin users with error 0xC000000D
Non-admin users might fail to connect to Remote Desktop hosts with Administrator protection enabled, seeing error 0xC000000D. KB5127653, released October 27, 2026, resolves this issue.
How to apply the workaround Group Policy / IntuneOn affected devices using an update from before October 27, 2026, temporarily turn off Administrator protection by resetting the User Account Control Type Of Admin Approval Mode policy in Intune or Group Policy.
-
File History might stop working after installing September 2026 Windows update
Some File History users might be unable to create or update backups, even when a working backup drive is connected. Updates released on or after September 22, 2026, such as KB5124006, resolve this issue.
Resolution Fixed in KB5126653Install KB5126653 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Devices might experience a black screen or desktop loading issues after sign-in
Some devices, primarily Azure Virtual Desktop hosts using FSLogix, might show a black screen after sign-in or fail to load the desktop automatically. This issue is resolved by updates released October 13, 2026, including KB5127648.
How to apply the workaround Group PolicyBefore installing the resolving update, users can start Explorer manually; enterprise IT can mitigate the issue with Known Issue Rollback and a restart.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- To temporarily start the desktop, open Task Manager, select Run new task, enter
explorer.exe, and select OK. - For enterprise-managed devices, install and configure the applicable Known Issue Rollback Group Policy, then restart the devices.
- To temporarily start the desktop, open Task Manager, select Run new task, enter
-
Applications which require AC-3 audio decoding might close unexpectedly
Some applications that rely on Windows built-in AC-3 (Dolby Digital) audio decoding might fail to launch or close unexpectedly when certain audio features are used. KB5127648 and later updates resolve this issue.
Resolution Fixed in KB5127648Install KB5127648 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
You might be unable to turn on Smart App Control
Some devices cannot turn Smart App Control back on after it was turned off; its setting might be grayed out.
How to apply the workaround Registry / GPOThe values restore the ability to turn on Smart App Control.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit3 steps cmd.exe · Administrator Power-User Kit (.zip)Step-by-step procedure- Back up the registry before making changes.
- Open Command Prompt as an administrator and run both commands.
- Restart the device.
> reg add "HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" /v 2883193997 /t REG_DWORD /d 1 /f> reg add "HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" /v 2850574478 /t REG_DWORD /d 1 /f
-
Domain-joined devices might lose their secure trust relationship with the domain
Some Credential Guard protected machine accounts might lose their secure connection to an on-premises domain, blocking interactive sign-in. KB5124006 and later updates resolve this issue.
How to apply the workaround Group Policy / IntuneThe rollback or disabling Machine Identity Isolation stops its enforcement, which prevents the affected domain trust problem. The rollback policy must be set to Disabled, and the device must be restarted.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit4 steps powershell.exe · Administrator Power-User Kit (.zip)Step-by-step procedure- For the rollback option, install the special Group Policy for Windows 11, version 26H1, set its KB5124012 rollback policy to Disabled, and restart the devices.
- Alternatively, disable Machine Identity Isolation using the same method that enabled it: Intune policy, Group Policy, or the registry.
- If using the registry, check either listed key. Change
MachineIdentityIsolationfrom 2 to 0 only when its current value is 2. - Restart the device, then repair the secure channel with the PowerShell command.
> Test-ComputerSecureChannel -Repair -Credential (Get-Credential) -
Remote Desktop Services might stop responding after September 2026 security update
Some organizations might see Remote Desktop connections fail, sign-in problems, or unresponsive tools and servers. Updates released on or after September 14, 2026, such as KB5129194, resolve this issue. Windows 365 and Azure Virtual Desktop are not affected.
Resolution Fixed in KB5129194Install KB5129194 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Host folder shares might be unavailable in Hyper-V-based Linux VMs
Host folders shared with some Linux virtual machines might not appear or open. Updates released on or after September 14, 2026, such as KB5129194, resolve this issue.
Resolution Fixed in KB5129194Install KB5129194 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Desktop background settings are lost or reset on some devices
Some devices might show a solid black desktop background after desktop settings fail to load; slideshow and contrast theme settings might also be affected. This issue is resolved by updates released on or after September 8, 2026, including KB5124008.
Resolution Fixed in KB5124008Install KB5124008 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Microsoft Teams and Outlook might fail to launch on ARM-based devices
On ARM-based PCs, Teams and the new Outlook might fail to start or close unexpectedly, especially on new PCs without Store updates. Windows updates from September 8, 2026, such as KB5124012, resolve this.
How to apply the workaround WorkaroundInstall version 1.0.19.0 or later of the Auto Super Resolution Package from Microsoft Store. This is a workaround; Windows updates from September 8, 2026, such as KB5124012, resolve the issue.
Step-by-step workaround instructionsShow steps Hide steps3 stepsStep-by-step procedure- Open Microsoft Store.
- Select Downloads > Check for updates.
- Install the latest update for the Auto Super Resolution Package, version 1.0.19.0 or later.
-
Mouse customization is reset on non-English Windows devices
Mouse personalization settings, including cursor and cursor animations, might reset on non-English Windows installations. This issue is resolved by updates released on or after September 8, 2026, including KB5124008.
Resolution Fixed in KB5124008Install KB5124008 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Deleting from Recycle Bin displays an internal file name
When you permanently delete one item, the confirmation box might show an internal file name instead of the original. Microsoft lists this issue for this update.
How to apply the workaround WorkaroundInstall KB5095093, which Microsoft says addresses this issue.
-
Installation of KB5079391 might fail with error 0x80073712
Some devices might encounter error 0x80073712 while installing KB5079391. KB5086672 addresses the issue.
Resolution Fixed in KB5086672Install KB5086672 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections
After the October 2024 security update, the OpenSSH service might fail to start, preventing SSH connections. The issue affected a limited number of enterprise, IoT, and education devices and was addressed by KB5052094.
Resolution Fixed in KB5052094Install KB5052094 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing this security update, you might experience issues with USB cameras
A USB camera might not be recognized as on after installing the update. KB5050092 addresses this issue.
Resolution Fixed in KB5050092Install KB5050092 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing this security update, you might experience issues with USB audio devices
USB audio devices, especially devices using a USB 1.0 audio driver-based DAC, might stop working and prevent audio playback. KB5050092 addresses this issue.
Resolution Fixed in KB5050092Install KB5050092 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Devices that have certain Citrix components installed might be unable to complete installation of the January 2025 Windows security update
Devices with certain Citrix components, including Citrix Session Recording Agent version 2411, might fail to complete installation of the January 2025 security update and revert changes. The issue is resolved in Citrix Session Recording Agent version 2503 and newer.
How to apply the workaround WorkaroundUpdate Citrix Session Recording Agent to version 2503 or newer.
-
After a fresh install or an In-place upgrade to Windows 11, version 24H2, you might face issues with connecting via [DirectAccess](https://learn.mi…
After a fresh install or in-place upgrade to version 24H2, some enterprise devices might get stuck connecting through DirectAccess. KB5044384 resolves this issue.
How to apply the workaround WorkaroundUntil a fix became available, Microsoft recommended that enterprises needing DirectAccess evaluate Always On VPN.
No known issue matches these filters.