---
title: Release notes for past releases of the Windows Machine Config Operator
---

# Release notes for past releases of the Windows Machine Config Operator {#windows-containers-release-notes-past}

You can review the release notes to learn about changes in previous versions of the Windows Machine Config Operator (WMCO).

For the current Red Hat OpenShift support for Windows Containers release notes, see "Red Hat OpenShift support for Windows Containers release notes".

## Release notes for Red Hat Windows Machine Config Operator 10.22.0 {#windows-containers-release-notes-10-22-0_windows-containers-release-notes-past}

Issued: 20 May 2026

You can review the following release notes to learn about the new features and bug fixes in the Windows Machine Config Operator (WMCO) version 10.22.0.

The components of the WMCO version 10.22.0 were released in [RHBA-2026:19710](https://access.redhat.com/errata/RHBA-2026:19710).

### New features and improvements {#wmco-10-22-0-new-features_windows-containers-release-notes-past}

Windows Server 2025 support
:   The WMCO now supports Windows Server 2025, OS Build [10.0.26100](https://support.microsoft.com/en-us/topic/may-12-2026-kb5087539-os-build-26100-32860-fe3fd635-23fc-41bd-b7a7-00e57c1c4f91) or later for all supported platforms.

Kubernetes upgrade
:   The WMCO now uses Kubernetes version 1.35.

### Bug fixes {#wmco-10-22-0-bug-fixes_windows-containers-release-notes-past}

- Before this update, if you enabled the `ClusterAPIMachineManagement` feature gate by enabling the `TechPreviewNoUpgrade` feature set, OpenShift Container Platform provisioned the `openshift-cluster-api` namespace. However, the WMCO was not adding the `windows-user-data` secret to that namespace, which is required by Cluster API compute machine sets. Because of the missing secret, CAPI-provisioned Windows machines would not bootstrap, remaining stuck in the `Pending` phase, and never joining the cluster. With this release, the OpenShift Container Platform now detects whether the `openshift-cluster-api` namespace exists and mirrors the `windows-user-data` secret into that namespace. CAPI-provisioned Windows machines successfully receive the bootstrap secret, are no longer getting stuck in `Pending` state, and join the cluster as expected. ([OCPBUGS-38401](https://issues.redhat.com/browse/OCPBUGS-38401))