Delay or Disable Windows 10/11 Feature Updates with TargetReleaseVersion (Safe Guide)
Difficulty: Intermediate |
Time Required: 15 minutes
Windows feature updates (like Windows 11 23H2 → 24H2, or Windows 10 21H2 → 22H2) can introduce new features—but they can also bring driver issues, app incompatibilities, performance changes, or unwanted UI changes. If you want stability, you may prefer to
stay on a known-good version until you’re ready.
Microsoft provides a supported method to “pin” your PC to a specific Windows release using a policy called
TargetReleaseVersion. When configured correctly, Windows Update will continue to deliver
security and quality updates for your current release, but it will
avoid upgrading to a newer feature update.
This guide shows how to safely set it up in Windows 10/11.
Prerequisites
Before you start, check the following:
- Administrator access on the PC.
- Your current Windows version (so you know what you’re pinning to):
- Press Win + R, type
winver, press Enter.
- Note the Version (e.g., 22H2, 23H2, 24H2) and the OS (Windows 10 vs Windows 11).
- Understand the goal:
- This method is best for delaying feature updates or staying on a specific release.
- It does not pause monthly security updates.
Note: TargetReleaseVersion is supported on Windows 10 and Windows 11. The easiest method depends on your edition:
- Windows Pro/Enterprise/Education: You can use Group Policy (recommended).
- Windows Home: Use the Registry method (works well, but be careful).
Step-by-step: Set TargetReleaseVersion (Recommended: Group Policy)
A) Windows 10/11 Pro, Enterprise, Education (Group Policy)
- Press Win + R, type
gpedit.msc, press Enter.
- Navigate to:
Computer Configuration → Administrative Templates → Windows Components → Windows Update → Windows Update for Business
- Find and open the policy:
Select the target Feature Update version
- Set it to Enabled.
- Configure the options:
- Target Version for Feature Updates: set to
Windows 10 or Windows 11 (match your OS)
- Target Feature Update version: set to the release you want to stay on, for example:
- Windows 10:
22H2
- Windows 11:
23H2 or 24H2 (choose your preferred one)
- Click Apply, then OK.
- Force a policy refresh (optional but recommended):
- Open Command Prompt (Admin) and run:
gpupdate /force
- Restart the PC.
That’s it. Windows Update should now avoid moving you to a newer feature update than the one you specified.
Warning: Don’t enter a version that doesn’t exist for your OS. For example, 22H2 is valid for Windows 10, but Windows 11 version naming may differ depending on what’s currently available for your device.
Step-by-step: Set TargetReleaseVersion (Windows Home / Registry Method)
If you don’t have Group Policy Editor, you can configure the exact same setting via the Registry.
B) Windows 10/11 Home (Registry)
- Press Win + R, type
regedit, press Enter.
- Approve the UAC prompt.
- Navigate to this key (create it if missing):
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
- If WindowsUpdate doesn’t exist:
- Right-click Windows → New → Key → name it
WindowsUpdate.
- In the right pane, create or set these values:
1) TargetReleaseVersion (DWORD 32-bit)
- Name:
TargetReleaseVersion
- Value:
1
2) TargetReleaseVersionInfo (String / REG_SZ)
- Name:
TargetReleaseVersionInfo
- Value: your target release, e.g.
22H2 / 23H2 / 24H2
3) ProductVersion (String / REG_SZ) (important on many systems)
- Name:
ProductVersion
- Value:
Windows 10 or Windows 11
- Close Registry Editor.
- Restart your PC.
After reboot, Windows Update should respect the target you set.
Tip: If you previously used other “update deferral” tools or policies, they can conflict. If behavior seems inconsistent, review other Windows Update policies or management tools (see troubleshooting below).
Verify it’s working
- Open Settings → Windows Update.
- Click Check for updates.
- You should still receive cumulative updates (Patch Tuesday/security fixes).
- You should not be offered a newer feature update beyond your target release.
To confirm the configured policy on Pro editions, you can also re-open Group Policy and verify it’s still enabled. On Home, re-check the Registry values.
How to undo (re-enable feature upgrades later)
When you’re ready to upgrade to the next feature update, you have two safe options:
Option 1: Remove the TargetReleaseVersion policy
- Group Policy method: set Select the target Feature Update version to Not Configured.
- Registry method: delete these values (or set
TargetReleaseVersion to 0):
TargetReleaseVersionTargetReleaseVersionInfoProductVersion
Restart, then run
Windows Update → Check for updates.
Option 2: Change the target to a newer version
If you want to move forward, set the target to the newer release (for example, from
23H2 to
24H2), then check for updates.
Note: If Microsoft has started phasing out support for your pinned release, Windows may eventually insist on a feature update to keep the device supported. TargetReleaseVersion reduces surprise upgrades, but it can’t override all servicing requirements forever.
Tips, warnings, and troubleshooting
Tips
- Pick a supported release: Staying on a version that’s still in support ensures you keep receiving security updates.
- Use this for stability: It’s ideal if you rely on specialized software, legacy hardware drivers, or a stable production environment.
- Combine with good update hygiene: Even if you delay feature updates, keep monthly security updates enabled.
Warnings
- Don’t “set and forget” for years: Feature update pinning is meant to control timing, not to avoid upgrading indefinitely. Eventually, older releases reach end-of-service.
- Avoid random “tweak tools”: Third-party update blockers can interfere with Windows Update in ways that make troubleshooting harder.
Troubleshooting
1) I’m still being offered a feature update
- Double-check:
TargetReleaseVersion is set to 1ProductVersion matches your OS (Windows 10 vs Windows 11)TargetReleaseVersionInfo is a valid release string
- Restart and check again.
2) Windows Update seems “stuck” or not offering anything
- Run Windows Update troubleshooter:
- Settings → System → Troubleshoot → Other troubleshooters → Windows Update
- Ensure required services aren’t disabled (Windows Update, BITS).
- If the PC is managed by work/school or MDM, those policies may override local settings.
3) I used multiple policies (pause, deferrals, metered connection)
- Temporarily remove extra controls and test with just TargetReleaseVersion.
- On Pro editions, verify policies under Windows Update for Business and related Windows Update templates.
Conclusion
Using
TargetReleaseVersion is one of the safest, Microsoft-supported ways to
delay or effectively “disable” automatic feature upgrades without shutting off important security updates. With a quick policy or Registry change, you can keep your system on a stable Windows release and upgrade on your schedule—especially helpful for work PCs, gaming rigs, and systems with sensitive drivers or apps.
Key Takeaways:
- TargetReleaseVersion lets you pin Windows 10/11 to a specific feature update (like 22H2/23H2/24H2).
- You continue receiving monthly security and quality updates while avoiding unexpected major upgrades.
- You can configure it via Group Policy (Pro+) or Registry (Home) and easily undo it later.
This tutorial was generated to help WindowsForum.com users get the most out of their Windows experience.