Short answer: Microsoft lists Windows Server 2016 extended support ending at 6:59:59 a.m. Pacific on 13 January 2027. Paid Extended Security Updates then run in three yearly steps through 8 January 2030. List each server and app now, choose an upgrade or a replacement, and use the paid updates only as a bridge.
This is for small and mid-size firms in the United States, the UAE, Saudi Arabia, Singapore and Malaysia that still run ERP, file shares or other line-of-business apps on that operating system. It is a planning guide. It is not a licensing quote.
When does Windows Server 2016 support end?
Microsoft's lifecycle page for Windows Server 2016 lists the extended end date as 13 January 2027 at 6:59:59 a.m. Pacific time. The page says support dates are shown in the Pacific time zone, Redmond time. That moment is 9:59 a.m. Eastern on the same day, 6:59 p.m. in the UAE, 5:59 p.m. in Saudi Arabia, and 10:59 p.m. in Singapore and Malaysia.
The date covers Datacenter, Essentials, MultiPoint Premium and Standard. Containers released with Windows Server 2016 follow the same dates. From 17 November 2026 to 13 January 2027 is 57 days.
Extended Security Updates are the paid releases listed after that timestamp. Year 1 starts the same morning at 8:00:00 a.m. Pacific.
What are the Extended Security Update dates?
The lifecycle page lists three yearly steps. All of these times are 8:00:00 a.m. Pacific.
| Year | Starts | Ends |
|---|---|---|
| Year 1 | 13 January 2027 | 11 January 2028 |
| Year 2 | 12 January 2028 | 9 January 2029 |
| Year 3 | 10 January 2029 | 8 January 2030 |
The page does not list a price. Treat the paid years as a bridge for a system you cannot move in time, and put a finish date on that bridge. Buying all three years and stopping there leaves you on an old server until 2030.
Has SQL Server 2016 already left extended support?
Yes, if the app also uses SQL Server 2016. Microsoft lists that extended end as 15 July 2026 at 6:59:59 a.m. Pacific. Year 1 of the paid updates started the same morning at 8:00:00 a.m. and runs to 13 July 2027 at 8:00:00 a.m. Pacific.
| SQL Server 2016 | Start (Pacific) | End (Pacific) |
|---|---|---|
| Product start to extended end | 1 June 2016, 8:00:00 a.m. | 15 July 2026, 6:59:59 a.m. |
| Extended Security Updates Year 1 | 15 July 2026, 8:00:00 a.m. | 13 July 2027, 8:00:00 a.m. |
| Extended Security Updates Year 2 | 14 July 2027, 8:00:00 a.m. | 18 July 2028, 8:00:00 a.m. |
| Extended Security Updates Year 3 | 19 July 2028, 8:00:00 a.m. | 17 July 2029, 8:00:00 a.m. |
Plan the database and the operating system together. Moving the Windows server and leaving SQL Server 2016 behind does not finish the job.
How do you choose a path for each server?
For each machine, including test servers, write the name, the edition, where it lives, which apps run on it, who uses them, and what else connects to it. Then give each app one path:
- Upgrade in place, if the application vendor supports a newer Windows Server version on that machine.
- Move the application to a server running a newer Windows Server version.
- Rehost the server in the cloud and keep the application as it is, for now.
- Replace the application with a hosted product and retire the server.
A custom app, or an integration the vendor has not tested on a newer Windows Server, is the usual blocker. The roadmap for moving legacy systems to the cloud covers rehost, replatform, rebuild and replace, and a phased cutover.
What should you finish before 13 January?
- Finish the inventory this week, including test machines.
- Mark anything that cannot move by 13 January. That list is the case for Extended Security Updates.
- Run a real order, invoice or file share through a test copy of the riskiest app.
- Move file and print servers first, then book the ERP cutover for a week you can staff, with a rollback you have tried.
The last week of December is a weak slot if the person who knows the app is away. Test earlier, and move the risky system in a week that person is in.
Where does Ascent24 fit?
Ascent24 builds custom software and cloud migration services, including help moving workloads off older servers and reconnecting the applications that depend on them. If a custom app is what blocks the upgrade, that is integration and rebuild work. We will not quote an Extended Security Update price here, because Microsoft's lifecycle page does not publish one.
FAQs
Which Windows Server 2016 editions does this date cover?
Datacenter, Essentials, MultiPoint Premium and Standard. Containers released with Windows Server 2016 use the same dates.
Is the last moment 12 January or 13 January 2027?
Microsoft lists the extended end as 13 January 2027 at 6:59:59 a.m. Pacific. That is 9:59 a.m. Eastern the same day, 6:59 p.m. in the UAE, 5:59 p.m. in Saudi Arabia, and 10:59 p.m. in Singapore and Malaysia.
Do we have to buy Extended Security Updates?
No. They are the paid option after extended support ends. Move what you can. Use the paid updates for the systems that will miss 13 January, and set a date to leave them.
What if the application uses SQL Server 2016?
SQL Server 2016 left extended support on 15 July 2026 at 6:59:59 a.m. Pacific. It is in its first Extended Security Update year, which runs to 13 July 2027 at 8:00:00 a.m. Pacific.
Can we upgrade during the last week of December?
You can test before then. A first cutover in the last week of December is a poor time if the people who know the application are out. Aim the risky cutover at a week you can staff.
Sources
- Microsoft Learn, Windows Server 2016 lifecycle: https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2016
- Microsoft Learn, SQL Server 2016 lifecycle: https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2016