This out-of-band (OOB) update for Windows 11, version 25H2 and Windows 11, version 24H2 (KB5121767) is cumulative. It includes all improvements from previous security and non-security updates, along with an additional fix.

Improvements

This OOB update includes the following improvement:

• [System Performance] This update addresses an issue affecting a limited number of devices with an Intel Innovation Platform Framework (Intel IPF) driver that could cause changes in performance, power consumption, or system behavior after installing recent Windows updates. A limited number of Dell devices that were temporarily prevented from receiving the July 2026 security update KB5101650 can now install this OOB update. This OOB update is only recommended for devices affected by this issue. If your device is not affected, no action is required.

Note

If you have turned on Get the latest updates as soon as they're available in Windows Update settings (Settings > Windows Update), you will automatically receive this OOB update. If the toggle is off on your device, you can install the update by going to Settings > Windows Update and selecting Download & Install. This OOB update is also available from the Microsoft Update Catalog.

Component updates

Servicing stack update (SSU)

Includes KB5120102 (Build 26100.8872), which improves the reliability of the Windows update installation process. To learn more about SSUs, see Simplifying on-premises deployment of servicing stack updates.

AI components

Updated to version 1.2605.856.0 (Image Search, Content Extraction, Semantic Analysis, Settings Model).

How to get this update

Before you install this update

Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

Install this update

To install this update, use one of the following Windows and Microsoft release channels.

Windows Update

This update is an optional update. To install this optional update, go to Settings > Windows Update > Advanced options > Optional updates.

File Information

For a list of the files provided in this update, download the file information for cumulative update KB5121767.
For a list of the files provided in the servicing stack update, download the file information for the SSU (KB5120102) - version 26100.8872.

Original source

This article describes Cumulative Update (CU7) for Microsoft SQL Server 2025. This update package contains 10 fixes that were issued after the release of SQL Server 2025 Cumulative Update 6. It updates components in the following builds:

• SQL Server - Product version: 17.0.4065.4, file version: 2025.170.4065.4
• Analysis Services - Product version: 17.0.25.223, file version: 2025.170.25.223

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when they're run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the "Known issues" section in SESSION_CONTEXT.

Linked server queries that use MSDASQL fail and generate error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2025, SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

Bug Reference - Description - Fix area - Component - Platform

• 5216512 - Fixes an issue in which monitoring queries that use sys.dm_exec_requests or sys.sysprocesses intermittently fail and return Error "976" or Error "978" when they run against a read-intent only secondary replica in an availability group. - SQL Server Engine - High Availability and Disaster Recovery - Windows
• 5271098 - Updates UCS encryption to use the AES-256 algorithm instead of AES-128 if TLS isn't explicitly enabled. - SQL Server Engine - Universal Communication Stack - All
• 5281735 - Fixes a non-yielding scheduler condition that can occur when SQL Server writes a time zone-related error to the error log. - SQL Server Engine - Programmability - All
• 5290707 - Adds a trace flag that lets you enable TLS 1.3 for SQL Server without having to edit the registry. - SQL Server Engine - Universal Communication Stack - Windows
• 5293307 - Strengthens Service Broker dialog encryption by using the AES-256 algorithm. - SQL Server Engine - Universal Communication Stack - Windows
• 5295512 - Adds logical capping to the EDIT_DISTANCE function to prevent overflow errors that an authenticated user could otherwise use to cause a denial-of-service crash. - SQL Server Engine - Query Execution - All
• 5295713 - Fixes an insecure deserialization vulnerability in the Message Queue task by removing support for the legacy BinaryMessageFormatter (2000 format). This change prevents remote code execution from untrusted MSMQ messages. - Integration Services - Integration Services - Windows
• 5349316 - Fixes an issue in which ALTER JSON INDEX REORGANIZE generates a dump file if statistics exist on the internal table of a JSON index. - SQL Server Engine - Programmability - All
• 5354186 - Fixes an issue in which the node parent offset is calculated incorrectly and can cause JSON corruption during a JSON_MODIFY operation. - SQL Server Engine - Programmability - All
• 5355051 - Fixes an issue in which a JSON_MODIFY merge operation can cause corruption and generate a dump file. - SQL Server Engine - Programmability - All

Original source

This article describes Cumulative Update package 26 (CU26) for Microsoft SQL Server 2022. This update contains 12 fixes that were issued after the release of SQL Server 2022 Cumulative Update 25. It updates components in the following builds:

• SQL Server - Product version: 16.0.4265.3, file version: 2022.160.4265.3
• Analysis Services - Product version: 16.0.43.252, file version: 2022.160.43.252

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Incorrect behavior of SESSION_CONTEXT in parallel plans

Queries that use the built-in SESSION_CONTEXT function might return incorrect results or trigger access violation (AV) dump files when they're run in parallel query plans. This issue occurs because of the manner in which SESSION_CONTEXT interacts with parallel execution threads, particularly if the session is reset for reuse.

For more information, see the "Known issues" section in SESSION_CONTEXT.

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists for SQL Server 2022, SQL Server 2019, and SQL Server 2017. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

For more information about the bugs that are fixed and enhancements that are included in this cumulative update, see the following table.

Bug Reference Description Fix area Component Platform 5132800 Adds more detailed error information to the Windows Server Failover Cluster log if the availability group resource DLL can't retrieve diagnostic column information. SQL Server Engine High Availability and Disaster Recovery Windows 5138995 Adds support for removing an IP address from an availability group listener by using the ALTER AVAILABILITY GROUP ... MODIFY LISTENER ... REMOVE IP command. SQL Server Engine High Availability and Disaster Recovery Windows 5196012 Fixes a SQL injection vulnerability in the sys.sp_MSforeachdb stored procedure that allows an authorized attacker to elevate privileges over a network. SQL Server Engine Management Services All 5197074 Fixes an issue in which an index rebuild maintenance plan stops responding because of a long-running query. SQL Server Engine Maintenance Plan All 5216517 Fixes an issue in which monitoring queries that use sys.dm_exec_requests or sys.sysprocesses intermittently fail and return error "976" or "978" on a secondary replica in an availability group. SQL Server Engine High Availability and Disaster Recovery Windows 5219564 Fixes an issue in the interpolation calculation of the new cardinality estimator for very large values that can cause an ALTER INDEX operation to choose a serial plan. SQL Server Engine Query Execution All 5240249 Removes the deprecated RSA32Lib cryptographic library as part of ongoing cryptography modernization. SQL Server Engine Universal Communication Stack Windows 5272424 Fixes an access violation that occurs when you run ALTER PARTITION FUNCTION ... SPLIT RANGE against a partition function that's used by a table that has an identity column that's also referenced by a clustered index on a schema-bound view. SQL Server Engine Programmability All 5285172 Fixes a nonyielding scheduler condition that can occur when SQL Server writes certain errors to the error log. SQL Server Engine Programmability All 5293216 Adjusts the sampling rate for incremental statistics if the last sampling rate was 100 percent and many new rows are inserted into the table. SQL Server Engine Query Execution All 5300009 Improves memory management during query compilation for columnstore indexes to reduce query compilation time. SQL Server Engine Methods to access stored data Windows 5347342 Fixes a nonyielding scheduler condition that can occur if sys.dm_db_index_operational_stats iterates through a large number of cached heaps or B-trees. SQL Server Engine Methods to access stored data All

How to obtain or download this or the latest cumulative update package

File information

Notes for this update

How to uninstall this update

References

• Announcing updates to the SQL Server Incremental Servicing Model (ISM)
• SQL Server Service Packs are no longer supported starting from SQL Server 2017
• Determine which version and edition of SQL Server Database Engine is running
• Servicing models for SQL Server
• Naming schema and Fix area descriptions for SQL Server software update packages
• Description of the standard terminology that is used to describe Microsoft software updates

Original source

Follow us on LinkedIn, X, Bluesky

Release date: July 15, 2026

Update 1.129.1: The update addresses these issues.

Downloads: Windows: x64 Arm64 | Mac: Universal Intel silicon | Linux: deb rpm tarball Arm snap

Welcome to the 1.129 release of Visual Studio Code. This release brings a dedicated agent host, a new editor panel in the Agents window, running commands with !, and a preview of the modern UI.

• The agent host: Run agent sessions in a dedicated process and connect to them from multiple windows.
• New editor panel in the Agents window (Experimental): Review agent-generated files and diffs in a docked editor.
• Run commands with ! prefix: Run terminal commands directly from chat prompts.
• Modern UI preview (Experimental): Get a first look at the updated VS Code workbench appearance.

Happy Coding!

VS Code is rolling out gradually to all users. Use Check for Updates in VS Code to get the latest version immediately.

To try new features as soon as possible, download the nightly Insiders build, which includes the latest updates as soon as they are available.

Agents

The agent host

We're rearchitecting how agent sessions work in VS Code around the agent host - a dedicated process that runs agent harnesses such as Copilot, Claude, and Codex, based on the Agent Host Protocol (AHP). Because a session lives in its own process, the same session can be connected to and rendered from multiple VS Code windows at once. The agent host's Copilot agent is powered by the Copilot SDK, which means that its behavior and functionality is aligned with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products.

Learn more about the VS Code Agent Host architecture.

We're actively developing the agent host and starting to roll it out to users in both the editor window and the Agents window. To opt in, enable chat.agentHost.enabled (This setting is managed at the organization level. Contact your administrator to change it.) and then pick an agent host harness from the harness dropdown. The screenshot below shows how to select the Copilot harness on the agent host in the editor window.

As we continue to invest in the agent host, some new features in these release notes may only be available when an agent runs on it. Those features link back to this section and, where relevant, note any additional settings that enable them (for example, chat.agents.claude.preferAgentHost to enable the Claude agent on the agent host).

New editor panel in the Agents window (Experimental)

The Agents window shows your conversation with an agent next to a detail area for the files and changes it produces. This release introduces a redesigned editor panel that brings the editor and the detail area together into one docked pane with a shared tab bar, so reviewing an agent's work feels like working in the main editor instead of switching between separate panels.

With the new editor panel, you can:

• Open files and diffs directly inside the docked editor, next to your chat, and add tabs with a New Tab action that matches the chat tab strip.
• Review changes in the Changes view with an improved diff experience: toggle between inline and side-by-side views, expand or collapse all files at once, and read changes in a more compact diff representation that fits more of the change on screen. The next action, such as Create Pull Request, is available right from the editor tab title, and editor keybindings like toggling the diff view work the same as they do in the main VS Code window.
• Pick up where you left off. Each session restores its side-pane width, open editors, active editor, and per-file collapsed state across session switches and window reloads.

This is an experimental, opt-in layout. To try it, enable sessions.layout.singlePaneDetailPanel and reload the window, since the setting is read once at startup.

Session-management tools for Agent Host sessions

Agents running on the agent host (Copilot, Claude, and Codex) now have access to a suite of session-management tools, so an agent can enumerate, create, observe, and act on other sessions and chats without you needing to switch away from your current conversation.

With these tools, an agent can:

• List your sessions with their status, workspace, and changes, so it can find the right one to act on. Archived sessions are excluded unless explicitly requested.
• Read another session's recent conversation to understand what it's doing.
• Create a new session or a new chat within an existing session to hand off a sub-task, rather than overloading a single conversation with unrelated work.
• Send a message to a session or chat it created, to kick off or steer that work.

Whenever a tool creates or targets a session, VS Code renders an Open Session pill so you can jump straight to it. Sending a message to another session always asks for your confirmation first. An agent can't message its own chat, and a burst of sends is capped so a single request can't fan out into an unbounded number of sessions.

Agents window improvements

This release includes several smaller improvements to the Agents window new-session flow:

• Remembered new-session defaults: the new-session picker remembers your last agent mode and approvals choices and uses them as the defaults the next time you create a session, so you don't have to reselect the same options for every task.
• Worktree checkbox: instead of choosing between folder and worktree isolation from a dropdown, the new-session configuration shows a single New Worktree checkbox. Check it to run the session with Git worktree isolation, which keeps the agent's changes in a separate folder until you're ready to review and merge them, or leave it unchecked to use folder isolation.

Chat

Run commands with ! prefix

You can now prefix chat messages with a ! to run their contents as terminal commands. This works in agent host sessions both in the editor and Agents window.

BYOK models with the Copilot agent harness

You can now use Bring Your Own Key (BYOK) models in the Agents window when you select the Copilot harness running on the agent host.

Migrate prompt files to skills (Experimental)

Prompt files (*.prompt.md) are used to describe custom slash commands. They are only supported in the Local agent harness while other harnesses express slash commands with skills. For compatibility across harnesses, we recommend to migrate all prompt files to skills.

With chat.customizations.promptMigration.enabled enabled, if you select a harness running on the agent host and you have migratable prompt files, you'll now see a 'Migrate Prompts' entry in the AI Customizations overview.

The migration interface lets you:

• View prompt files from both workspace (.github/prompts/) and user data locations.
• Migrate selected files to skills and open the newly created skills.

Editor experience

Reopen an editor from the editor toolbar

When a file or diff supports multiple editors, you can switch editors directly from the editor toolbar. Open the ... menu and select an editor from the Reopen Editor With submenu. This makes alternative editors easier to discover without using the Command Palette.

Modern UI preview (Experimental)

Setting: workbench.experimental.modernUI

You can now preview a modernized VS Code UI that updates the look and feel of the editor workbench. This is currently an experimental feature that you can enable with the workbench.experimental.modernUI setting and is enabled by default in Insiders builds.

Authentication

GitHub Enterprise support for Copilot in the agent host

Developers whose GitHub Copilot access is provided through a GitHub Enterprise (GHE) instance can sign in and use Copilot in VS Code. Previously, the agent host's Copilot authentication only supported github.com, so a GHE-backed Copilot subscription could not complete sign-in: both the OAuth flow and the Copilot token request targeted github.com.

With this release, VS Code can authenticate Copilot against a GitHub Enterprise instance. When you sign in to Copilot, choose your GitHub Enterprise instance, and VS Code runs the sign-in flow and requests Copilot access tokens from that host instead of github.com. This works in both the editor window and the Agents window, and with both the Copilot and Claude agents.

Because this support is part of the agent host, ensure the agent host is enabled with chat.agentHost.enabled (This setting is managed at the organization level. Contact your administrator to change it.).

Proposed APIs

Configure custom editors for diff and merge editors

Custom editors now opt out of diff and merge editors by default. As a result, a file can continue to open in a custom editor while its diffs and merges open in the built-in text editors. You might notice this change if you previously saw a custom editor when opening a diff or merge editor.

To open a diff in another editor, use the Reopen Editor With submenu in the editor toolbar. To always use a specific editor for matching diffs, configure the workbench.diffEditorAssociations setting.

The proposed customEditorPriority API provides separate priorities for files, diffs, and merge editors:

{
  "priority": {
    "textEditor": "default",
    "diffEditor": "option",
    "mergeEditor": "never"
  }
}

The new never priority prevents automatic selection for that editor type while keeping the editor available for explicit selection.

If the text diff editor cannot display binary content, VS Code still falls back to a compatible custom diff editor.

Thank you

Contributions to vscode:

• @accnops (Arthur Cnops): chat/voice: land voice answers on question carousels (fix Skipped) PR #323161
• @cipheraxat (Akshat Anand): Fix Modern UI editor tab decoration color on full label PR #325291
• @danielrobbins (Daniel Robbins): Fix bugs related to setting the right Chat model. (Fixes Issue #323765) PR #323767
• @dobbydobap (varshitha):
  • Fix second Rerun Last Task failing to launch for reevaluateOnRerun tasks PR #324571
  • Unstick a pinned tab dragged to the start of the unpinned row PR #324734
• @JeffreyCA: Update Fig spec for Azure Developer CLI (azd) PR #321221
• @Kaidesuyoo (Kaidesuyo): fix persistent workbench UI performance degradation PR #324986
• @myselfsiddharth (Siddharth Mehta): debug: right-align toolbar actions in exception widget PR #325077
• @theanarkh (theanarkh):
  • workbench: fix ObjectSettingCheckboxWidget memory leaky PR #323670
  • fix: make sure register handler when ipc emitter add listener PR #323663
• @yavanosta (Dmitry Guketlev): Use startColumn in growUntilVariableBoundaries PR #324523

Issue tracking

Contributions to our issue tracking:

• @gjsjohnmurray (John Murray)
• @RedCMD (RedCMD)
• @IllusionMH (Andrii Dieiev)
• @albertosantini (Alberto Santini)
• @dobbydobap (varshitha)
• @hogiSp (hogiSp)

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.

If you'd like to read release notes for previous VS Code versions, go to Updates on code.visualstudio.com.

Original source

Updates released between July 01, 2026, and July 15, 2026.

Microsoft 365 admin center

• Submit agent to Agent Store from Agent Builder [Windows, Web]

Customers can submit their agents built in Agent Builder to the Agent Store under the "Built by your org" section, after admin review and approval in Microsoft 365 Admin Center. This governed flow enables admins to review, approve, and publish submitted agents so that they can be discovered and used by others in the Agent Store. This helps organizations share validated agents at scale while maintaining quality and governance.

Roadmap ID: 557173

Details:

What changed: Customers can submit agents created in Agent Builder to the Agent Store after admin review and approval in the Microsoft 365 Admin Center. Previously, there was no governed process for publishing custom agents at scale. This update introduces a controlled workflow that maintains quality and governance while enabling agent sharing within organizations.

Why: This change helps organizations share validated custom agents securely and efficiently. Admin review ensures agents meet organizational standards before publication.

Try this:

1. Build an agent in Agent Builder.
2. Submit the agent for admin review in the Microsoft 365 Admin Center.
3. After approval, find the agent published under 'Built by your org' in the Agent Store.

Why this matters: Governed submission protects organizational security while enabling wider use of custom Copilot agents.

Business impact: Organizations can scale agent deployment with centralized control, improving collaboration and compliance.

Personal impact: You gain access to trusted, organization-approved agents that enhance productivity and reduce duplicated effort.

Microsoft 365 Copilot

• Copilot Prompt Gallery - Company-wide prompt publishing [Windows, Web]

Organizations can build their own collections of prompts that are tailored to their business needs and workflows and distribute these to all users within the tenant.

Roadmap ID: 486695

Details:

What changed: Admins can now build prompt collections specific to their company's needs and publish them tenant-wide through the Copilot Prompt Gallery. Previously, users only had access to default prompts without centralized management or customization options.

Why: This change allows organizations to standardize and optimize Copilot usage by providing prompts aligned with internal processes and terminology.

Try this:

1. Open the Copilot Prompt Gallery in the Microsoft 365 admin center.
2. Create a new prompt collection tailored to your business workflows.
3. Publish the collection to all users in your tenant for consistent access.

Why this matters: Centralized prompt management improves user efficiency and ensures Copilot responses align with company standards.

Business impact: Teams gain consistent access to relevant prompts, reducing training needs and improving productivity.

Personal impact: Users benefit from prompts that reflect their daily tasks, saving time and reducing guesswork.

Microsoft Edge: v.149 - Modern, unified, and updated Look and Feel [Web]

Microsoft Edge will update the Look and Feel to give customers a unified experience across all of Microsoft AI surfaces including Copilot and Bing. This will change multiple elements of the UX such as spacing, corners, fonts, default colors, etc.

Roadmap ID: 559993

Details:

What changed: Microsoft Edge version 149 introduces a refreshed user interface that aligns with the design language used in Copilot and Bing. Changes include updated spacing, rounded corners, new font styles, and revised default color schemes. This unified design enhances consistency across Microsoft AI products without affecting browser functionality or security settings.

Why: Updating the interface creates a cohesive experience across Microsoft AI tools, reducing user confusion and improving visual comfort. Consistent design helps users transition smoothly between Edge, Copilot, and Bing.

Try this:

1. Open Microsoft Edge and notice the updated spacing and corner styles.
2. Compare font styles and colors with those in Copilot or Bing.
3. Use the browser as usual to experience the consistent design across AI surfaces.

Why this matters: A consistent design across Microsoft AI tools improves usability and reduces the learning curve for users working with multiple Microsoft products.

Business impact: Teams benefit from a unified interface that simplifies training and support for Microsoft AI tools integrated with Edge.

Personal impact: You experience a visually coherent environment that reduces distraction and makes navigation more intuitive.

Microsoft 365 Copilot App

• Create brand kits from your brand guidelines [Web]

Seamlessly create brand kits by uploading your brand guidelines document.

Details:

What changed: Users can now upload a brand guidelines document to automatically generate brand kits. Previously, creating brand kits required manual setup and configuration. This update streamlines the process and reduces setup errors.

Why: This change simplifies brand kit creation by automating the extraction of brand elements from guidelines, saving time and ensuring consistency.

Try this:

1. Open the brand kit creation tool.
2. Upload your brand guidelines document.
3. Review and customize the generated brand kit.

Why this matters: Automating brand kit creation helps maintain brand consistency and reduces manual effort.

Business impact: Teams can produce standardized brand assets faster, improving brand compliance across projects.

Personal impact: You save time setting up brand kits and reduce errors from manual configuration.

Microsoft 365 Copilot Extensibility

• Access agents with Model Context Protocol in Office apps [Web]

Agents built with the Model Context Protocol (MCP) are available in Word, Excel, PowerPoint, Outlook, and Catalyst.

Details:

What changed: Users can now access agents built with the Model Context Protocol (MCP) directly within Word, Excel, PowerPoint, Outlook, and Catalyst apps. Previously, these agents were not integrated into these Office applications. This update enables seamless agent interactions using MCP across multiple Microsoft 365 apps.

Why: Integrating MCP agents into core Office apps improves user productivity by providing contextual assistance and data retrieval without switching applications.

Try this:

1. Open Word, Excel, PowerPoint, Outlook, or Catalyst.
2. Access the Copilot pane.
3. Interact with MCP-enabled agents to get contextual assistance.

Why this matters: This integration brings consistent agent support across popular Office apps, enhancing workflow continuity.

Business impact: Teams can leverage MCP agents within familiar Office environments, reducing context switching and improving collaboration.

Personal impact: You gain faster access to intelligent assistance within your everyday Office apps, saving time and effort.

• Admins can manage access more precisely with support for nested permissions in Confluence and ServiceNow [Web]

Support for hierarchical ACLs for SNOW and Confluence connectors.

Roadmap ID: 503587

Details:

What changed: The connectors for Confluence and ServiceNow now evaluate parent-level permissions when determining access to child items. Previously, only child item permissions were considered, which could lead to inconsistent access control. This update supports nested permissions, improving security and compliance.

Why: Supporting hierarchical permissions ensures that access control aligns with organizational policies and reduces unauthorized data exposure in Copilot extensibility scenarios.

Try this:

1. Review your Confluence or ServiceNow catalog permissions.
2. Configure parent and child item permissions to reflect your organizational hierarchy.
3. Verify access control behavior in Microsoft Copilot to confirm hierarchical permissions are enforced.

Why this matters: Accurate permission evaluation prevents unauthorized access and maintains data security across integrated systems.

Business impact: Security teams can enforce consistent access policies across multiple platforms, reducing risk of data leaks.

Personal impact: Users see search and content results that respect organizational permission structures, reducing confusion and access issues.

• Manage Federated Copilot Connectors in Microsoft 365 admin center connectors tab [Web]

Admins can now deploy and manage Federated Copilot Connectors (MCP-based connectors) directly from the Connectors tab under Copilot in the Microsoft 365 admin center.

Details:

What changed: Previously, Copilot connectors primarily enabled organizations to index and sync organizational data into Microsoft 365. With Federated Copilot connectors, admins can now enable connections to external data sources through the Model Context Protocol (MCP), including custom line-of-business applications and publicly available MCP servers. These connectors use user-level authentication to access data at runtime, eliminating the need for organizational indexing while preserving existing source permissions.

Why: Organizations need a centralized way to govern and manage both indexed and federated data connections used by Microsoft 365 Copilot. Bringing Federated Copilot Connectors into the Connectors experience simplifies administration while maintaining security and compliance controls.

Try this:

1. Sign in to Microsoft 365 admin center.
2. Navigate to Copilot, and then Connectors.
3. Deploy or update Federated Copilot Connectors for users.

Why this matters: Provides centralized governance for MCP-based connectors, reduces administrative overhead, and accelerates deployment of approved external data sources across the organization.

Business impact: IT teams can efficiently manage Copilot connectors at scale, improving governance and deployment speed.

Personal impact: Users gain faster access to approved external tools and data sources in Copilot while benefiting from secure, user-scoped access that respects existing permissions.

Original source

Manage Teams devices in the Pro Management portal

Administrators can now use the Pro Management portal to monitor device health, manage inventory, and access analytics for both Windows and Android devices. Management of Android-based Teams Rooms, Teams panels, and Teams phones is moving from the Teams admin center to the Pro Management portal, providing a consistent and secure management experience across devices and manufacturers.

Report external users for security concerns in Teams

This feature enables users to report suspicious external users directly within Teams, alongside existing block actions. Reports are surfaced in the Teams admin center, giving admins visibility into potentially risky interactions and enabling them to investigate and take appropriate actions. This enhancement helps organizations respond faster to phishing, impersonation, and other external threats while leveraging end-user signals as an additional layer of protection.

Manage Teams Core agents in the Teams admin center

Administrators can now manage Teams Core agents, such as Facilitator, from a dedicated experience in the Teams admin center. Control agent availability and settings for your organization, specific users, or groups from a single location. Teams Core agents are available by default to licensed users and no longer depend on organization-wide Microsoft app settings.

Improved app and agent access request management

Users can now request access to apps and agents blocked by administrators through a guided experience in Teams and receive notifications when their request status changes. Administrators can review and act on requests more efficiently in the Teams admin center, with improved visibility into new requests.

Original source

Background: What changed and why

IT administrators can now automatically accept SSO permissions on managed Windows devices using a supported registry setting. In this context, SSO, or single sign-on, refers to using the Microsoft credentials from a user’s Windows sign-in to access other Microsoft apps and services without seeing any prompts. This new capability is available beginning with the July 2026 monthly security update (2026—KB5101650) for Windows 11, version 24H2 and 25H2.

In the European Economic Area (EEA), Microsoft updated the Windows sign-in experience so that users are not automatically signed in to other Microsoft applications and services after signing in to Windows. Instead, Windows asks users whether they want to use the same credentials to sign in to additional apps or services — giving users choice over how their Windows account is used for sign-in.

For managed enterprise environments, some organizations wanted additional flexibility to manage the SSO prompt experience on devices where their organizations already manage sign-in policies and trust relationships. To support those scenarios, we’ve developed a registry-based control that lets IT administrators automatically accept SSO permissions on eligible managed Windows devices.

What’s new: Enterprise admin control for sign-in behavior

Starting with the July 2026 monthly security update for Windows 11, version 24H2 and 25H2, IT administrators can deploy the following registry policy to automatically accept SSO permissions on managed devices:

Registry Path:
HKLM\SOFTWARE\Policies\Microsoft\Windows\AAD

Value:
AutoAcceptSsoPermission (DWORD) = 1

This policy can be deployed via:

• Group Policy (GPO)
• Microsoft Intune or similar mobile device management (MDM) tool
• Microsoft Configuration Manager
• Any management tool that supports registry policy deployment

Important details

• Scope: Applies only to managed enterprise devices with Microsoft Entra ID accounts
• Personal accounts: Prompts remain for personal Microsoft accounts (MSA)
• Unmanaged devices: Not affected —prompts remain for non-policy-controlled environments
• Supported OS: Windows 11, version 24H2 and 25H2

Getting started

To get started:

1. Ensure that your devices are running Windows 11, version 24H2 and 25H2 or later.
2. Install the July 2026 monthly security update.
3. Deploy the registry policy via GPO, Intune, or your preferred management tool.
4. Validate SSO behavior across your managed device fleet.

For detailed deployment guidance, visit Admin control for SSO prompts in Windows.

What’s next

We’re continuing to evaluate additional admin controls and transparency features that will give your organization greater confidence in managing authentication experiences across your device fleet. Have feedback? Share your ideas in the Comments.

Continue the conversation. Find best practices. Bookmark the Windows Tech Community, then follow us on LinkedIn or @MSWindowsITPro for updates. Looking for support? Visit Windows on Microsoft Q&A.

Original source

Applies To

SQL Server 2025 on Windows (all editions), SQL Server 2025 on Linux (all editions)

Summary

This security update contains fixes and resolves vulnerabilities. To learn more about the vulnerabilities, see the following security advisories:

• CVE-2026-47295 - Microsoft SQL Server Elevation of Privilege Vulnerability
• CVE-2026-47296 - Microsoft SQL Server Elevation of Privilege Vulnerability
• CVE-2026-50468 - Microsoft SQL Server Information Disclosure Vulnerability
• CVE-2026-54116 - Windows MultiPoint Services Elevation of Privilege Vulnerability
• CVE-2026-54117 - Microsoft SQL Server Remote Code Execution Vulnerability
• CVE-2026-54118 - Microsoft SQL Server Remote Code Execution Vulnerability
• CVE-2026-55002 - Microsoft SQL Server Elevation of Privilege Vulnerability

The Microsoft SQL Server components are updated to the following builds in this security update:

• SQL Server - product version: 17.0.4060.2, file version: 2025.170.4060.2

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Improvements and fixes included in this update

A downloadable Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists. Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#bkmk_NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

Bug reference - Description - Fix area - Component - Platform

• 5340799 - This fix resolves an insecure deserialization vulnerability in MessageQueueTask by removing support for the legacy BinaryMessageFormatter (2000 format). MessageQueueTask prevents remote code execution from untrusted Microsoft Message Queuing (MSMQ) messages. - Integration Services - Integration Services - Windows
• 5340800 - This fix resolves an insecure deserialization vulnerability in MessageQueueTask by restricting SoapFormatter deserialization that uses an allow list binder. The restriction prevents remote code execution (RCE) from untrusted Microsoft Message Queuing (MSMQ) message. - Integration Service - Integration Service - Windows
• 5266554 - This fix prevents unintended EXECUTE permission inheritance for EXTERNAL MODEL objects if a newly created principal reuses the same ID as a previously existing principal that had this permission. - SQL Server Engine - Metadata - Windows
• 5332047 - This fix addresses a vulnerability in SQL Server in which vector intrinsics (VECTOR_DISTANCE, VECTOR_NORM, and VECTOR_NORMALIZE) leak sqlservr.exe process memory to low‑privilege, authenticated SQL Server users if the distance metric or norm algorithm is specified as varchar(max). - SQL Server Engine - Programmability - Linux, Windows
• 5337381 - This fix resolves a memory leak that occurs if the sys.dm_exec_input_buffer dynamic management function (DMF) or the DBCC INPUTBUFFER command is used. - SQL Server Engine - Query Execution - Linux, Windows
• 5336749 - This fix addresses input validation and sanitization of user input for a parameter that's passed to an internal replication stored procedure by validating and sanitizing the input before the stored procedure uses it. - SQL Server Engine - Replication - Linux, Windows
• 5263357 - This fix resolves an SQL injection vulnerability in SQL Server in which improper neutralization of special elements in SQL Server commands allows an authenticated attacker to elevate privileges over a network. - SQL Server Engine - SQL Agent - Linux, Windows

How to obtain and install the update

Method 1: Windows Update

This update is available through Windows Update. When you turn on automatic updating, this update will be downloaded and installed automatically. For more information about how to turn on automatic updating, see Windows Update: FAQ.

Method 2: Microsoft Update Catalog

To get the standalone package for this update, go to the Microsoft Update Catalog website.

Note

• The detection logic has been updated for this and future security releases that are posted to the Microsoft Update Catalog website. For more information, see Updates to the Microsoft Update detection logic for SQL Server servicing.
• This update is made available through the Microsoft Update Catalog for all servers that are running SQL Server, even if Power BI Report Server is not installed. Installing this security update is optional for computers that do not host Power BI Report Server. For more information, see Download Power BI Report Server.

Method 3: Microsoft Download Center

The following file is available for download from the Microsoft Download Center:

Download the package now

How to obtain or download the latest cumulative update package for Linux

To update SQL Server 2025 on Linux to the latest CU, you must first have the Cumulative Update repository configured. Then, update your SQL Server packages by using the appropriate platform-specific update command.

For installation instructions and direct links to the CU package downloads, see the SQL Server 2025 Release Notes.

More information

Prerequisites

To apply this update, you must have SQL Server 2025 or any SQL Server 2025 CU release through this SQL Server 2025 CU6 GDR installed.

Security update deployment information

For deployment information about this update, see Deployments - Security Update Guide.

File hash information

File name - SHA256 hash

SQLServer2025-KB5101346-x64.exe - 7C11D53C5C4F84176C84A0A578FE8F2F953EE2A4F986D4AAB70A0C4833B1E804

File information

The English version of this package has the file attributes (or later file attributes) that are listed in the following worksheet. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For all supported x64-based versions - Download the list of files that are included in security update 5101346.

Information about protection and security

Protect yourself online: Windows Security support

Learn how we guard against cyber threats: Microsoft Security

Original source

Applies To

SQL Server 2025 on Windows (all editions), SQL Server 2025 on Linux (all editions)

Summary

This security update contains fixes and resolves vulnerabilities. To learn more about the vulnerabilities, see the following security advisories:

• CVE-2026-47295 - Microsoft SQL Server Elevation of Privilege Vulnerability
• CVE-2026-47296 - Microsoft SQL Server Elevation of Privilege Vulnerability
• CVE-2026-50468 - Microsoft SQL Server Information Disclosure Vulnerability
• CVE-2026-54116 - Windows MultiPoint Services Elevation of Privilege Vulnerability
• CVE-2026-54117 - Microsoft SQL Server Remote Code Execution Vulnerability
• CVE-2026-54118 - Microsoft SQL Server Remote Code Execution Vulnerability
• CVE-2026-55002 - Microsoft SQL Server Elevation of Privilege Vulnerability

The Microsoft SQL Server components are updated to the following builds in this security update:

• SQL Server - product version: 17.0.1125.2, file version: 2025.170.1125.2

Important

To help secure SQL Server on Windows, enable encryption with Extended Protection.

Known issues in this update

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:

Msg 7416, Level 16
Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416.

Improvements and fixes included in this update

A downloadable Microsoft Excel workbook that contains a summary list of builds, together with their current support lifecycle, is available. The Excel file also contains detailed fix lists.

Download this Excel file now.

Note

Individual entries in the following table can be referenced directly through a bookmark. If you select any bug reference ID in the table, a bookmark tag is added to the URL by using the "#bkmk_NNNNNNN" format. You can then share this URL with others so that they can jump directly to the desired fix in the table.

Bug reference 5264018

Upgrades SQL Server Integration Services (SSIS) password-based encryption (EncryptAllWithPassword and EncryptSensitiveWithPassword) to use PBKDF2 with SHA-256 and 100,000 iterations for packages that target SQL Server 2025. Packages that are saved after this update, including packages that are generated by the Import and Export Wizard, require compatible versions of SQL Server Data Tools (SSDT) and SQL Server Management Studio (SSMS) to open. Until Microsoft releases compatible versions, see the SSDT and SSMS release notes. Packages that target SQL Server 2022 and earlier versions aren't affected.

Bug reference 5295777

This fix resolves an insecure deserialization vulnerability in MessageQueueTask by removing support for the legacy BinaryMessageFormatter (2000 format). MessageQueueTask prevents remote code execution from untrusted Microsoft Message Queuing (MSMQ) messages.

Bug reference 5298237

This fix resolves an insecure deserialization vulnerability in MessageQueueTask by restricting SoapFormatter deserialization that uses an allow list binder. The restriction prevents remote code execution (RCE) from untrusted Microsoft Message Queuing (MSMQ) message.

Bug reference 5160132

This fix prevents unintended EXECUTE permission inheritance for EXTERNAL MODEL objects if a newly created principal reuses the same ID as a previously existing principal that had this permission.

Bug reference 5332063

This fix addresses a vulnerability in SQL Server in which vector intrinsics (VECTOR_DISTANCE, VECTOR_NORM, and VECTOR_NORMALIZE) leak sqlservr.exe process memory to low‑privilege, authenticated SQL Server users if the distance metric or norm algorithm is specified as varchar(max).

Bug reference 5335508

This fix resolves a memory leak that occurs if the sys.dm_exec_input_buffer dynamic management function (DMF) or the DBCC INPUTBUFFER command is used.

Bug reference 5336752

This fix addresses input validation and sanitization of user input for a parameter that's passed to an internal replication stored procedure by validating and sanitizing the input before the stored procedure uses it.

Bug reference 5196011

This fix resolves an SQL injection vulnerability in SQL Server in which improper neutralization of special elements in SQL Server commands allows an authenticated attacker to elevate privileges over a network.

How to obtain and install the update

Method 1: Windows Update

This update is available through Windows Update. When you turn on automatic updating, this update will be downloaded and installed automatically. For more information about how to turn on automatic updating, see Windows Update: FAQ.

Method 2: Microsoft Update Catalog

To get the standalone package for this update, go to the Microsoft Update Catalog website.

Note

• The detection logic has been updated for this and future security releases that are posted to the Microsoft Update Catalog website. For more information, see Updates to Microsoft Update detection logic for SQL Server servicing.
• This update is made available through the Microsoft Update Catalog for all servers that are running SQL Server, even if Power BI Report Server is not installed. Installing this security update is optional for computers that do not host Power BI Report Server. For more information, see Download Power BI Report Server.

Method 3: Microsoft Download Center

The following file is available for download from the Microsoft Download Center:

Download the package now

More information

Prerequisites

To apply this update, you must have SQL Server 2025 or any SQL Server 2025 GDR release through this SQL Server 2025 GDR installed.

Security update deployment information

For deployment information about this update, see Deployments - Security Update Guide.

File hash information

File name: SQLServer2025-KB5091223-x64.exe

SHA256 hash: 64EB41E9B91EC15BCEA01880B4CDF52B95DF6595E9989C49FBA4AC194AC9880A

File information

The English version of this package has the file attributes (or later file attributes) that are listed in the following worksheet. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For all supported x64-based versions - Download the list of files that are included in security update 5091223.

Information about protection and security

Protect yourself online: Windows Security support

Learn how we guard against cyber threats: Microsoft Security

Original source

This cumulative update for Windows 11, version 26H1 (KB5101649) includes the latest security fixes and improvements, along with non-security updates from last month's optional preview release. Visit the Windows release health dashboard for the latest status on this release.

Improvements

This update includes new features and quality improvements that were part of the following update:

• June 9, 2026—KB5095051 (OS Build 28000.2269)
• June 23, 2026—KB5095091 (OS Build 28000.2340) Preview

This update addresses security vulnerabilities documented in the following guide:

• July 2026 Security Updates

The following summary outlines key quality improvements addressed by this update. The bold text within the brackets indicates the item or area of the change.

• [Secure Boot] This update includes additional high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Certificate deployment via Windows updates continues across supported PCs and non-managed business devices in the coming months.
• [Apps (Known issue)] Fixed: This update addresses an issue that affects certain third-party apps that use OLE Automation to interact with Microsoft Office. After installing the June 2026 security update (KB5095091), these apps might fail to launch Office or open documents.
• [Input] This update changes hotkey unregister and cleanup behavior. In rare cases, some built-in Windows experiences that rely on previous hotkey lifecycle behavior might temporarily stop responding to certain keyboard shortcuts. This issue can typically be resolved by restarting the app affected. If the issue is not resolved, report it through the Feedback Hub.
• [Management] With this update, at.exe and schedcli.dll can no longer be used to administer "AT Time" or ATSvc servers. Microsoft recommends discontinuing use of ATServer, which has been disabled by default since Windows Server 2012. Developers and system administrators should expect AT.exe and ATServer to be removed in future versions of Windows. The AT Client, at.exe is replaced by "schtasks.exe", PowerShell ScheduledTasks commands, and the ITaskSchedulerService interface.
• [Networking] This update introduces a security hardening change that enforces TDI transport registration requirements. As a result, applications that use sockets over unregistered third-party TDI transports might stop working after installing this update. Registered TDI transports are not affected. For more information, see Third-party TDI transports might stop working after installing Windows security updates released on or after July 14, 2026.
• [Remote Desktop (RDP) Security] Support for SHA-2 certificate thumbprints has been added for trusted RDP publishers, with SHA-1 support retained only for backward compatibility and planned for future removal. New guidance is available for managing RDP file security through Group Policy to help organizations reduce phishing risks by controlling which .rdp files users can open. We recommend IT administrators migrate to SHA-256 thumbprints or a stronger algorithm as soon as possible to avoid disruption.

If you've already installed previous updates, your device will download and install only the new updates included in this package.

Components updates

Known issues in this update

Microsoft is not currently aware of any issues with this update.

How to get this update

Before you install this update

Microsoft combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates.

Deployment

If you deploy dynamic updates such as this update to an existing Windows image, ensure the boot.stl file is included as part of the installation media. Failure to include the file might prevent devices from successfully starting from the installation media and can result in error code 0xc0430001.

Note

The boot.stl file is used during Secure Boot validation and must match the Windows version and architecture of the image you are updating.

To ensure the boot.stl file is included as part of the installation media, do one of the following:

• Use the Update WinPE script to update an existing Windows image. (Recommended)
• Manually copy the boot.stl file from the device Windows\Boot\EFI folder to the corresponding folder on your installation media before deploying the update.

For information about how to apply Dynamic Update packages to existing Windows images, see Update Windows installation media with Dynamic Update.

Install this update

To install this update, use one of the following Windows and Microsoft release channels.

File information

For a list of the files provided in this update, download the file information for cumulative update 5101649​​​​​​​​​.

For a list of the files provided in the servicing stack update, download the file information for the SSU (5121292) - version 28000.2524.

Related topics

Windows monthly updates explained

Description of the standard terminology used for Microsoft software updates

Windows release health

Original source

This cumulative update for Windows 11, version 23H2 (KB5099414), includes the latest security fixes and improvements, along with non-security updates from last month’s optional preview release. Visit the Windows release health dashboard for the latest status on this release.

Want a quick overview? Watch the Windows 11, version 24H2 and version 25H2 video.

Announcements and messages

This section provides key notifications related to this release, including announcements, change logs, and end-of-support notices.

Windows Secure Boot certificate expiration

Important: Secure Boot certificates used by most Windows devices are set to expire starting in June 2026. Microsoft has been updating these certificates on consumer and non-managed business devices over the past several months. Devices that haven’t received the newer certificates will continue to start and operate normally, and standard Windows updates will continue to install. Updated certificates will continue to be delivered through Windows Update in the coming months.

Improvements

This update addresses security issues for your Windows operating system.

Important

Use EKB KB5027397 to update to Windows 11, version 23H2.

This security update contains fixes and quality improvements from KB5093998 (released June 09, 2026). The following summary outlines key issues addressed by this update. Also, included are available new features. The bold text within the brackets indicates the item or area of the change.

• [Secure Boot] This update includes additional high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Certificate deployment via Windows updates continues across supported PCs and non-managed business devices in the coming months.
• [Apps (Known issue)] Fixed: This update addresses an issue that affects certain third-party apps that use OLE Automation to interact with Microsoft Office. After installing the June 2026 security update (KB5093998), these apps might fail to launch Office or open documents.
• [Country and Operator Settings Asset (COSA)] This update brings profiles up to date for certain mobile operators.
• [File Explorer (known issue)] Fixed: An issue where the OneDrive shortcut in File Explorer stops working when File Explorer is run with administrative mode.This issue might occur after installing the June 2026 security update (KB5093998).
• [Input] This update changes hotkey unregister and cleanup behavior. In rare cases, some built-in Windows experiences that rely on previous hotkey lifecycle behavior might temporarily stop responding to certain keyboard shortcuts. This issue can typically be resolved by restarting the app affected. If the issue is not resolved, report it through the Feedback Hub.
• [Networking] This update introduces a security hardening change that enforces TDI transport registration requirements. As a result, applications that use sockets over unregistered third-party TDI transports might stop working after installing this update. Registered TDI transports are not affected. For more information, see Third-party TDI transports might stop working after installing Windows security updates released on or after July 14, 2026.
• [Recycle Bin (known issue)] Fixed: This update addresses an issue where the confirmation dialog might display an internal Recycle Bin file name instead of the original file name when permanently deleting a file. This issue might occur after installing the June 2026 security update (KB5093998).
• [Security] This update upgrades the curl tool in Windows to version 8.21.0 and includes security improvements that help protect your device.
• [Remote Desktop (RDP) Security] Support for SHA-2 certificate thumbprints has been added for trusted RDP publishers, with SHA-1 support retained only for backward compatibility and planned for future removal. New guidance is available for managing RDP file security through Group Policy to help organizations reduce phishing risks by controlling which .rdp files users can open. We recommend IT administrators migrate to SHA-256 thumbprints or a stronger algorithm as soon as possible to avoid disruption.

If you've already installed previous updates, your device will download and install only the new updates included in this package.

For more information about security vulnerabilities, see the Security Update Guide and the July 2026 Security Update.

Windows 11 servicing stack update (KB5104023) - 22621.7373

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates. To learn more about SSUs, see Simplifying on-premises deployment of servicing stack updates.

Known issues in this update

Microsoft is not currently aware of any issues with this update.

How to get this update

Before you install this update

Microsoft combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates.

Deployment

If you deploy dynamic updates such as this update to an existing Windows image, ensure the boot.stl file is included as part of the installation media. Failure to include the file might prevent devices from successfully starting from the installation media and can result in error code 0xc0430001.

Note

The boot.stl file is used during Secure Boot validation and must match the Windows version and architecture of the image you are updating.

To ensure the boot.stl file is included as part of the installation media, do one of the following:

• Use the Update WinPE script to update an existing Windows image. (Recommended)
• Manually copy the boot.stl file from the device Windows\Boot\EFI folder to the corresponding folder on your installation media before deploying the update.

For information about how to apply Dynamic Update packages to existing Windows images, see Update Windows installation media with Dynamic Update.

Install this update

To install this update, use one of the following Windows and Microsoft release channels.

Windows Update

Available

This update downloads and installs automatically from Windows Update and Microsoft Update.

File information

For a list of the files provided in this update, download the file information for cumulative update 5099414.

For a list of the files provided in the servicing stack update, download the file information for the SSU (KB5104023) - versions 22621.7373.

Related topics

Windows release health

Microsoft Store for Business and Education with Configuration Manager

Get updates for apps and games in Microsoft Store

Original source

This cumulative update for Windows 11, version 25H2 and 24H2 (KB5101650) includes the latest security fixes and improvements, along with non-security updates from last month's optional preview release. Visit the Windows release health dashboard for the latest status on this release.

Want a quick overview?: Watch the Windows 11 release note video for this update.

Announcements and messages

This section provides key notifications related to this release, including announcements, change logs, and end-of-support notices.

Update temporarily unavailable for some Dell devices with Intel processors

Important

This update might not be available for a limited number of Dell devices with Intel processors due to an incompatibility reported by Dell that can potentially cause unexpected shutdowns, poor performance, increased heat, and battery drain. We are working together with Dell to prevent the affected models from experiencing the issue and plan to release a resolution for affected devices in the coming days.

Improvements

This update includes new features and quality improvements that were part of the following update:

• June 9, 2026—KB5094126 (OS Builds 26200.8655 and 26100.8655)
• June 23, 2026—KB5095093 (OS Builds 26200.8736 and 26100.8736) Preview

This update addresses security vulnerabilities documented in the following guide:

• July 2026 Security Updates

The following summary outlines key quality improvements addressed by this update. The bold text within the brackets indicates the item or area of the change.

• [Secure Boot] This update includes additional high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Certificate deployment via Windows updates continues.
• [Apps (Known issue)] Fixed: This update addresses an issue that affects certain third-party apps that use OLE Automation to interact with Microsoft Office. After installing the June 2026 security update (KB5094126), these apps might fail to launch Office or open documents.
• [Input] This update changes hotkey unregister and cleanup behavior. In rare cases, some built-in Windows experiences that rely on previous hotkey lifecycle behavior might temporarily stop responding to certain keyboard shortcuts. This issue can typically be resolved by restarting the app affected. If the issue is not resolved, report it through the Feedback Hub.
• [Networking] This update introduces a security hardening change that enforces TDI transport registration requirements. As a result, applications that use sockets over unregistered third-party TDI transports might stop working after installing this update. Registered TDI transports are not affected. For more information, see Third-party TDI transports might stop working after installing Windows security updates released on or after July 14, 2026.
• [Recycle Bin (known issue)] Fixed: This update addresses additional scenarios where the confirmation dialog might display an internal Recycle Bin file name instead of the original file name when permanently deleting a file. This issue might occur after installing the June 2026 security update (KB5094126).
• [Security] This update upgrades the curl tool in Windows to version 8.21.0 and includes security improvements that help protect your device.
• [Remote Desktop (RDP) Security] Support for SHA-2 certificate thumbprints has been added for trusted RDP publishers, with SHA-1 support retained only for backward compatibility and planned for future removal. New guidance is available for managing RDP file security through Group Policy to help organizations reduce phishing risks by controlling which .rdp files users can open. We recommend IT administrators migrate to SHA-256 thumbprints or a stronger algorithm as soon as possible to avoid disruption.

If you've already installed previous updates, your device will download and install only the new updates included in this package.

Known issues in this update

Microsoft is not currently aware of any issues with this update.

How to get this update

Before you install this update

Microsoft combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates.

Deployment

If you deploy dynamic updates such as this update to an existing Windows image, ensure the boot.stl file is included as part of the installation media. Failure to include the file might prevent devices from successfully starting from the installation media and can result in error code 0xc0430001.

Note

The boot.stl file is used during Secure Boot validation and must match the Windows version and architecture of the image you are updating.

To ensure the boot.stl file is included as part of the installation media, do one of the following:

• Use the Update WinPE script to update an existing Windows image. (Recommended)
• Manually copy the boot.stl file from the device Windows\Boot\EFI folder to the corresponding folder on your installation media before deploying the update.

For information about how to apply Dynamic Update packages to existing Windows images, see Update Windows installation media with Dynamic Update.

Install this update

To install this update, use one of the following Windows and Microsoft release channels.

Windows Update

Available: Included

Next Step: This update downloads and installs automatically from Windows Update and Microsoft Update.

File information

For a list of the files provided in this update, download the file information for cumulative update 5101650.

For a list of the files provided in the servicing stack update, download the file information for the SSU (KB5120102) - version 26100.8872.

Related topics

Windows monthly updates explained

Description of the standard terminology used for Microsoft software updates

Microsoft Store for Business and Education with Configuration Manager

Get updates for apps and games in Microsoft Store

Original source

[1.11.0] - 2026-07-09

Added

• agent-framework-core: Add message injection middleware so tools or host code can enqueue messages into an active run and drain them into the next model call within the same AgentSession (#6998)
• agent-framework-core: Integrate message injection into create_harness_agent and the harness console sample so a running harness agent can be nudged mid-turn (#7027)
• agent-framework-core: Add progressive MCP disclosure so agents can discover, load, and unload MCP tool schemas on demand while keeping the allowed_tools boundary intact (#6850)
• agent-framework-core: Add refresh_interval (TTL) to CachingSkillsSource so cached skill lists expire and re-fetch on a configured interval (#6977)
• agent-framework-core, agent-framework-foundry-hosting: Add SkillsSourceContext (invoking agent plus optional session) threaded through the skills source pipeline, enabling context-aware filtering and per-key cache isolation (#6895)
• agent-framework-core: Allow disabling approval for SkillsProvider tools (#6867)
• agent-framework-core: Allow opting out of FileAccessProvider tool approval (#6879)
• agent-framework-core: Allow custom argument parsing for inline skill scripts so non-conforming tool-call argument shapes (for example, vLLM) can be handled (#6817)
• agent-framework-hosting, agent-framework-hosting-responses: Add a hosting protocol helper surface (AgentState, WorkflowState, SessionStore, AgentRunArgs, WorkflowRunArgs) and Responses helpers (create_response_id, responses_session_id, responses_to_run, responses_from_run, responses_from_streaming_run) (#6891)
• agent-framework-ag-ui: Add FastAPI SSE keepalive support for long, output-silent streams (#6980)
• agent-framework-github-copilot: Forward skill_directories and disabled_skills to the Copilot session (#6937)
• agent-framework-openai: Allow tool_choice: required when allowed_tools is set (#7024)
• agent-framework-anthropic, agent-framework-core, agent-framework-foundry-hosting, agent-framework-gemini, agent-framework-openai: Mark hosted/provider-executed tool calls as informational-only via Content.informational_only so they remain visible in transcripts without local re-invocation (#6997)
• samples: Add a deterministic action-boundary validation middleware sample (#6528)
• samples: Add Agent Harness blog post accompanying samples, part 3 (#6741)
• samples: Add a declarative Foundry Hosted Agent workflow sample (#6897)

Changed

• agent-framework-core: [BREAKING — experimental] Extract caching from SkillsProvider into a CachingSkillsSource decorator (#6847)
• agent-framework-core: [BREAKING — experimental] Treat nested SKILL.md content as part of the parent skill instead of discovering it as a separate skill root (#6849)
• agent-framework-core: [BREAKING — experimental] FileAccess/FileMemory replace_lines now performs literal replacement (including line deletion) instead of always re-adding a line terminator (#6859)
• agent-framework-core: Remove the experimental marker from the Skills API now that its surface is stable (#6974)
• agent-framework-core: Lazy-load root agent_framework exports to reduce import cost for narrow-surface scenarios (#6962)
• agent-framework-a2a, agent-framework-claude, agent-framework-copilotstudio, agent-framework-core, agent-framework-durabletask, agent-framework-github-copilot, agent-framework-purview: Implement ADR-0029 service_session_id lifecycle mapping, separating durable continuation state, per-run identity forwarding, and telemetry conversation-id extraction (#6724)
• agent-framework-azurefunctions, agent-framework-core, agent-framework-durabletask: [BREAKING] Support multi-workflow hosting and sub-workflows on the Durable Task host, including per-workflow durable naming and nested human-in-the-loop request routing (#6696)
• agent-framework-ag-ui: [BREAKING] Canonicalize AG-UI interrupt and resume handling around RUN_FINISHED.outcome.interrupts and canonical ResumeEntry payloads (#6925)
• agent-framework-mem0: Support the mem0ai 2.x OSS search call shape (#7004)
• agent-framework-mistral: Widen the uv_build backend requirement to allow newer uv releases (#7033)
• agent-framework-lab: Raise the agentlightning dependency ceiling for the lightning extra (#6984)
• agent-framework-claude, agent-framework-durabletask, agent-framework-gemini, agent-framework-monty, agent-framework-openai: Raise dependency floors to the first versions that provide the SDK APIs and typing consumed by these packages
• docs: Clarify AgentSession.service_session_id scoping to document backing API key/project boundaries and hosted multi-tenant guidance (#6993)
• docs: Add security guidance for external skill sources and script execution to harness feature docstrings (#6936)
• samples: Bump vite and @vitejs/plugin-react-swc in the ChatKit integration sample frontend (#6613)
• samples: Add a multi-tenant hosting security consideration note to the A2A sample (#6983)
• samples: Update Foundry Hosted Agent samples for the v2 protocol changes (#6841)
• samples: Use a writable runtime directory for the Foundry Skills sample (#6606)
• tests: Add Agent typing smoke tests across chat clients (#6950)
• tests: Skip NumPy stubs during mypy typing to unblock scheduled dependency-maintenance typing runs (#6969)
• tests: Consolidate Dependabot dependency updates for dev tooling (uv, ruff, pytest, mypy, pyright, mcp, opentelemetry-sdk, poethepoet) across the workspace and package dev-dependency groups (#6984, #7033)
• tests: Bump the transitive js-yaml dependency in the DevUI frontend lockfile (#6813)

Fixed

• agent-framework-core: Parse the structured response value from the final message instead of concatenated text, avoiding spurious ValidationError/JSONDecodeError (#6383)
• agent-framework-core: Fix read_skill_resource instruction dropping the .md extension (#7031)
• agent-framework-core: Bind policy-enforcement approvals to a single tool invocation (call id, function, arguments, security label, and session) and consume them on first use (#6966)
• agent-framework-core: Process messages to an executor serially within a superstep to prevent concurrent handler invocations for the same target executor (#6776)
• agent-framework-core: Auto-inject local conversation history on stateless clients even when non-history context providers (for example, SkillsProvider and FileAccessProvider) are registered (#6810)
• agent-framework-core: Improve the error message when a TypeVar is used in handler/executor registration (#4553)
• agent-framework-anthropic, agent-framework-core: Fix Anthropic requests that mix tool calls and tool results in one assistant message, and return a deterministic result when the function-loop limit is reached with a blank final response (#6794)
• agent-framework-anthropic, agent-framework-core, agent-framework-foundry-hosting, agent-framework-openai: Fix Foundry reasoning/MCP compaction so reasoning output keeps its provider id and reasoning plus MCP call pairs stay atomic (#6907)
• agent-framework-anthropic: Normalize a single Anthropic tool value the same as a one-item sequence during request preparation (#6903)
• agent-framework-anthropic: Migrate structured outputs to the stable output_config.format shape to avoid malformed/concatenated JSON when tools are also present (#5884)
• agent-framework-azure-ai-search: Pass include_reference_source_data in agentic search requests so source_data is populated on returned references (#5100)
• agent-framework-bedrock: Fix non-ASCII escaping in JSON content blocks returned by the Converse API (#6628)
• agent-framework-foundry: Strip tools from the Foundry agent request on the preview path (allow_preview=True) to avoid invalid_payload errors (#6644)
• agent-framework-gemini: Fix GeminiChatClient dropping image/file content on multimodal messages (#6751)
• agent-framework-claude, agent-framework-core, agent-framework-github-copilot, agent-framework-ollama: Fix response metadata construction so usage, finish reason, raw response, continuation token, and structured value are propagated consistently across providers (#6955)
• agent-framework-a2a: Accept A2A data URIs whose media type includes parameters before the ;base64 marker (#6818)
• agent-framework-ag-ui: Prefer explicit AG-UI resume payloads over message-derived responses (#6360)
• agent-framework-ag-ui: Clear queued approvals on cancel so cancelled flows do not leave stale prompts for later turns (#6947)
• agent-framework-ag-ui: Preserve the streamed text message id in mixed snapshots with pending tool calls and streamed trailing text (#6269)
• agent-framework-devui: Fix list[Message] input handling for declarative ToolAgent entries (#6534)
• agent-framework-devui: Fix DevUI deployment Dockerfile auth args (#6150)
• agent-framework-hyperlight: Harden workspace staging against symlinks and reparse points that could escape the sandbox workspace/mount root (#6856)
• agent-framework-openai: Fix web_search_options sent to the Azure OpenAI Chat Completions API (#6225)
• docs: Fix stale ChatAgent references in _clients.py docstrings and make tool-support examples copy/paste-safe (#6924)
• samples: Fix an invalid options kwarg in the workflow shared-session sample (#6294)
• docs: Add prerequisite command documentation for Python hosting samples (#5935)

Removed

• agent-framework-hosting-telegram: [BREAKING] Remove the unreleased hosting-telegram package and the earlier host/channel surface from the workspace, superseded by the new hosting protocol helper surface (#6891)

Full Changelog: python-1.10.0...python-1.11.0

Original source