KB 5079063 Logs Five Execution Provider Updates for September 22
KB 5079063 is a running record, not a single-update KB. It applies to all editions of Windows 11 version 26H1, 25H2 and 24H2. Microsoft's summary recommends installing the latest AI updates on "AI-capable" Windows devices. It also tells readers to check installed components under Settings > Windows Update > Update history. The newest entries sit at the top of each table, and each entry has its own KB article.
The September 22, 2026 row is a provider-only release. All five execution provider families in both Windows version groups got a new build on the same day. That hasn't happened since May 26, 2026, the last date on which every column carried a version number. The months in between were partial. On August 27, only Intel OpenVINO and Qualcomm QNN moved. On July 28, AMD Vitis, Nvidia TensorRT-RTX and Qualcomm QNN updated while the other two columns read "No Update."
The version numbers follow a readable pattern. Since March 2026, provider builds use a 2.YYMM.x.0 scheme, so 2.2609.x.0 points to a September 2026 build. The February 2026 and 2025 entries used a 1.8.x.0 numbering instead, such as 1.8.63.0 for OpenVINO and 1.8.30.0 for QNN. The history page doesn't explain the switch. What it does show is that version 1 and version 2 provider builds belong to different eras of the table.
Windows ML Execution Providers Are the Plumbing Under Third-Party AI Apps
An execution provider is the vendor-specific backend that lets a machine-learning runtime send a model to particular hardware. Microsoft's KB for an earlier OpenVINO release describes the Intel provider as an execution provider used with ONNX Runtime/Windows machine learning to enable hardware-accelerated inference on Intel platforms. The same KB says it accelerates ONNX models on Intel CPUs, GPUs, and NPUs, allowing Windows and applications to take advantage of Intel hardware optimizations for machine learning workloads. The other four entries fill the same role for their own silicon: MIGraphX and Vitis for AMD, TensorRT-RTX for Nvidia GPUs, and QNN for Qualcomm.
Shipping these through Windows Update is the whole point of the design. When Intel introduced its OpenVINO provider for Windows ML, it said the integration enables seamless updates and maintenance of the Execution Provider without requiring application rebuilds or code modifications from developers. In practice, a developer building on Windows ML doesn't bundle each vendor's acceleration library. Windows maintains the providers, and the monthly rows in KB 5079063 are the visible record of that work.
So the September 22 update matters mostly to machines running software that uses Windows ML. It matters less to users waiting for a new Windows feature. The history page makes no claims about performance or new capabilities. The individual KBs Microsoft has published for this component class use generic wording. The earlier OpenVINO KBs, for example, say only that each update includes improvements to the OpenVINO Execution Provider AI component for Windows 11, version 24H2 and Windows 11, version 25H2. Treat these as maintenance releases, not feature drops.
26H1 and 24H2/25H2 Get Different KBs and Different OpenVINO Builds
Microsoft keeps two separate tables: one for Windows 11 version 26H1, and one shared by versions 24H2 and 25H2. Each group has its own KB numbers for the same September 22 components, and one component differs in version too.
| Execution provider | 26H1 version | 26H1 KB | 24H2/25H2 version | 24H2/25H2 KB |
|---|---|---|---|---|
| AMD MIGraphX | 2.2609.2.0 | KB5128778 | 2.2609.2.0 | KB5128774 |
| AMD Vitis | 2.2609.1.0 | KB5128777 | 2.2609.1.0 | KB5128773 |
| Intel OpenVINO | 2.2608.0.0 | KB5128779 | 2.2609.2.0 | KB5128775 |
| Nvidia TensorRT-RTX | 2.2609.1.0 | KB5128780 | 2.2609.1.0 | KB5128776 |
| Qualcomm QNN | 2.2609.3.0 | KB5128782 | 2.2609.3.0 | KB5128781 |
Intel OpenVINO is the odd one out. On 24H2 and 25H2 it moves to 2.2609.2.0 under KB5128775. That supersedes the August 27 build, 2.2608.0.0 (KB5123773), which in turn replaced the previously released update KB5103225 from June. On 26H1, though, the September 22 entry lists version 2.2608.0.0 under the new KB5128779. That is the same version number 26H1 already got on August 27 under KB5123774. The history page gives no reason for re-issuing that version under a fresh KB. Anyone auditing a 26H1 fleet should match on the KB number, not the version string alone.
The two groups also have separate histories. The 24H2/25H2 provider table goes back to September 25, 2025, with KB5067990 as the first OpenVINO entry at version 1.8.15.0. The 26H1 table starts on February 10, 2026. The early rows show 26H1 getting builds that 24H2/25H2 had already received a few weeks before. The 26H1 February 10 set, including OpenVINO 1.8.63.0 (KB5078979), matches the version numbers 24H2/25H2 got on January 29, 2026.
Microsoft's per-component KBs set the same prerequisites for each group. For 24H2 and 25H2, you must have the latest cumulative update for Windows 11, version 24H2 or Windows 11, version 25H2 installed. The 26H1 KB for OpenVINO 1.8.63.0 has an equivalent rule: You must have the latest cumulative update for Windows 11, version 26H1 installed.
Copilot+ PC Components Sit Out the September 22 Cycle
KB 5079063 has a second table for each Windows group, titled "Windows AI Components for Copilot+ PCs only." It holds the on-device models behind Copilot+ features: Image Transform, Image Creation, Image Processing, and Phi Silica, Microsoft's small on-device language model. The table has four columns: "All systems," AMD-powered, Intel-powered and Qualcomm-powered. For September 22, 2026, every column reads "No update" in both the 26H1 and the 24H2/25H2 tables.
The latest Copilot+ row is August 27, 2026, and the two Windows groups got different builds that day. On 24H2 and 25H2, Image Transform, Image Creation, Image Processing and Phi Silica all went to version 1.2608.951.0. The KB number depends on the component and the processor column. For example, Image Transform is KB5124882 under "All systems," while Phi Silica is KB5124881 on AMD, KB5124880 on Intel and KB5124879 on Qualcomm. Intel systems get a separate "OpenVino Image Creation" component (KB5124885).
On 26H1, the August 27 row lists version 1.2607.840.0 for most components. The exception is Qualcomm Image Creation at 1.2607.837.0 (KB5125075). Qualcomm systems on 26H1 also have a separate "Phi Silica J32" entry (KB5124890). The 1.2607.840.0 builds match what 24H2/25H2 received on July 28. The 26H1 table also shows "No update" for July 28, 2026, when 24H2/25H2 did get Copilot+ builds. The 24H2/25H2 table, for its part, shows "No update" for June 23, when 26H1 got one. By this observation, the two groups run on offset schedules rather than moving together. Microsoft doesn't explain the gaps, and the "No update" entries don't indicate a fault.
The overall picture is clear. If you're on a Copilot+ PC, the September 22 cycle doesn't change your Phi Silica or imaging model versions. Only the execution providers moved.
Checking Update History Against the KB 5079063 Tables
Microsoft's KBs for this component class say the updates arrive with no action from the user. The OpenVINO KBs state that each update will be downloaded and installed automatically from Windows Update. The KB 5079063 page gives no rollout schedule, so a device may not show the September 22 builds right away. Confirming what a machine has installed takes a few steps:
- Confirm which Windows 11 version the device runs: 26H1, 24H2 or 25H2. This decides which table and which KB numbers apply.
- Make sure the latest cumulative update for that version is installed. The component KBs list it as a prerequisite.
- Open Settings > Windows Update > Update history. Look for entries whose names follow the pattern Microsoft documents. For OpenVINO, that looks like Windows ML Runtime Intel OpenVINO Execution Provider (KB5123773).
- Compare the KB number you find with the September 22 row for your Windows group. On a 24H2 or 25H2 machine, a current OpenVINO provider shows KB5128775. On 26H1 it shows KB5128779.
Success means the KB numbers in Update history match the table row for your Windows version and hardware. The page doesn't say which providers get installed on which hardware. It is reasonable to infer that a device only receives providers relevant to its silicon, but KB 5079063 doesn't document that. Don't treat a missing AMD or Nvidia entry on an Intel laptop as a failure. The page also includes no removal, rollback or troubleshooting steps for these components.
What this means for you
Most readers don't need to do anything. The September 22 execution provider builds install through Windows Update, and the Copilot+ models didn't change. The people who should pay attention are those who manage fleets or build on Windows ML. They need to know which provider version a machine is running before testing or explaining a change in an AI workload.
Developers whose apps rely on Windows ML hardware acceleration should treat September 22 as a new baseline. All five vendors' providers changed, and the updates come without any app rebuild. That makes KB 5079063 the quickest way to pin down which provider build was live when a behavior change first showed up. Administrators with mixed fleets should keep 26H1 and 24H2/25H2 machines in separate reporting groups, because the KB numbers never overlap between them.
- On September 22, 2026, Microsoft released new builds of all five Windows ML execution providers: AMD MIGraphX, AMD Vitis, Intel OpenVINO, Nvidia TensorRT-RTX and Qualcomm QNN.
- Windows 11 26H1 and Windows 11 24H2/25H2 get different KB numbers for the same component, such as KB5128779 versus KB5128775 for Intel OpenVINO.
- On 26H1, Intel OpenVINO stays at version 2.2608.0.0 under a new KB, while 24H2/25H2 moves to 2.2609.2.0. Audit by KB number, not by version string.
- The Copilot+ PC-only components (Phi Silica, Image Transform, Image Creation and Image Processing) show "No update" for September 22. Their latest builds are from August 27.
- These components install automatically through Windows Update after the latest cumulative update is present, and you can check them under Settings > Windows Update > Update history.
KB 5079063 has become Microsoft's single ledger for AI components that ship outside the regular cumulative updates. The September 22 entry shows that ledger working as designed: vendor acceleration code for every major PC chip family was refreshed in one cycle, with no app changes needed. New rows have appeared roughly once a month through 2026, the latest on August 27 and September 22. That pace makes this page the reference to check whenever a Windows ML workload behaves differently from one month to the next.