A feature update is a new version of Windows that adds or changes functionality and moves a device to a newer release, identified by a version label such as 24H2 or 25H2. In keeping Windows current, it differs fundamentally from the monthly quality updates: it changes the operating system build and resets the support lifecycle of the device, while monthly updates only fix and secure the version already installed.
Windows 11 receives one feature update per year, released in the second half of the calendar year, hence the H2 suffix. Each version is supported for a fixed period, so installing feature updates on schedule is what keeps a device eligible for security fixes over the long term.
How a feature update is delivered and installed
A feature update can be installed in two technically different ways. A full in-place upgrade replaces the operating system image with a new one while migrating apps, settings and user data, and it keeps the previous installation in a Windows.old folder for rollback. This process typically takes 30 to 90 minutes and several restarts, depending on hardware and the amount of data.
When two versions share the same servicing branch, Microsoft instead ships an enablement package. The new features are already present in the installed build but dormant, and the small package switches them on with a single restart, which reduces downtime to minutes.
Before installation, Windows Update checks compatibility and safeguard holds. A safeguard hold blocks the offer to devices with a known incompatible driver, application or hardware configuration until the issue is resolved.
Servicing timelines and version labels
Every feature update starts a fixed support window that depends on the edition. Once the window ends, the version stops receiving cumulative updates, and the device must move to a newer version to stay protected. The table below summarizes the general servicing model for Windows 11.
| Edition | Support per version | Practical consequence |
|---|---|---|
| Home and Pro | 24 months | Upgrade at least every second year |
| Enterprise and Education | 36 months | Organizations can skip one annual version |
| LTSC editions | Five years or more | No annual feature updates at all |
| Windows Server LTSC | Long-term fixed lifecycle | Upgrades are planned migrations |
The version label follows a year and half-year pattern: 23H2 was released in the second half of 2023, 24H2 in the second half of 2024. Each version also has an OS build number, such as 26100 for 24H2, which administrators use in inventory and compliance reports.
Feature updates compared with other update types
Windows uses several update types with different scope, cadence and risk. Understanding the differences helps administrators plan testing and maintenance windows.
| Update type | Cadence | What it changes |
|---|---|---|
| Feature update | Once a year | Windows version, features and support lifecycle |
| Cumulative update | Monthly on Patch Tuesday | Security and quality fixes for the current version |
| Optional preview update | Monthly, later in the month | Non-security fixes ahead of the next release |
| Out-of-band update | When urgently needed | Fix for a critical flaw or broken update |
| Hotpatch | Most months on eligible devices | Security fixes applied without a restart |
| Driver and firmware update | Varies by vendor | Hardware support and stability |
The major difference in risk is clear from this comparison. A cumulative update modifies selected files, while a feature update rebuilds the operating system, so it is more likely to expose incompatible drivers, security software or line-of-business applications.
Managing feature updates in organizations
Organizations control feature updates through Windows Update for Business policies, Microsoft Intune, WSUS or Configuration Manager. The usual approach is a ring-based rollout: a small pilot group receives the new version first, followed by broader groups after a validation period.
| Ring | Share of devices | Purpose |
|---|---|---|
| Pilot | About 1 to 5 percent | IT staff test core apps and drivers |
| Early adopters | About 10 to 15 percent | Representative users from each department |
| Broad | Most remaining devices | General deployment after issues are fixed |
| Critical | Small set of sensitive systems | Updated last after full validation |
Windows Update for Business allows feature updates to be deferred for up to 365 days or pinned to a specific target version, which prevents devices from jumping ahead before testing is complete. Deferral should not become indefinite postponement, because an out-of-support version stops receiving security fixes.
Rollback, failures and common mistakes
After a full in-place upgrade, Windows offers a rollback period of 10 days by default, during which the previous version can be restored from Settings. Administrators can extend this window with DISM up to 60 days, but Disk Cleanup or Storage Sense may remove Windows.old earlier and make rollback impossible.
Failed installations end with an automatic rollback and an error code that points to the cause. The table below lists frequent causes and remedies.
| Cause | Typical symptom | Remedy |
|---|---|---|
| Insufficient free space | Download or setup stops early | Free at least 20 to 30 GB on the system drive |
| Incompatible driver | Rollback after a restart | Update or remove the driver, then retry |
| Third-party security software | Setup hangs or fails | Update the product to a supported version |
| Corrupted component store | Repeated install errors | Repair with DISM and System File Checker |
| Safeguard hold | Update is not offered | Wait for the fix rather than forcing it |
- Forcing an update past a safeguard hold with installation media can reproduce the very problem the hold prevents.
- Skipping backups before an upgrade leaves no recovery path if migration damages user data.
- Testing only the operating system misses failures in VPN clients, printers and specialized applications.
In plain words
A feature update is the yearly new edition of Windows. Monthly updates are like small repairs to a house, while a feature update is a renovation that adds new rooms and modernizes the old ones.
Each Windows version is looked after for a limited time, about two years for home computers. After that, the repairs stop. The main point is that installing the yearly update keeps the computer safe, so it should be accepted rather than postponed forever.
A real-world example
A school district manages 2,400 Windows 11 Education laptops with Intune. When version 25H2 becomes available, the IT team assigns it to a pilot ring of 60 devices used by technicians and two teachers in each school, while the rest stay pinned to 24H2.
Within the first week, the pilot reveals that an older driver for classroom document cameras fails after the upgrade. The team obtains an updated driver from the hardware vendor, deploys it to all devices and then releases the feature update to the early adopter ring.
Because Education editions receive 36 months of support, the district times the broad rollout for the summer break. The upgrade arrives as an enablement package with a single restart, and all devices reach the new version before the school year starts without classroom disruption.