Windows Server 2025: Lifecycle, Support, and Key Changes

If you manage Microsoft infrastructure, you'll want to know that Windows Server 2025 has a clearly defined support lifecycle , and this cycle affects not only the operating system itself but also legacy services like WINS and compatibility with Microsoft 365 Apps. Over the next few years, several key dates will overlap, so it's important to keep them in mind to avoid suddenly finding yourself with servers lacking security patches and support. And if you need to install it, see how to download and install Windows Server.

In the following lines, we'll calmly review when support for Windows Server 2025 begins and ends, what exactly happens in 2034 , how all of this relates to other versions of Windows Server, Windows 10, Windows 11, and Microsoft 365, and what significant changes are coming to services like WINS. The goal is for you to finish this article with a very clear understanding of which systems will remain supported, which will enter extended support, and which will be completely discontinued.

Windows Server 2025 Lifecycle: Standard and Extended Support

Windows Server 2025 is released under Microsoft's Fixed Lifecycle Policy , which means that the product has a clearly defined standard support period and extended support period, without the continuous evolution model typical of the modern policy.

According to the official lifecycle schedule, general availability of Windows Server 2025 LTSC begins on November 1, 2024. From that point, the platform enters its standard support phase, during which it receives new features, bug fixes, and, of course, regular security updates (configurable with WSUS configuration ).

Standard support for Windows Server 2025 is scheduled to end on November 13, 2029. After that date, the product will no longer receive functional updates and will enter extended support, during which Microsoft will only provide security updates and certain critical fixes under specific conditions.

The key date everyone is watching is the end of extended support: November 14, 2034. That day marks the complete end of the Windows Server 2025 lifecycle under the fixed policy: there will be no more security patches or official technical support, unless Microsoft releases specific additional programs in the future, something that has not yet been announced.

The editions covered by this fixed lifecycle of Windows Server 2025 include Datacenter, Datacenter: Azure Edition, Standard, and Essentials , which share the same start, end of standard support, and end of extended support dates.

LTSC, annual channel and position of Windows Server 2025 within the family

In Microsoft's current catalog, Windows Server is distributed through two main release channels : the Long-Term Servicing Channel (LTSC) and the Annual Channel (sometimes called AC or Annual Channel). Each is designed for different scenarios and has different support durations.

The LTSC offers long cycles, focused on stability and security , with a traditional support policy based on monthly cumulative updates and, in the case of Windows Server 2025, extended support until 2034. It is the typical option for critical workloads that cannot be receiving disruptive changes every few months.

The annual channel, on the other hand, is geared towards more dynamic scenarios, closely tied to containers and microservices , where organizations are willing to adopt a faster pace of innovation and, in return, accept shorter lifecycles. Currently, Windows Server version 23H2 is the latest release in this channel and will reach its end of support in October 2025.

Within this overall framework, Windows Server 2025 is considered the current reference LTSC version . It shares a focus on innovation with other components of Microsoft's hybrid platform, such as Azure Stack HCI, Windows containers, and AKS on Azure Stack HCI, reinforcing its role as the foundation for modern on-premises and hybrid infrastructures.

For those who need to consult these dates through automation, Microsoft exposes this information through the Windows Updates API in Microsoft Graph , allowing it to be integrated into proprietary inventory and lifecycle management tools.

Lifecycle dates compared: Windows Server 2025, 2022, 2019 and 2016

If we compare the different versions of Windows Server from the perspective of their maintenance options, it becomes clear at a glance how Windows Server 2025 fits into Microsoft's long-term roadmap for servers.

The Windows Server major release table indicates that Windows Server 2025 LTSC (Datacenter and Standard editions) has been available since 2024-11-01 , with mainstream support ending on 2029-11-13 and extended support ending on 2034-11-14. Alongside these dates, additional information is listed, such as the last installed update, the date of the last revision, and the most recent build (for example, 26100.7178 as of 2025-11-18).

Windows Server 2022, also in the LTSC channel with Datacenter and Standard editions, has an availability date of 2021-08-18 , with the end of standard support on 2026-10-13 and the end of extended support on 2031-10-14. In this way, 2025 and 2022 overlap for several years, which allows room for gradual migrations.

In the case of Windows Server 2019 (version 1809), the table shows that mainstream support has ended , with only extended support remaining until January 9, 2029, under LTSC. Monthly updates continue, but the product is clearly nearing its final removal from the supported catalog.

Windows Server 2016 (version 1607), labeled as a Long-Term Servicing Branch (LTSB) and with Datacenter, Essentials, and Standard editions, appears in the table with an availability date of 2016-08-02 and an end of extended support on 2027-01-12. At this point, it is a platform that relies on its last years of security patches.

For each of these versions, the official documentation also maintains an extremely detailed history of all monthly updates (security and non-security) released, with information on the resulting build and the associated KB.

Windows Server 2025 and earlier update history

In the specific case of Windows Server 2025, the Microsoft support page includes a very granular version history for operating system build 26100. This table identifies, for each update: the release type (LTSC), the update type (for example, "2025-11 B" or "OOB" for out-of-band), the availability date, the generated build, and the KB article number.

This historical update began with build 26100.1742 in the update labeled "2024-10 A" (released on 2024-11-01) and progresses month by month with B packages (second Tuesday) and out-of-box (OOB) updates when vulnerabilities or critical issues need to be urgently addressed . For example, the November 2025 B update (2025-11 B) updates to build 26100.7171 and is identified as KB5068861.

Similarly, there are expandable sections with comprehensive details of the Windows Server 2022 (OS build 20348), Windows Server 2019 (OS build 17763), and Windows Server 2016 (OS build 14393) builds , listing years of cumulative patches, C and D releases, and out-of-band updates.

This information is essential for security and compliance audits, as it allows you to accurately verify which exact build a server is running at any given time and which vulnerabilities are resolved or pending; to audit installed features it is also common to use the Get-WindowsFeature command.

Hot patch schedule: baseline and hot patches

Beyond the classic monthly updates, Microsoft has introduced a hotpatching schedule for Windows Server , especially geared towards Datacenter: Azure Edition and scenarios managed with Azure Automanage.

In this model, each calendar year is structured into quarters. In the first month of each quarter, devices receive a baseline cumulative update that requires a restart . During the following two months, hot patches are released that include only security updates and, in many cases, can be applied without restarting the machine, reducing the impact on service availability. More details about hotpatching in Windows Server are available.

For example, in the calendar year 2025 for Windows Server 2025 , January, April, July, and October are recorded as baseline months (with B releases implying a reset), and February, March, May, June, August, September, November, and December are reserved for hotfixes with a focus on security. Each entry details the resulting build (such as 26100.2894 in January or 26100.6899 in October) and its corresponding KB article.

Windows Server 2022 follows a very similar scheme, with its own calendar year 2025 table where the pattern of alternating between baseline and hotpatching is repeated , making it clear which months will require a mandatory restart and which will not.

The operational advantage is clear: by minimizing the number of restarts, organizations can keep their workloads in production longer without such frequent maintenance windows, while maintaining security compliance; it is also advisable to monitor performance to check the impact of updates.

End of WINS support on all versions of Windows Server

Beyond the system's lifecycle dates, Microsoft has announced a significant change regarding legacy services. Specifically, WINS (Windows Internet Name Service) will no longer be supported in all versions of Windows Server starting in November 2034 , which will have a major impact on organizations that still rely on this name resolution service.

WINS was the classic NetBIOS name registration and resolution mechanism for Windows networks , very common in older environments. This service was functionally discontinued with the release of Windows Server 2022 (in August 2021), when Microsoft made it clear that it would no longer add improvements or new features.

The company specifies that Windows Server 2025 will be the last LTSC version to maintain support for WINS . In a November 2025 statement, Microsoft officially declared this service obsolete and set the roadmap: WINS will remain present throughout the Windows Server 2025 lifecycle, but the actual end date will be 2034.

When the change is fully implemented, Windows Server will no longer include the WINS server role , along with its associated automation APIs, management console snap-in, and any other related interfaces. In practice, it will be as if the service never existed in newer versions.

Microsoft strongly recommends that companies still relying on WINS begin identifying NetBIOS-based services and applications as soon as possible and migrate them to DNS. The documentation emphasizes that temporary solutions like the widespread use of static hosts files are neither sustainable nor secure in medium-sized or large corporate environments; therefore, proper DHCP and DNS configuration is crucial.

List of products with end of support in 2034 and their relationship to other Windows systems

Within its product lifecycle pages, Microsoft compiles lists of products that will be retired or reach their end of support in various years . For 2034, the fixed policy lists those products that have already formally announced their end of support that year, including Windows Server 2025 and other related LTSC editions.

The company notes that once support ends, no further security or other updates will be released , and no assisted technical support options (free or paid) or online technical content updates will be available. All reference information will then become static.

In parallel, the logic behind the modern lifecycle policy for products like Microsoft 365 is explained , where continued support requires keeping system and maintenance requirements up to date. For example, Microsoft 365 Apps are required to run only on supported Windows systems.

In the desktop environment, the Windows 10 and Windows 11 tables summarize which versions are currently supported. For Windows 11, versions 25H2, 24H2, 23H2, 22H2, and 21H2 are specified, indicating their servicing option (General Availability Channel), availability dates, operating system builds, and differentiated end-of-service dates for Home/Pro and Enterprise/Education/IoT editions.

For example, Windows 11 24H2 appears as a General Availability channel with build 26100, availability date 2024-10-01 and end of maintenance for Home/Pro on 2026-10-13, while the Enterprise, Education and IoT Enterprise editions maintain support until 2027-10-12.

In the case of Windows 10, the key version is 22H2 in the General Availability Channel, with build 19045 , whose end-of-service date for all major editions (Home, Pro, Enterprise, Education, and IoT Enterprise) is aligned to 2025-10-14. In addition, the Enterprise and IoT Enterprise LTSC/LTSB editions from 2021, 2019, 2016, and 2015 are listed, with their respective end-of-standard and extended support dates.

Products with end of support in 2025 and changes to Azure

Along with the 2034 information, the documentation also includes sections on products being retired or reaching end of support in 2025 , following both the modern and fixed policies. This includes components of Dynamics 365, Configuration Manager, and various versions of Windows 11.

In the modern policy section, for example, Dynamics 365 Business Central on-premises (release 2 of 2023, version 23.x) is listed with end of support on April 2, 2025 , as well as Dynamics 365 Business Central on-premises release 1 of 2024 (version 24.x) with end of support on October 7, 2025.

It is also noted that Microsoft Configuration Manager version 2309 reaches its end of support on April 9, 2025 , and version 2403 on October 22, 2025, marking significant milestones for administrators of client management environments.

In the area of ​​the desktop operating system, the end of support for Windows 11 Enterprise and Education, version 22H2 (along with Windows 11 IoT Enterprise 22H2) is mentioned as October 14, 2025 , as well as the end of maintenance for Windows 11 Home and Pro, version 23H2, on November 11, 2025.

Additionally, further changes to Azure related to APIs, SDKs, tools and features are also listed , referring to the "Azure Updates" page as a centralized reference to follow the evolution of the cloud services ecosystem.

General recommendations from Microsoft regarding support and migrations

Throughout these pages, Microsoft emphasizes that, if organizations have any questions about product support, they should contact their account representative or use the Microsoft Technical Support portal for specific answers about their case; in emergency situations, it's helpful to know how to recover Windows Server.

For those unsure of the status of their systems, the company maintains a centralized page where it's possible to search the lifecycle of each individual product. This serves as a starting point for determining whether a system is in standard support, extended support, or completely out of support.

When a product transitions from standard support to extended support (as is the case with many versions of Windows Server and desktop Windows), it's important to remember that extended support includes free security updates, some non-security updates, and paid support , but Microsoft stops accepting requests for design changes or new features; in this context, it's advisable to perform a full backup on Windows Server before any major intervention.

In the realm of Windows Server, if an organization continues to use versions that no longer meet the compatibility requirements for Microsoft 365 Apps, the recommendation is to migrate to solutions such as Windows 365 or Azure Virtual Desktop . This ensures that the end-user's work environment remains supported without forcing them to maintain older server versions.

Finally, regarding legacy services like WINS, Microsoft's position is very clear: organizations must stop relying on NetBIOS-based technologies and move towards DNS . Avoiding shortcuts such as the heavy use of hosts files and designing realistic migration plans is key to reaching 2034 prepared and without last-minute surprises.

With this landscape of dates, lifecycle policies, and compatibility changes, Windows Server 2025 stands as the benchmark for on-premises infrastructures in the medium and long term , with a support window extending until 2034, which, if properly utilized, should be sufficient to calmly plan the transition to the next generations of the platform.

Related articles:

Hotpatching in Windows Server: How-To Guide, Cycle, Costs, and Orchestration

Isaac

Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.