The Update BureauWindows 11, version 23H2 · Release Health
Known issues in Windows 11, version 23H2
Problems Microsoft has confirmed for this version, from its official release health notes. 23 still open or mitigated.
Active known issues
Open & Mitigated-
OneDrive shortcut in File Explorer might not work in administrator mode
The OneDrive shortcut in File Explorer might not work when File Explorer runs with administrative privileges. The issue affects the built-in Administrator account or apps run as administrator.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5093998 on affected systems until a fix is released.
-
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.
-
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
-
Some devices with Virtual Secure Mode enabled might fail to shut down or hibernate
Microsoft lists this as a known issue: Some Secure Launch-capable PCs with Virtual Secure Mode enabled restart instead of shutting down or hibernating.
How to apply the workaround WorkaroundKB5075941 and all updates released after February 10, 2026 fully resolve the issue. An earlier fix in KB5077797 helped some Secure Launch devices.
-
Secure Launch-capable devices might fail to shut down or hibernate
Some Secure Launch-capable PCs restart instead of shutting down or entering hibernation. Microsoft says KB5075941 and later updates resolve the issue.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5073455 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.
-
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.
-
Reset and recovery issue
After installing KB5063875, attempts to reset or recover the device might fail. This can affect Reset my PC, Fix problems using Windows Update, or RemoteWipe CSP.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5063875 on affected systems until a fix is released.
-
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.
-
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.
-
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.
-
Recovery error with error code 0xc0000098
Some devices might show a repair error with code 0xc0000098 during installation and fail to start. This has affected a small number of physical devices, but mostly virtual machines.
How to apply the workaround WorkaroundIf the update is not deployed yet in a virtual desktop environment, use KB5062170 instead. If Windows will not start, recover the device, then install KB5062170.
Step-by-step workaround instructionsShow steps Hide steps6 stepsStep-by-step procedure- For a device with Windows Recovery enabled, open the Windows Recovery Environment, then restart Windows.
- For a device without Recovery enabled, mount its virtual hard disk from a remote device.
- Attach the virtual hard disk as a data disk to another virtual machine or device, then return it to the affected machine.
- Restart Windows normally; this reverts Windows to the last successfully installed update.
- For Azure devices, follow the repair steps in the Azure virtual machine repair guidance.
- After recovery, install KB5062170 from the Microsoft Update Catalog.
-
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.
-
Active Directory Group Policy: Events in local policy
Local Active Directory Group Policy might report that Audit logon events is set to No auditing even when the policy is enabled and logon events are being audited. KB5058919 resolves this reporting issue.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5055528 on affected systems until a fix is released.
-
Windows 11, versions 24H2 might not download via Windows Server Updates Services
Some enterprise devices with the April 8, 2025 update or later might not download Windows 11, version 24H2, through Windows Server Update Services. The log might show error 0x80240069.
How to apply the workaround Group PolicyFor affected devices on an update released before May 13, 2025, an IT admin can install and configure the special Group Policy.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- If the device has KB5058405 or a later update, no special policy is needed.
- For an affected device on an earlier update, have an IT admin install and configure the special Group Policy.
-
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.
-
USB Printer Issue
Some USB-connected dual-mode printers might print random text and data, including network commands. This happens more often when the printer is turned on or reconnected.
How to apply the workaround WorkaroundInstall KB5053657, which addresses the printer issue.
-
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.
-
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 this security update, you might face issues with booting Linux if you have enabled the dual-boot setup for Windows and Linux in your device
Some devices set up to dual-boot Windows and Linux might fail to boot Linux after the August 2024 Windows security update. The error can report “Verifying shim SBAT data failed: Security Policy Violation.” Microsoft says the security update applied an SBAT setting when some customized dual-boot setups were not detected.
How to apply the workaround WorkaroundInstall the September 2024 Windows security update or a later update. Dual-boot systems need no additional steps afterward; Windows-only systems can set the registry key documented in the linked CVE articles.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- Install the September 2024 Windows security update or a later update.
- On Windows-only systems, set the registry key documented in the CVE-2022-2601 and CVE-2023-40547 articles.
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.
-
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.
-
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.
-
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.
-
After installing KB5050092, you might observe issues with USB connected dual-mode printers that support both USB Print and IPP Over USB protocols
After installing KB5050092, some USB-connected dual-mode printers might print random text and data, including network commands. KB5053657 resolves this issue.
Resolution Fixed in KB5053657Install KB5053657 (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 installing KB5043145, some customers have reported that their device restarts multiple times or becomes unresponsive with blue or green screens
After installing KB5043145, some devices might restart multiple times or become unresponsive with blue or green screens. Some might open Automatic Repair after repeated restart attempts, and BitLocker recovery might be triggered. KB5044285 addresses this issue.
Resolution Fixed in KB5044285Install KB5044285 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing the July 9, 2024, Windows security update, you might see a [BitLocker recovery](https://learn.microsoft.com/windows/security/operating-system-security/data-protection/bitlocker/recov…
After the July 9, 2024 Windows security update, some devices might show a BitLocker recovery screen at startup, especially when Device Encryption is enabled. KB5041585 resolves this issue.
Resolution Fixed in KB5041585Install KB5041585 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing KB5039302, you might face issues using Windows Update Agent API (WUA) from your script (PowerShell, VBScript, etc.) while sea…
On Enterprise devices, scripts using the Windows Update Agent API might return empty update properties or error 0x8002802B. KB5040527 resolves this issue.
Resolution Fixed in KB5040527Install KB5040527 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing KB5036893 or later updates, you might face issues while upgrading from Windows Pro to a valid Windows Enterprise subscription.Resulting from this operation, you might observe the f…
After KB5036893 or later updates, upgrading from Windows Pro to a valid Windows Enterprise subscription might fail with an access denied error (0x80070005) in the LicenseAcquisition scheduled task. KB5040527 addresses the issue.
Resolution Fixed in KB5040527Install KB5040527 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing KB5039302, some devices might fail to start
Some devices might fail to start, repeatedly restart, and require recovery, especially devices using virtual machine tools and nested virtualization. KB5040442 and later resolve this issue.
Resolution Fixed in KB5040442Install KB5040442 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing KB5037853, you might face issues during the install process
On Windows virtual machines running on Arm-based Mac devices, installation might fail during restart and roll back to the previous update. KB5039212 resolves this issue.
Resolution Fixed in KB5039212Install KB5039212 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing KB5037853, you might face issues using the taskbar
The taskbar might temporarily glitch, stop responding, disappear, or reappear after installing KB5037853. The issue is resolved by KB5039212.
Resolution Fixed in KB5039212Install KB5039212 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
After installing KB5036893, you might be unable to [change your user account profile picture](https://support.microsoft.com/en-us/windows/change-your-account-picture-3645cdc7-acab-49d2-76a9-4ce7e5e…
After installing KB5036893, you might be unable to change your user account profile picture. Choosing a file in Settings might show error 0x80070520; KB5037853 addresses the issue.
Resolution Fixed in KB5037853Install KB5037853 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Windows devices might face VPN connection failures after installing the update dated April 9, 2024, or later
Windows devices might have VPN connection failures after installing the update dated April 9, 2024, or later. KB5037771 addresses the issue.
Resolution Fixed in KB5037771Install KB5037771 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Windows 11 devices attempting to install the February 2024 security update, released February 13, 2024 (KB5034765), might face issues during the update process
The update installation might fail when the download reaches 96%, and the device might roll back to its previous update. The issue might appear in Event Viewer with error code 0x800F0922. KB5035853 addresses it.
Resolution Fixed in KB5035853Install KB5035853 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
The color font format for COLRv1 does not render properly
The COLRv1 color font format might not render properly, affecting emoji with a 3D-like appearance. KB5034204 addresses the issue.
Resolution Fixed in KB5034204Install KB5034204 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Using the FixedDrivesEncryptionType or [SystemDrivesEncryptionType](https://nam06.safelinks.protec…
In some managed environments, the “Require Device Encryption” setting might incorrectly show error 65000 when BitLocker policies require full encryption or used-space-only encryption. This is a reporting issue only and does not affect drive encryption. KB5034204 addresses the issue.
Resolution Fixed in KB5034204Install KB5034204 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Window…
On devices using more than one monitor, desktop icons might move unexpectedly or become misaligned when using Copilot in Windows (preview). The issue is addressed on the service side for versions 22H2 and 23H2 on devices with updates released January 9, 2024, or later. Managed devices used in a multimonitor configuration do not yet have Copilot for Windows available.
Resolution ResolvedMicrosoft has resolved this issue in a subsequent update. No manual workaround is required after updating.
No known issue matches these filters.