A laptop displays a Windows 11 Intel OpenVINO update, illustrated powering an AI network across Intel CPU, GPU, and NPU chips.
Microsoft has released KB5136901, which updates the Intel OpenVINO Execution Provider to version 2.2611.1.0 on Windows 11 versions 24H2, 25H2 and 26H2. The KB describes the contents only as "improvements." The more useful detail for readers is when each Windows version gets the update, what it replaces, and how to check that it installed. Microsoft published the KB on November 19, 2026.

A laptop displays a Windows 11 Intel OpenVINO update, illustrated powering an AI network across Intel CPU, GPU, and NPU chips. What KB5136901 covers​

According to Microsoft's KB, the update applies to all editions of Windows 11 versions 24H2, 25H2 and 26H2. It updates the OpenVINO Execution Provider AI component on those versions.

The main facts:

ItemDetail
KB numberKB5136901
ComponentIntel OpenVINO Execution Provider
New version2.2611.1.0
Applies toWindows 11 24H2, 25H2, 26H2 (all editions)
DeliveryDownloaded and installed automatically through Windows Update
PrerequisiteLatest cumulative update for your Windows 11 version
ReplacesKB5128775
Update History entryWindows ML Runtime Intel OpenVINO Execution Provider (KB5136901)

The 24H2 caveat: Windows 11 24H2 is on the list, but Microsoft says it won't offer this update to 24H2 until that version's next servicing period, on or after December 8, 2026. Microsoft gives no reason for the delay and no exact delivery date. If a 24H2 machine doesn't have KB5136901 yet, that is expected and does not mean anything is broken.

Microsoft's KB doesn't list specific bug fixes, performance gains, newly supported models or operators, security fixes or driver requirements. It says "improvements" and nothing more. If anyone claims the update makes something faster, Microsoft's KB doesn't back that up.

Summary: It's an automatic Windows Update package for 24H2, 25H2 and 26H2. Install the latest cumulative update first. 24H2 won't be offered it before December 8, and Microsoft doesn't say what changed.

What an execution provider does​

Microsoft describes the OpenVINO Execution Provider as a component used with ONNX Runtime and Windows Machine Learning (Windows ML). It lets ONNX models run with hardware acceleration on Intel CPUs, GPUs and NPUs.

In Windows ML, execution providers (EPs) are hardware-specific backends that run a model's operations. Microsoft's Windows ML documentation lists the providers that come with Windows ML: CPU, DirectML (legacy), and the experimental Windows ML CG EP. Vendor providers, including OpenVINO (EpName OpenVINOExecutionProvider), are separate. Microsoft lists OpenVINO alongside providers from AMD, NVIDIA and Qualcomm. For OpenVINO, Microsoft points to "Intel Windows ML support" for requirements and driver guidance; it doesn't publish a fixed driver baseline for OpenVINO the way it does for some other vendors.

According to Microsoft's documentation, these vendor providers are downloaded on demand. They are available on Windows 11 24H2 (build 26100) and later, depending on device and driver compatibility. Having an Intel chip doesn't mean your apps use OpenVINO. An app has to use Windows ML or ONNX Runtime and select or register that provider.

Summary: OpenVINO links Windows ML to Intel hardware, but it only helps apps that actually use it.

Where this fits in Microsoft's AI update history​

Microsoft's "Release history of AI updates" page shows that KB5136901 was one of five execution provider updates released on November 19 for the 24H2/25H2/26H2 group: AMD MIGraphX Version 2.2611.1.0 (KB5136903), AMD Vitis Version 2.2611.0.0 (KB5136902), Intel OpenVINO Version 2.2611.1.0 (KB5136901), Nvidia TensorRT-RTX Version 2.2611.1.0 (KB5136900), and Qualcomm QNN Version 2.2611.1.0 (KB5136899). These are separate packages for separate vendors. The AMD, NVIDIA and Qualcomm updates are not part of KB5136901.

Windows 11 26H1 has its own package for the same version: for 26H1, the Intel OpenVINO column lists Version 2.2611.1.0 under KB5136906. If you're looking for KB5136901 on a 26H1 machine, it won't be there. Look for KB5136906 instead.

The same history page shows the previous OpenVINO release for 24H2/25H2/26H2: version 2.2609.2.0 under KB5128775, dated September 22, 2026. That's the update KB5136901 replaces. The October 28 release round had no OpenVINO update, so this is the first new OpenVINO provider for these versions in about two months.

A practical note: the "2611" in the version string matches the November 2026 release across vendors, so it probably reflects a shared Windows ML servicing cadence. That's an inference from the numbering, not something Microsoft documents. It also doesn't mean the same changes went into every vendor's provider.

Summary: Same version as the 26H1 package, different KB number. It replaces the September release, and it's one of five separate vendor EP updates.

How to check that KB5136901 is installed​

For most users, Microsoft's method is enough:

  1. Confirm the PC runs Windows 11 25H2 or 26H2. On 24H2, expect the offer only on or after December 8, 2026. On 26H1, look for KB5136906 instead.
  2. Install the latest cumulative update for your version. It's a prerequisite.
  3. Open Settings > Windows Update > Update history.
  4. Look for the entry Windows ML Runtime Intel OpenVINO Execution Provider (KB5136901).

That entry confirms the update installed.

For developers​

Microsoft's Windows ML guidance says that once a provider is installed, Windows ML updates it automatically. Compatible updates reach your app without you rebuilding or redeploying it. Microsoft also says apps currently can't install an updated EP programmatically, because Windows ML manages the update itself.

To check which version a device has, Microsoft documents reading the provider's PackageId and version from the Windows ML execution provider catalog. If the provider isn't installed, PackageId is null. Compare the reported version with 2.2611.1.0 to see whether the device has the November release.

One caution from experience: a newer provider doesn't guarantee your whole model runs on the Intel NPU or GPU. Operator support, graph partitioning and CPU fallback depend on the provider, the model and the session settings. Benchmark your own workload before and after the update instead of assuming it got faster.

Troubleshooting and managed environments​

If an EP update doesn't appear, Microsoft's Windows ML troubleshooting guidance lists a few common causes:

  • Windows Update is paused. Devices with paused updates can't download providers through the Windows Update path. Resume with Settings > Windows Update > Resume updates.
  • A restart is pending. Some upstream updates need a reboot before the EP download can continue. Restart and check again.
  • Enterprise policy. On managed devices, policies can block component downloads or limit access to Windows Update. Ask IT whether a policy is involved.

A version caveat: the same troubleshooting page says Windows ML 2.5.96 and later get execution providers through the Microsoft Store, while 2.4.89 and earlier used Windows Update. KB5136901 itself is delivered through Windows Update. That guidance is general Windows ML troubleshooting, not a known issue with this KB. Microsoft hasn't reported any problems with KB5136901.

If none of that works, Microsoft suggests filing a report in Feedback Hub under Developer Platform > Windows Machine Learning. Feedback Hub collects the logs the team needs.

For IT admins​

These AI component KBs come out on their own schedule, separate from Patch Tuesday cumulative updates. Each depends on the latest cumulative update being installed. In practice:

  • Make sure pilot devices have the current cumulative update, or the EP update won't arrive.
  • Expect your 24H2 machines to get KB5136901 later than your 25H2 and 26H2 machines.
  • If you run local AI workloads on Intel hardware, such as internal ONNX apps or Windows ML-based tools, test them on a small group first. Microsoft hasn't said what changed, so you can't predict how they'll behave.

Bottom line​

KB5136901 is a small update to the layer between Windows ML and Intel CPUs, GPUs and NPUs. It moves OpenVINO from 2.2609.2.0 to 2.2611.1.0 and replaces KB5128775. It installs automatically on 25H2 and 26H2, and 24H2 has to wait until on or after December 8. Microsoft only says it contains "improvements," so treat it as routine maintenance, not a new feature. Install the latest cumulative update, look for the Update History entry above, and if you rely on Intel-accelerated AI apps, test them yourself.

 

References

  1. KB5136901: Intel OpenVINO Execution Provider update (version 2.2611.1.0) | Microsoft Support Microsoft Support 2026-11-19T00:00:00+00:00
  2. KB5136901: Intel OpenVINO Execution Provider update (version 2.2611.1.0) | Microsoft Support support.microsoft.com
  3. Windows ML execution providers | Microsoft Learn learn.microsoft.com