Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Windows ML packages include a copy of the ONNX Runtime, so that your app can depend on an optional shared system-wide copy of the ONNX Runtime rather than distributing your own copy (if you choose framework-dependent deployment). See Install and deploy Windows ML for more details.
Versions of ONNX Runtime in Windows ML
The following tables clarify which ONNX Runtime (ORT) commit was shipped with each Windows ML package release.
Note
Only the current release is officially supported. Past and preview/experimental versions are shown for release history only.
The 2.x versions of Windows ML ship ORT version 1.24 or higher via the Microsoft.Windows.AI.MachineLearning NuGet package. If you're using Microsoft.WindowsAppSDK.ML, check that package's dependency on Microsoft.Windows.AI.MachineLearning to determine which ORT version applies to your app.
Current release
| Microsoft.Windows.AI.MachineLearning version | Release date | ONNX Runtime commit hash | ONNX Runtime date |
|---|---|---|---|
2.1.71 |
6/10/2026 | 800ac32 (1.24.6) |
4/28/2026 |
Release history (including preview/experimental)
| Microsoft.Windows.AI.MachineLearning version | Release date | ONNX Runtime commit hash | ONNX Runtime date |
|---|---|---|---|
2.3.10-preview |
6/25/2026 | 8f0278c (1.27.0) |
6/12/2026 |
2.1.75-experimental |
6/8/2026 | 94bc0cd (1.25.2) |
5/10/2026 |
2.1.70 |
6/8/2026 | 800ac32 (1.24.6) |
4/28/2026 |
2.1.6 |
5/28/2026 | 800ac32 (1.24.6) |
4/28/2026 |
2.1.3-experimental |
5/18/2026 | 94bc0cd (1.25.2) |
5/10/2026 |
2.1.1 |
5/18/2026 | 800ac32 (1.24.6) |
4/28/2026 |
2.0.325-experimental |
4/21/2026 | ef605cd (1.24.5) |
4/16/2026 |
2.0.300 |
4/28/2026 | ef605cd (1.24.5) |
4/16/2026 |
2.0.297-preview |
3/26/2026 | 2d92497 (1.24.4) |
3/16/2026 |
Automatic updates for framework-dependent apps
If your app uses the framework-dependent version of Windows App SDK, your app will automatically receive updates across the revision version number without re-compiling and updating your app, but not across minor or major versions.
The following table shows how automatic updates work across different Windows App SDK version number changes:
| Version Component | Example Change | Automatic Update? | Description |
|---|---|---|---|
| Revision (x.y.Z) | 1.8.0 → 1.8.1 | ✅ Yes | Bug fixes and patches - automatically applied |
| Revision (x.y.Z) | 1.8.1 → 1.8.2 | ✅ Yes | Bug fixes and patches - automatically applied |
| Minor (x.Y.z) | 1.8.2 → 1.9.0 | ❌ No | Significant update - requires manual update |
| Major (X.y.z) | 1.9.0 → 2.0.0 | ❌ No | Breaking changes - requires manual update |
Version breakdown examples
| App Targets | Latest Available | App Actually Uses | Update Type |
|---|---|---|---|
| 1.8.0 | 1.8.3 | 1.8.3 | ✅ Automatic (revision) |
| 1.8.0 | 1.9.0 | 1.8.3* | ❌ Manual required (minor) |
| 1.8.0 | 2.0.0 | 1.8.3* | ❌ Manual required (major) |
*Latest revision within the same minor version
This means that if you target 1.8.0 of Windows App SDK and 1.8.1 is released, your app will automatically use 1.8.1 (and the corresponding Windows ML ONNX Runtime version). However, when 1.9.0 is released, your app will continue using 1.8.1 until you manually update your app to target 1.9.0.