Skip to main content

Configuration policies: pin a Windows 11 feature version

Pin Windows 11 devices to a feature version you have approved with the Target feature version setting in a configuration policy. Without a pin, the Windows 11 upgrade in an IT automation profile always installs the newest Windows 11 release. With a pin, Windows Update doesn't move the device past the selected version, and the Windows 11 upgrade installs the pinned version instead of the newest one. The pin uses the Windows Update for Business target version (TargetReleaseVersion) values, so a pin you already set with Group Policy works the same way.

This article explains how a target feature version works, how to set, change, and remove one, what it doesn't do, and how to check a device when a pinned upgrade doesn't go as expected. For configuration policies in general, see Configuration policies: overview.

Before you begin

Check these requirements before you pin a Windows 11 feature version with a configuration policy.

Important note: Check your access and the device before you set a pin:

  • Editing configuration policies requires Full admin access. There is no separate permission for the Windows feature updates section.
  • The device runs Windows 11 Pro, Enterprise, or Education. Windows 11 Home ignores the pin.
  • The device isn't managed by WSUS. WSUS-managed devices ignore the pin.

The upgrade runs from an IT automation profile with Upgrade to latest Windows 11 build selected, and the device must be eligible for Windows 11. For the eligibility check and the upgrade setting, see Windows version updates and upgrades.

How a target feature version works

What a pinned feature version does and doesn't stop

A pinned Windows 11 feature version is a version ceiling, not an update block. Windows Update doesn't offer the device a feature version newer than the pin, but security and quality updates keep installing as usual. A pin controls which version a device can reach, not when updates install: timing still follows your IT automation profile's schedule and the Windows update settings in your configuration policy.

A pin doesn't last forever. When a pinned version reaches its end of servicing, Microsoft moves the device to a newer version regardless of the pin, so plan the move to a newer pin before that date.

What the policy writes to the device, and Group Policy pins

When a configuration policy has a target feature version, it writes three Windows Update for Business values to the device under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate. For example, for 25H2:

Value Written as
TargetReleaseVersion 1 (DWORD)
ProductVersion Windows 11
TargetReleaseVersionInfo 25H2

 

Nothing is written under an Atera registry key. A domain Group Policy Object (GPO) that pins a version writes the same three values, so the Atera agent treats a GPO pin exactly like a pin set in a configuration policy, and the Windows 11 upgrade installs the version the GPO pins.

Windows 11 versions you can pick

The Target feature version dropdown offers Latest and the three Windows 11 versions before it:

  • Latest: no pin. Devices can move to the newest Windows 11 release. This is the default.
  • One of the three previous versions: pin devices to that version.

Atera adds new Windows 11 versions to this list. When Microsoft deprecates a Windows 11 version, it's no longer offered in the dropdown for new accounts or new configuration policies. A policy that's already pinned to that version keeps it selected, with "(deprecated)" next to the version name, and you can still save other changes to that policy. After you select a different version and save, the deprecated version no longer appears in that policy's dropdown.

Windows 10 devices and a pinned Windows 11 version

A target feature version applies to the Windows 11 upgrade only. If an IT automation profile has Upgrade to latest Windows 10 build selected, a Windows 10 device still updates to the latest Windows 10 version, as before. On a device that already runs Windows 11, that Windows 10 option has no effect. A pin can't roll a device back to an older Windows version.

Pin devices to a Windows 11 feature version

To pin a Windows 11 feature version, turn on Target feature version in a configuration policy, pick the version, and make sure the policy is assigned to the devices. In a policy created before this setting existed, Target feature version is off and shows Latest, so nothing changes on devices until you turn it on.

To pin a Windows 11 feature version:

  1. Go to Admin > Monitoring and automation > Configuration policies.

    The Configuration policies page appears.

     

  2. Select a policy, or click New policy to create one.

     

  3. In the Windows feature updates section, toggle on Target feature version.

     

  4. From the dropdown, select the version to pin.

     

  5. Click Save (top right of the page). For a new policy, click Create.

     

  6. If the policy isn't assigned to the devices yet, assign it. See Assign a configuration policy.

    The policy writes the pin to the assigned devices when it's applied: as soon as it's saved, and then every 12 hours. Offline devices receive it the next time they check in.

 

Windows Update no longer moves pinned devices past the selected version. The upgrade itself happens the next time an IT automation profile with Upgrade to latest Windows 11 build runs on the device. It then installs the pinned version.

Note: A device follows one configuration policy only, and if it's in more than one dynamic group with different policies, the most recently edited policy applies.

Change or remove a pinned Windows 11 feature version

You change or remove a pinned Windows 11 feature version in the configuration policy that set it, under Admin > Monitoring and automation > Configuration policies. Changes reach devices the next time the policy is applied.

  • Pin a different version: in Target feature version, select the new version and click Save. The device's pin follows the last version you saved. Deprecated versions aren't offered.
  • Remove the pin: select Latest and click Save. The policy removes the three pin values from the device. The next time an IT automation profile with Upgrade to latest Windows 11 build runs, it installs the newest Windows 11 release.

Important note: Turning Target feature version off doesn't remove a pin, because the policy then writes nothing and leaves the device's current values in place, including a pin set by Group Policy.

Important note: Removing a device from a configuration policy, or deleting the policy, doesn't remove the pin either. The pinned version stays on the device and keeps being enforced until it's changed, for example by a GPO or a manual registry change. To remove a pin, select Latest in the policy and let it apply before you unassign the device or delete the policy.

What a pinned feature version doesn't do

These limits apply to every target feature version set in a configuration policy:

  • Windows 11 Home ignores the pin. Atera doesn't upgrade a pinned Home device, so it can't move past the pin. Move the device to a supported edition, or upgrade it manually.
  • WSUS-managed devices ignore the pin, and Atera doesn't upgrade them. Control their version in WSUS.
  • End of servicing: when a pinned version reaches end of servicing, Microsoft moves the device forward regardless of the pin.
  • Manual upgrades: a user with local administrator rights can still run the Windows 11 Installation Assistant or an ISO on the device. The pin doesn't block that. To prevent it, remove local administrator rights.
  • Rollback: a pin can't move a device back to an older Windows version.
  • Failure reasons: Atera doesn't show why a pinned upgrade failed. Check the device instead (see the troubleshooting section below).

Troubleshooting a pinned Windows 11 upgrade

Atera doesn't show why a pinned Windows 11 upgrade failed or why a device is on another version, so check the device itself. Find the cause that matches what you see below.

The device didn't upgrade to the pinned Windows 11 version

If a device with a pinned Windows 11 feature version didn't upgrade, or the upgrade failed, check these in order:

  • The IT automation profile with Upgrade to latest Windows 11 build ran on the device, and its schedule and rules matched the device.
  • The device is eligible for Windows 11. A device that fails the eligibility check (for example, no TPM) fails before any download starts.
  • The device isn't running Windows 11 Home. Home ignores the pin, and Atera doesn't upgrade it.
  • The device isn't managed by WSUS.
  • The pin values under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate (TargetReleaseVersion, ProductVersion, and TargetReleaseVersionInfo) match the version you pinned. Compare them with DisplayVersion under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion.
  • The device was restarted after the update installed. If it doesn't reach the pinned version within 72 hours, the upgrade times out.

The device is on a different Windows 11 version than the pin

If a device runs a different Windows 11 version than the one pinned in its configuration policy:

  • Read the version from DisplayVersion under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion, not from ProductName, which can show "Windows 10 Pro" on a Windows 11 device.
  • If the device is on a newer version than the pin, check whether a local administrator ran the Windows 11 Installation Assistant or an ISO, or whether the pinned version reached its end of servicing.
  • If the pin values are missing or show another version, check which configuration policy the device follows. A device follows one policy only, and in dynamic groups the most recently edited policy applies.
  • Check whether a domain Group Policy Object writes the same pin values.

The device is still pinned after turning off Target feature version, unassigning it, or deleting the policy

This is expected. Turning Target feature version off in a configuration policy writes nothing to the device and leaves the existing pin values in place. Removing the device from the policy, or deleting the policy, also leaves the pin on the device, and it keeps being enforced until it's changed, for example by a GPO or a manual registry change.

To remove the pin, open the configuration policy, turn Target feature version on, select Latest, click Save, and wait for the policy to be enforced (this can take up to 12 hours). Only then unassign the device or delete the policy.

A Windows 11 version shows as deprecated

When Microsoft deprecates a Windows 11 version, Atera stops offering it in the Target feature version dropdown for new accounts and new configuration policies. A policy that's already pinned to that version keeps it selected, with "(deprecated)" next to the version name. You can still save other changes to that policy. After you select a different version and save, the deprecated version no longer appears in that policy's dropdown.