Microsoft’s Windows Lifecycle Policy defines how long each version of Windows receives updates and support. Understanding this policy is essential for IT administrators and certification candidates, as it determines how long devices stay compliant, secure, and eligible for Microsoft servicing.
Let’s break down the scenario carefully using the official lifecycle details from Microsoft’s documentation and the provided reference links.
Understanding Windows Lifecycle Support
Microsoft releases Feature Updates twice a year — typically in March (H1) and September (H2). Each feature update defines a new version of Windows, such as 21H1, 21H2, 22H2, and so on. These updates are supported for a fixed duration, depending on their release month and edition.
1. Support Duration by Release Type
According to Microsoft’s Windows Lifecycle Fact Sheet:
- March (H1) Feature Updates: Serviced for 18 months from the release date.
- September (H2) Feature Updates: Serviced for 30 months from the release date.
This applies to Enterprise and Education editions. Home and Pro editions typically receive only 18 months of support regardless of release date.
2. Scenario Overview
The question asks:
“As of March, how long will the computers in each office remain supported by Microsoft?”
Two locations are listed:
- Seattle
- New York
Each location’s computers are running different Windows 10 builds — one released in March (H1) and one in September (H2). The goal is to calculate how long each will remain supported as of March.
3. Seattle Office – March Feature Update
The Seattle office runs a Windows version that was released in March.
According to Microsoft’s servicing policy:
- March (H1) updates are serviced for 18 months from their release date.
Example:
If the Seattle devices are running Windows 10 version 21H1 (March 2021 release):
- Release Date: March 2021
- End of Support: September 2022
- As of March 2022, that would leave 6 months of remaining support.
If the current context is March 2024, a more recent March feature update (such as 22H1 or 23H1) would still follow the same 18-month servicing rule, meaning its end of support would occur around September of the following year.
✅ Seattle Support Duration: 18 months from release (approximately 6 months remaining if nearing end of cycle)
4. New York Office – September Feature Update
The New York office runs a version released in September.
As per Microsoft’s policy:
- September (H2) updates are serviced for 30 months from their release date.
Example:
If the New York devices are running Windows 10 version 21H2 (September 2021 release):
- Release Date: September 2021
- End of Support: March 2024 (for Enterprise/Education)
- As of March 2023, approximately 12 months of support remain.
- As of March 2024, it’s reaching end of support.
If the devices are on a more recent September release, like 22H2 (September 2022), support would extend until March 2025, leaving roughly 12 months remaining as of March 2024.
✅ New York Support Duration: 30 months from release (typically 18–24 months remaining depending on version age)
5. Comparing Support Lifecycles
| Office | Update Type | Release Timing | Servicing Duration | Typical Use Case | Support Remaining (as of March) |
|---|---|---|---|---|---|
| Seattle | March Feature Update (H1) | Spring release | 18 months | Shorter-term builds or pilot deployments | ~6–12 months remaining |
| New York | September Feature Update (H2) | Fall release | 30 months | Long-term enterprise use | ~18–24 months remaining |
6. Explanation of Feature vs. Quality Updates
As referenced in the Windows Central article:
- Feature Updates: Introduce new features and functionality. Released twice a year (March and September).
- They reset the servicing timeline (18 or 30 months).
- Quality Updates: Monthly updates containing security fixes, reliability improvements, and performance patches.
- Do not reset the lifecycle; they simply maintain system stability during the servicing period.
This distinction is critical when planning lifecycle management. Feature updates must be planned strategically to ensure devices don’t fall out of support.
7. Best Practices for IT Administrators
To maintain compliance and minimize risk:
- Stagger Feature Updates — Deploy March releases for test groups and September releases for production to take advantage of the longer support window.
- Monitor Lifecycle Dates — Track each version’s end-of-support date via the Windows Release Health dashboard.
- Automate Updates via Intune or Configuration Manager — Use Windows Update for Business (WUfB) policies to schedule deferrals and gradual rollouts.
- Communicate with End Users — Notify users before major updates to minimize disruptions.
- Regularly Review Build Versions — Replace outdated versions before their support expiration to ensure ongoing security updates.
8. Final Answers
Based on Microsoft’s lifecycle fact sheet:
- Seattle (March Feature Update): Supported for 18 months from release.
- New York (September Feature Update): Supported for 30 months from release.
If we interpret “as of March” literally:
- Seattle computers would have around 6–12 months of support left.
- New York computers would have 18–24 months of support left, depending on the version release date.
✅ Final Answer Summary
| Location | Feature Update | Servicing Duration | Support Remaining (approx.) |
|---|---|---|---|
| Seattle | March Release (H1) | 18 months | 6–12 months |
| New York | September Release (H2) | 30 months | 18–24 months |
References:
