Release Health & Mitigations
Known issues
Problems Microsoft has confirmed for the products we follow, from its official release health notes. 117 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.
-
SQL Server linked server connections might remain open
SQL Server linked-server queries using OLE DB providers might leave connections to external databases open after queries finish. Connections can build up and slow server performance over time; Oracle and PostgreSQL are among the known affected connections.
How to apply the workaround WorkaroundFor an enterprise mitigation, contact Microsoft Support for business. Closing identified idle connections or restarting the SQL service can temporarily ease the load, but might interrupt active work and the issue can return.
-
A ContentEngine deadlock occurs because of missing Korean WordBreaker rule files
The KB lists a deadlock linked to missing Korean WordBreaker files. Search results might be missing, mail delivery might be delayed, or Outlook might stall or disconnect.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5129955 on affected systems until a fix is released.
-
Some Master Data Services features might not work as expected
After installing KB5104824, creating an entity or attribute in Master Data Services, or loading hierarchies in Explorer, might not work as expected.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5104824 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.
-
Availability (free/busy) fails for delegated mailboxes in Exchange hybrid deployments using Graph API only
In some Exchange hybrid setups, checking a delegated mailbox's availability might show an error or no details. This affects Graph API-only setups; Microsoft says the service fix is available.
How to apply the workaround Exchange Management ShellThe override enables the Graph API route for availability checks. Refreshing Variant Configuration applies the change immediately.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit3 steps Exchange Management Shell Instructions (.txt)Step-by-step procedure- Check the current value of the override.
- Only if it is
Enabled=Falseor was previously disabled, set it toEnabled=True. - Run the refresh command to apply the change immediately.
> Get-SettingOverride -Identity EnableRouteThroughMSGraphFeature> Set-SettingOverride -Identity EnableRouteThroughMSGraphFeature -Parameters "Enabled=True"> Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh
-
Published calendar (.ics) returns HTTP 500 for calendar applications
After KB5121573, subscriptions to anonymously published Exchange calendars might stop refreshing. Calendar apps might receive an HTTP 500 error.
How to apply the workaround IIS / URL RewriteAdd a URL Rewrite rule to the Exchange Back End site. It adds
layout=premiumto calendar-feed requests that do not already have a layout parameter.Step-by-step workaround instructionsShow steps Hide steps5 stepsStep-by-step procedure- Confirm that the IIS URL Rewrite module is installed.
- In IIS Manager, add a blank inbound rule to the Exchange Back End site's URL Rewrite settings.
- Match
^owa/calendar/.+\.ics$and add a condition that excludes requests whose query string already containslayout=. - Rewrite the URL to
{R:0}?layout=premium&{QUERY_STRING}; clear Append query string. - Apply the rule on every server that serves the published calendar. No application pool recycle is required.
-
Access violation when you query sys.dm_exec_requests during database recovery
Queries against
sys.dm_exec_requestsmight cause an access violation and create a dump file while a database is recovering. This can happen during restore, startup recovery, or before an availability group replica comes online.How to apply the workaround SQL Trace FlagEnable trace flag 4696, avoid queries against recovering databases, or uninstall the update. With the trace flag, monitoring queries on secondary replicas might return errors 976 or 978.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- Enable trace flag 4696 to opt out of the code change.
- Alternatively, avoid queries against
sys.dm_exec_requestsfor databases that are recovering, or uninstall the update.
-
Wrapper messages appear in shared mailbox in hybrid environments after installing the June 2026 Security Update
In Exchange hybrid, sent messages might appear as attachments in an Exchange Online shared mailbox Inbox. With an on-premises sender, Send As or Send on Behalf rights, and message-copy enabled, this occurs; KB5121608 resolves it.
How to apply the workaround Exchange Management ShellThe article says to remove the override if it was created as a workaround for this issue.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit2 steps Exchange Management Shell Instructions (.txt)Step-by-step procedure- In Exchange Management Shell, check whether the override exists.
- If it exists, remove it.
> Get-SettingOverride "DisableBlockSharedAndUserMailboxHeaders"> Remove-SettingOverride "DisableBlockSharedAndUserMailboxHeaders"
-
After you run PSConfig, run the following PowerShell commands
After PSConfig, run the listed PowerShell commands to avoid a possible regression from a defense-in-depth feature under development.
How to apply the workaround PowerShellThe setting disables the defense-in-depth check that may cause a regression. Existing actor token validation checks remain in place.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit1 step powershell.exe · Administrator Instructions (.txt)Step-by-step procedure- After running PSConfig, run the three PowerShell commands.
> $farm = Get-SPFarm> $farm. DisableActorTokenAudienceValidation = $true #disables only the defense-in-depth validation> $farm.update ()
-
Customers who install the SharePoint 2016 July Public Update might find that Office Online Server can't render or edit documents
After installing the July public update, Office Online Server might not render or edit documents.
How to apply the workaround SharePoint Management ShellThe workaround trusts the farm's public signing certificate so Office Online Server can render and edit documents.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit4 steps SharePoint Management Shell Instructions (.txt)Step-by-step procedure- Get the STS signing certificate and export its public certificate to
STS_Public.cer. - Check that
$pub.HasPrivateKeyreturnsFalse. - Register the public certificate as a trusted token issuer.
- Run
iisreseton every SharePoint server in the farm.
> $stsm = Get-SPSecurityTokenServiceConfig> $live = $stsm.LocalLoginProvider.SigningCertificate> $bytes = $live.Export("Cert")> $tempFile = "$env:TEMP\STS_Public.cer"> Set-Content -Path $tempFile -Value $bytes -Encoding Byte> $pub = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2($tempFile)> $pub.HasPrivateKey> $realm = $stsm.NameIdentifier> New-SPTrustedSecurityTokenIssuer ` -Name "LocalSelfIssuerWopiFix" ` -Description "Re-trust farm self-issuer after July PU" ` -Certificate $pub ` -RegisteredIssuerName $realm> iisreset
- Get the STS signing certificate and export its public certificate to
-
When a workflow status link is selected, WrkStat.aspx displays the following error message: The WorkflowInstanceID parameter is invalid
Selecting a workflow status link can make
WrkStat.aspxshow “The WorkflowInstanceID parameter is invalid.”How to apply the workaround WorkaroundFollow Microsoft's linked guidance for workflow status links.
-
Customers in multi-front-end SharePoint farms with Trusted Provider or Forms authentication may face repeated authentication prompts or multiple sign-ins
Multi-front-end farms using Trusted Provider or Forms authentication might show repeated sign-in prompts. Farms using Windows authentication should not be affected.
How to apply the workaround WorkaroundConfigure sticky sessions on the reverse proxy; this addresses most reported scenarios.
-
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.
-
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.
-
Warnings related to Remote Desktop might not display correctly
After installing KB5082063, Remote Desktop file security warnings might show overlapping text or partly hidden buttons when monitors use different scaling settings.
How to apply the workaround WorkaroundKB5087545 addresses this warning display issue.
-
Devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key
A limited set of managed devices might ask for the BitLocker recovery key on the first restart after installation. This can happen when BitLocker is on the OS drive, PCR7 is included in the configured profile or equivalent registry setting, System Information reports PCR7 binding as “Not Possible,” the Windows UEFI CA 2023 certificate is in the Secure Boot DB, and the device does not yet use the 2023-signed Windows Boot Manager.
How to apply the workaround Group PolicyRemoving the explicit PCR7 setting lets Windows use its selected default PCR profile. Suspending and resuming BitLocker updates its bindings.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit4 steps cmd.exe · Administrator Instructions (.txt)Step-by-step procedure- Before installing the update, open Group Policy Editor or the Group Policy Management Console.
- Go to
Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption > Operating System Drivesand setConfigure TPM platform validation profile for native UEFI firmware configurationstoNot Configured. - Run
gpupdate /forceon affected devices. - Where BitLocker is enabled on the C: drive, run the suspend command, then the resume command.
> gpupdate /force> manage-bde -protectors -disable C:> manage-bde -protectors -enable C:
-
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
-
Availability group listener error 10013 in error log
When the SQL Server service starts or an availability group fails over, listener-related errors might appear in the error log. Creating a listener might also produce an error that its TCP port is already in use. The messages do not affect functionality, and listener connections continue to work.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5080999 on affected systems until a fix is released.
-
Linked server queries that use MSDASQL fail with error 7416
Linked-server queries using the
MSDASQLprovider and a provider string might fail with error 7416, reporting that no login mapping exists. The Database Engine's stricter connection validation can reject certain configurations that worked in earlier builds.How to apply the workaround WorkaroundUse the workaround guidance in the linked Microsoft troubleshooting article.
-
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.
-
For SharePoint Server Subscription Edition customers who are currently on the January 2026 public update, updating directly to the March 2026 public update fails when you run the SharePoint Products Configuration Wizard (PSConfig)
For farms on the January 2026 public update, upgrading directly to the March 2026 update fails when you run the SharePoint Products Configuration Wizard (PSConfig).
How to apply the workaround WorkaroundInclude the February 2026 update in the upgrade sequence, and run PSConfig immediately after the February update and again after the March update.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- Install KB5002822 (January 2026), then KB5002833 (February 2026), then KB5002843 (March 2026).
- Run PSConfig immediately after installing the February update and again after the March update.
-
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.
-
Apps might become unresponsive when saving files to cloud-based storage
Some apps may freeze or show errors when opening or saving cloud files. With Outlook data files on OneDrive, Outlook may hang or fail to reopen; sent items may disappear or old emails may download again.
How to apply the workaround WorkaroundContact the app developer about other ways to access the files. For Outlook, move PST files out of OneDrive; webmail is another option if your provider supports it.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- Contact the app developer about other ways to access the files.
- For Outlook, move its PST files out of OneDrive or use webmail if your email provider supports it.
-
Apps might become unresponsive when saving files to cloud-based storage
Some apps might freeze or show errors when opening or saving files in cloud storage. Outlook might also hang when PST files are stored on OneDrive.
How to apply the workaround WorkaroundKB5078131 addresses this issue.
-
RemoteApp sessions might fail to start on Azure Virtual Desktop
RemoteApp connections in Azure Virtual Desktop might fail after KB5072033; full desktop sessions are not affected.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5072033 on affected systems until a fix is released.
-
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.
-
Users may see “4gab5" event tags logged in the SharePoint Unified Logging System (ULS) logs when they access sitedirectorysettings.aspx by using ‘set other host’
Users might see “4gab5” event tags in SharePoint Unified Logging System (ULS) logs when they access
sitedirectorysettings.aspxusing ‘set other host’.How to apply the workaround SharePoint Management ShellAdding the additional farm host allows it to access the page, which is otherwise restricted to the current farm host.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit3 steps SharePoint Management Shell Instructions (.txt)Step-by-step procedure- Confirm that the additional host is safe before adding it.
- In the SharePoint Management Shell, add the host to
AdditionalValidSPFarmHostsand update the farm. - Run
iisreset.
> add-pssnapin *> $f = get-spfarm> $f.AddGenericAllowedListValue("AdditionalValidSPFarmHosts", "your_additional_farm_host")> $f.update()> iisreset
-
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.
-
Some machines enrolled for Hotpatch might temporarily lose Hotpatch status
A very limited number of Hotpatch-enrolled Windows Server 2025 machines received this update. Those machines temporarily lose Hotpatch updates and get regular monthly updates that require a restart in November and December; the January 2026 baseline restores Hotpatch eligibility.
How to apply the workaround WorkaroundIf the machine installed this update, install the regular monthly updates in November and December, then the January 2026 baseline. If it downloaded but has not installed the update, pause updates, resume them, and scan again.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- For a machine that downloaded but has not installed the update, open Settings > Windows Update and select Pause updates.
- Resume updates, then scan for updates again.
-
Windows Server Update Services (WSUS) does not display error details
Windows Server Update Services (WSUS) does not show synchronization error details in its reports after KB5070881 or later updates.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5070881 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 continue to 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.
-
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
Microsoft says the reported IIS website loading issue does not affect Windows Server 2025. Server users do not need to take action.
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
After KB5065429, shared files and folders might be unreachable over SMBv1 on NetBIOS over TCP/IP. The issue can affect a client or server with the September 2025 security update; SMBv2 and SMBv3 are not affected. KB5066198 resolves it.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5065429 on affected systems until a fix is released.
-
PSDirect connections failing in hotpatched devices
Microsoft lists an open issue where PowerShell Direct connections might fail on hotpatched devices. It can occur when the host and guest virtual machines are not both fully updated.
How to apply the workaround WorkaroundIf connections fail, update both the host and guest virtual machines with the recommended updates.
-
SMBv1 protocol connectivity
Microsoft lists an open issue where shared files and folders might be unreachable over SMBv1 on NetBIOS over TCP/IP. It can occur if either the SMB client or server has the September 2025 security update.
How to apply the workaround WorkaroundThe page names KB5066782 as an update that 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.
-
Directory synchronization (DirSync)
After the September 2025 security update, apps using the DirSync control for on-premises AD DS can miss members when syncing groups with more than 10,000 members. This remains listed as open here; the page points to KB5068861 as addressing it.
How to apply the workaround WorkaroundThe page points to KB5068861 as addressing the issue.
-
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.
-
After you install KB5002771, you might experience an issue when you configure calendar overlay settings
You might experience an issue when configuring calendar overlay settings after installing KB5002771.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5002771 on affected systems until a fix is released.
-
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.
-
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.
-
$farm.RemoveGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")
Some SharePoint page resources might fail to load, and ULS logs might show an access denied message.
How to apply the workaround SharePoint Management ShellAdd the valid resource path to the AllowList, then restart IIS.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit2 steps SharePoint Management Shell Instructions (.txt)Step-by-step procedure- Make sure the resource path is valid and as expected.
- Run the commands in SharePoint Management Shell.
> $farm = get-spfarm> $farm.AddGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")> $farm.Update()> iisreset
-
$farm.ContainsGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")
Some SharePoint page resources might not load, and an Access Denied message might appear in the logs.
How to apply the workaround SharePoint Management ShellAdding the resource path to the AllowList lets the affected page resource load.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit2 steps SharePoint Management Shell Instructions (.txt)Step-by-step procedure- Make sure the resource path is valid and as expected.
- In SharePoint Management Shell, add the resource path to the AllowList, update the farm, and run
iisreset.
> $farm = get-spfarm> $farm.AddGenericAllowedListValue("SignOutRefererAllowList", "<resource path>")> $farm.Update()> iisreset
-
The Windows 11, version 22H2 package KB5056580 was not available on Windows Server Update Services (WSUS) or Microsoft Update Catalog
The Windows 11, version 22H2 package was missing from WSUS and the Update Catalog. Microsoft published it there on July 14, 2025.
How to apply the workaround WorkaroundBefore it was published there, the package could be installed through Windows Update or Microsoft Update.
-
Azure VM with Trusted Launch disabled
A small subset of Generation 2 Azure VMs might not boot after KB5062553. The risk applies when Trusted Launch is disabled and VBS is enforced through a registry key.
How to apply the workaround WorkaroundKB5064489 is listed as addressing 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.
-
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.
-
Noto fonts
CJK text might look blurry in Chromium browsers at 96 DPI (100% scaling).
How to apply the workaround WorkaroundIncrease display scaling to improve text clarity. Users can also report Noto CJK font issues through Google's Noto Fonts GitHub repository.
-
Update delay with deferral policies
Some devices in organizations using quality-update deferral policies might receive the June 2025 security update later than expected because its metadata timestamp is June 20, 2025, although it was released on June 10. This affects update timing, not quality or applicability.
How to apply the workaround WorkaroundOrganizations using Windows Autopatch can create an expedite policy; otherwise, admins can 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 and deliver the update immediately.
- Alternatively, adjust deployment rings or deferral configurations to reduce the delay window.
-
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.
-
Print to PDF might not work
After KB5058411, Microsoft Print to PDF might disappear or fail to install with error 0x800f0922. Microsoft lists this issue here; KB5062553 addresses it.
How to apply the workaround WorkaroundEnable Microsoft Print to PDF in Windows Features, or use the PowerShell commands below.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit2 steps powershell.exe · Administrator Instructions (.txt)Step-by-step procedure- Press Windows + R, enter
optional features, and enable Microsoft Print to PDF in the Windows Features dialog, or open PowerShell as administrator. - Run the commands below in order. The final command might return error 0x800f0922.
> Disable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features> Enable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices
- Press Windows + R, enter
-
Noto fonts
CJK text might look blurry or unclear at 96 DPI in Chromium-based browsers, including Microsoft Edge and Google Chrome. Increasing display scaling improves clarity.
How to apply the workaround WorkaroundIncrease display scaling to improve clarity; users can also report Noto CJK font issues through Google's GitHub repository.
-
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.
-
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 Hello
Microsoft lists an issue that might prevent Windows Hello facial recognition or PIN sign-in after a local reset. It affects devices where Secure Launch or DRTM is enabled after KB5055523.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5055523 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.
-
Active Directory Replication
On Windows Server 2025 domain controllers that hold the schema master role, duplicate schema object entries might cause Active Directory replication to fail with a schema mismatch. The issue can appear during Exchange Server setup forestprep and can affect replication across the enterprise.
How to apply the workaround WorkaroundKB5068861 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
CJK text might look blurry in Chromium-based browsers at 96 DPI (100% scaling).
How to apply the workaround WorkaroundIncrease display scaling to improve text clarity.
-
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.
-
Microsoft Copilot
On some devices, Microsoft Copilot might be removed and unpinned from the taskbar. Microsoft says the issue is fixed and affected devices are being restored.
How to apply the workaround WorkaroundReinstall the app from the Microsoft Store and pin it to the taskbar.
-
Open Secure Shell service
Microsoft lists an OpenSSH service issue reported after the October 2024 security update. On some enterprise, IoT, and education devices, the service might fail to start and block SSH connections.
How to apply the workaround WorkaroundInstall KB5053596, which addresses this issue.
-
Open Secure Shell service
On some devices, the Open Secure Shell service might fail to start, blocking SSH connections. Microsoft says it is investigating whether Home or Pro devices are affected.
How to apply the workaround WorkaroundThe page says KB5052077 addresses this issue.
-
Azure Arc Setup wizard app
The Azure Arc Setup wizard app might stop responding when opened from Start or the taskbar. The application event log might show Event ID 1000 for
AzureArcSetup.exe.Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5051987 on affected systems until a fix is released.
-
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.
-
USB Printer Issue
Some USB-connected dual-mode printers might print random text and data, often starting with “POST /ipp/print HTTP/1.1”. This is more likely when the printer is turned on or reconnected.
How to apply the workaround WorkaroundThe page says KB5053643 addresses this issue.
-
System Guard Runtime Monitor Broker service
Event Viewer might show a System Guard Runtime Monitor Broker service error on devices with updates released January 14, 2025, or later. The error should not affect performance, features, or device security; KB5055612 addresses it.
How to apply the workaround WorkaroundDo not manually start or configure the service, or uninstall or remove it.
-
System Guard Runtime Monitor Broker service
Event Viewer might show a System Guard Runtime Monitor Broker service error on devices with updates from January 14, 2025, or later. The error is otherwise silent and should not affect performance, features, or device security.
How to apply the workaround WorkaroundKB5055526 addresses this issue; do not manually start, configure, uninstall, or remove the service or its components.
-
Remote desktop
Remote Desktop sessions on Windows Server 2025 might freeze shortly after connection, making mouse and keyboard input unresponsive. Remote Desktop sessions might also disconnect unexpectedly, including Windows 11 version 24H2 clients connecting to Remote Desktop Services on Windows Server 2016 or earlier; Windows Server 2025 is not affected as an RDS host but might disconnect as a client to older servers. KB5055523 resolves the freeze, and KB5053656 addresses the disconnection issue.
How to apply the workaround Group PolicyFor enterprise-managed devices with the disconnection issue and an update older than March 27, 2025, configure the special Group Policy and restart the devices. Devices with the March 27, 2025 update or later do not need this policy or a Known Issue Rollback.
Step-by-step workaround instructionsShow steps Hide steps3 stepsStep-by-step procedure- For affected enterprise-managed devices updated before March 27, 2025, obtain the special Group Policy for Windows 11 version 24H2 and Windows Server 2025.
- Configure it under
Computer Configuration > Administrative Templates. - Restart the affected devices.
-
Citrix
Some devices with Citrix Session Recording Agent version 2411 might fail to install the January 2025 security update and undo the changes. Home users are not expected to be affected.
How to apply the workaround WorkaroundUpdate Citrix Session Recording Agent to version 2503 or newer.
-
Citrix
Organizations with Citrix Session Recording Agent 2411 might see the January 2025 security update fail and roll back. Home users are not expected to be affected.
How to apply the workaround WorkaroundInstall Citrix Session Recording Agent version 2503 or newer; Citrix released version 2503 on April 28, 2025.
-
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.
-
A file version error occurs when you try to install Exchange Server November 2024 SU
Installing the November 2024 security update might fail with a file version error. If the first workaround does not help, the article provides a second method.
How to apply the workaround WorkaroundRestart the server, check Exchange service startup types and .NET Framework 4.8, then retry the installation. If Exchange services are disabled, restore their startup configuration first.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit5 steps powershell.exe · Administrator Instructions (.txt)Step-by-step procedure- Restart the Exchange server.
- Check the Exchange services with the listed
Get-Servicecommand. - If their
StartTypeis Disabled, run the setup commands to restore the services, then check their status again. - Check for the .NET Framework 4.8 update with
Get-Hotfix. If it is missing, install it through Windows Update. - Retry the November 2024 security update installation. If this method does not help, follow Workaround 2 in the linked article.
> Get-Service -DisplayName "Microsoft exchange*" | ft DisplayName,Starttype ,Status> cd "C:\Program Files\Microsoft\Exchange Server\V15\Bin"> Add-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.Setup -ErrorAction SilentlyContinue> .\ServiceControl.ps1 AfterPatch> Get-Hotfix
-
The Edge Transport service stops responding after installing November 2024 SU
The Edge Transport service might stop responding and restart after this security update when it decrypts certain externally protected messages. The issue is resolved by the May 29, 2025 hotfix for the applicable Exchange version.
How to apply the workaround Exchange Management ShellMSIPC is enabled by default in the November 2024 security update. Disabling it works around the service failure described in the issue.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit2 steps Exchange Management Shell Instructions (.txt)Step-by-step procedure- In an elevated Exchange Management Shell window, run the commands in order.
- After installing the applicable May 29, 2025 hotfix, remove the setting override and refresh configuration as shown in the undo commands.
> New-SettingOverride –Name "DisableMSIPC" -Component Encryption –Section UseMSIPC –Parameters @("Enabled=false") -Reason "Disabling MSIPC stack"> Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh> Restart-Service MSExchangeTransport
-
A time zone exception occurs after installing Exchange Server November 2024 SU (Version 1 or Version 2)
After either version of the November 2024 security update, calendar files might not preview or add to calendars. The issue can also affect processing of messages with calendar attachments.
How to apply the workaround WorkaroundThe mapping file has a duplicate entry for Asia/Bishkek. Removing one copy works around the resulting time zone exception.
Step-by-step instructions, command & download kitShow steps & kit Hide steps & kit4 steps powershell.exe · Administrator Instructions (.txt)Step-by-step procedure- Back up
IanaTimeZoneMappings.xmlin the ExchangeV15\Binfolder. - Open the file and find the two copies of
<Map IANA="Asia/Bishkek" Win="Central Asia Standard Time" />. - Delete one copy and save the file.
- In an elevated PowerShell window, restart the web and transport services.
> Restart-Service -Name W3SVC, WAS -Force> Restart-Service -Name MSExchangeTransport
- Back up
-
Exchange Transport Rules and Data Loss Prevention rules don't work after installing November 2024 SU V1
After November 2024 SU V1, Exchange might stop processing Transport Rules and DLP rules. The issue is listed for this update.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5044062 on affected systems until a fix is released.
-
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.
-
Resolution
KB5046856 fixes the “unknown token” error in scheduled database jobs.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5046062 on affected systems until a fix is released.
-
Symptoms
Some scheduled database jobs might show an “unknown token” error after KB5046062.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5046062 on affected systems until a fix is released.
-
CDC capture job might fail if columns are missing in CDC change tables
On databases using change data capture (CDC), columns with commas in their names might be missing from CDC tracking tables and cause capture-job failures; a comma-containing column in a tracking table might be dropped during a CDC upgrade. Separately, CDC upgrades can fail when tracking-table column names contain other symbols.
How to apply the workaround SQL Trace FlagBefore upgrading the GDR build, enable trace flag T15006 and restart the SQL Server service.
Step-by-step workaround instructionsShow steps Hide steps3 stepsStep-by-step procedure- In SQL Server Configuration Manager, open the instance properties and go to the Startup Parameters tab.
- Add trace flag
T15006, select Add and Apply, then restart the SQL Server service. - Perform the GDR upgrade.
-
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 Windows and Linux dual-boot devices might fail to boot Linux and show an SBAT security-policy error.
How to apply the workaround WorkaroundSeptember 2024 and later updates omit the settings that caused the issue; additional improvements to resolve it are included in May 2025 and later updates. Dual-boot systems need no additional steps after installing September 2024 or later updates.
-
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.
-
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
A Windows-and-Linux dual-boot device might fail to start Linux and show a Secure Boot policy violation. The September 2024 update and later updates do not contain the settings that caused the issue; later updates include additional improvements.
How to apply the workaround WorkaroundInstall the September 2024 Windows security update or a later update. Dual-boot devices need no additional steps after installing one of those updates.
-
Issue two: SQL Server VSS Writer might fail to perform a backup because no database is available to freeze
Backup tools might fail to create application-consistent backups because SQL Server VSS Writer has no database available to freeze. The issue is fixed in CU15.
How to apply the workaround WorkaroundThe page's current solution is to roll back to CU13 and perform the snapshot backup.
Step-by-step workaround instructionsShow steps Hide steps2 stepsStep-by-step procedure- Roll back to SQL Server 2022 CU13.
- Perform the snapshot backup.
-
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.
-
After installing KB5036909, 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 the update, changing a user account profile picture might fail with error 0x80070520. Microsoft says this issue has very limited or no impact for this Windows version.
How to apply the workaround WorkaroundContact Windows support for help if you encounter the issue.
-
After installing KB5036892, 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 KB5036892, changing a user account profile picture might fail with error 0x80070520. Microsoft says the issue has very limited or no impact for this Windows version.
How to apply the workaround WorkaroundContact Windows support if you encounter the issue.
-
After you install this SU, you can't preview Microsoft Word documents in Outlook on the web (OWA), and you receive an error message
Word documents cannot be previewed in OWA, and an error appears. KB5037224 fixes this.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5036386 on affected systems until a fix is released.
-
After you install this SU, you receive a "We're having trouble fetching results from the server" error message when you run a search in Microsoft Outlook cached mode
Outlook cached-mode searches show a “We're having trouble fetching results from the server” error. Searches work in online mode or OWA. KB5037224 fixes this.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5036386 on affected systems until a fix is released.
-
After you install this SU, OwaDeepTestProbe and EacBackEndLogonProbe are no longer working
OwaDeepTestProbe and EacBackEndLogonProbe fail after installation, and their monitors show Unhealthy. KB5037224 fixes this.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5036386 on affected systems until a fix is released.
-
After you install this SU, Download Domains are no longer working as expected
Users of some Outlook versions can no longer see inline images in OWA or download attachments through OWA. KB5037224 fixes this.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5036386 on affected systems until a fix is released.
-
After you install this security update (SU), the program no longer supports the Oracle Outside In Technology (OIT) or OutsideInModule
Exchange no longer extracts text from JPEG, TIFF, or AutoCAD attachments for mail-flow checks. This can affect attachment rules.
How to apply the workaround PowerShellA PowerShell script can override the setting that disables OIT. Microsoft advises against overriding it unless a functional issue affects the organization's mail flow.
-
Incorrect behavior of SESSION_CONTEXT in parallel plans
Queries using SESSION_CONTEXT might return wrong results or create access violation dump files when they run in parallel query plans, especially if a session is reset for reuse.
Workaround status No workaround yetMicrosoft has not published a manual workaround for this issue yet. Defer KB5033688 on affected systems until a fix is released.
-
Copilot in Windows (in preview) is not currently supported when your taskbar is located vertically on the right or left of your screen
Copilot in Windows (in preview) is not supported when the taskbar is positioned vertically on the left or right side of the screen.
How to apply the workaround WorkaroundWait for the new Copilot experience, which is gradually rolling out to devices with KB5039299 or later; it may arrive over the next few months.
-
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 between monitors or become misaligned when using Copilot in Windows (in preview).
How to apply the workaround WorkaroundWait for the new Copilot experience, which is gradually rolling out to devices with KB5039299 or later; it may arrive over the next few months.
Recently resolved
Fixed in latest updates-
Windows activation and licensing commands might fail with error 0x80041008
Organizations using command-line tools or automated processes for activation might see error 0x80041008 when running some licensing commands. Devices already activated remain activated; devices with the needed KMS key and setup that do not need these commands are not expected to be affected.
How to apply the workaround WorkaroundContact Microsoft Support for business for an immediate mitigation.
-
USB audio devices might fail to start or produce no sound
Some USB Audio Class 1.0 devices might fail to start or produce sound. KB5129239 resolves the 8-channel and 3D-audio symptoms, but other symptoms are still being addressed.
How to apply the workaround WorkaroundIT administrators can contact Microsoft Support for Business for an immediate workaround for symptoms not addressed by KB5129239.
-
USB Audio Class 1.0 devices with error Code 10 or no output
Some USB Audio Class 1.0 devices might fail to start, produce no audio, or have unresponsive volume or sound settings. KB5129235 addressed symptoms with 8-channel or 3D audio; KB5131080 addressed the remaining symptoms.
How to apply the workaround WorkaroundSome customers reported restoring audio for multichannel modes by switching to 2-channel mode.
-
Users might be unable to sign in to OWA or send emails on Exchange Server
Some on-premises Exchange servers might have OWA sign-in, email sending, or mailbox replication problems after the October 2026 update. The issue is resolved by KB5131080 and later updates.
How to apply the workaround Registry / GPOFor updates released before November 10, 2026, a registry change can temporarily raise the Endpoint Mapper limit. The mitigation is not needed with KB5131080 or later.
-
USB Audio Class 1.0 devices with error Code 10 or no output
Some USB Audio Class 1.0 devices might show Code 10, produce no sound, or have unresponsive volume controls or sound settings. KB5131085 resolves the remaining symptoms; KB5129238 resolved the 8-channel and 3D audio symptoms earlier.
How to apply the workaround WorkaroundFor 8-channel or 3D audio problems, some customers reported restoring sound by switching to 2-channel mode.
-
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 people using File History might be unable to create or update backups. A connected backup drive might still appear to need reconnecting, and old files might show no previous version.
Resolution Fixed in KB5126651Install KB5126651 (or a later cumulative update) on affected devices. No manual workaround is required after updating.
-
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.
No known issue matches these filters.