The Update BureauWindows 11, version 25H2 · Release Health
Known issues in Windows 11, version 25H2
Problems Microsoft has confirmed for this version, from its official release health notes. 19 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.
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.
No known issue matches these filters.