Windows Server 2016: ESU buys time, not a plan
On 12 January 2027, Windows Server 2016 gets its last regular security update. Microsoft offers paid Extended Security Updates until 2030, but itself calls them a bridge, not a solution. For the Essentials edition there is not even that.
On Tuesday, 12 January 2027, Microsoft delivers the last regular security update for Windows Server 2016. Mainstream support already ended in January 2022; since then the version has been in extended support. That leaves nine weeks, with Christmas and the turn of the year in between.
Unlike with earlier versions, many quickly have an answer at hand: then we will just buy ESU. That works, but it does not answer the actual question.
What Microsoft offers
For Windows Server 2016, Extended Security Updates are available for up to three years, that is, until 2030. The conditions are in Microsoft's documentation:
- Only security updates rated Critical and Important. No new features, no non-security fixes, no design changes. Technical support for the operating system itself is not extended; it is limited to activating and installing the ESU updates.
- Only Standard and Datacenter. Other editions are excluded.
- Only with the right licence. Buying ESU requires Software Assurance through a volume licensing programme such as an Enterprise Agreement or Open Value, or licensing through SPLA or a server subscription.
- Two ways to obtain it. The classic route through volume licensing, in yearly increments, or through Azure Arc with monthly billing. For Arc, the server must be connected to Azure; it can be configured since 3 August 2026, and billing starts on 13 January 2027.
Microsoft itself puts the programme in context: it is not intended as a long-term solution but as a temporary bridge.
Essentials: no bridge
There is no ESU for Windows Server 2016 Essentials. Microsoft says so explicitly in a separate notice. On the same 12 January, the Essentials features also end, including Remote Web Access and the address under remotewebaccess.com.
Essentials typically sits in small units: branch offices, practices, small businesses, associations. There the server is often file storage, client backup and remote access in one. Microsoft points out that there is no one-to-one replacement for this package. Anyone who only swaps the operating system may end up without remote access and without client backup.
Why ESU is not a decision
ESU moves the date, not the question. Three reasons:
- The bridge has an end. By 2030 at the latest, the same decision is due again, then with hardware three years older and a business application whose vendor is three years further on.
- Security updates are not everything. Whether the vendor of a business application still supports its software on a server without regular support is not covered by any ESU contract.
- It applies per server. ESU is not a tick box for the whole estate. Every server that stays needs its own justification, its licence and someone who keeps an eye on the end date.
Not visible from outside
Anyone who wants to count their servers with an external scan hits a limit: Windows Server 2016 ships IIS version 10.0, and the web server of 2019, 2022 and 2025 reports the same version number. The server header therefore does not reveal the version. The answer is in the inventory, per device with version and edition, or it is nowhere.
What to do in nine weeks
- Count first. Which servers run 2016, in which edition, with which role? Domain controller, file server, database, business application, print server.
- Then the Essentials servers. There is no extension for them. Remote access and client backup need a replacement that has been tested before 12 January.
- Then decide per server. Upgrade or migrate, switch off, or ESU with a justification, an owner and an end date.
- Check the licence before planning with ESU. Without Software Assurance or an Arc connection there is no ESU. That should be settled before the turn of the year, not after.
- Document the exception. A server that keeps running without updates is a risk someone carries deliberately. Then it should be written down somewhere, with a date and a name.
The test question
For how many of your Windows Server 2016 servers is it settled today what happens to them on 13 January?
If the answer is "for most of them, ESU": for which of them has the licence already been checked?
Sources
Microsoft Lifecycle: Windows Server 2016, retrieved 10 November 2026.
Microsoft Learn: Prepare to deliver Extended Security Updates for Windows Server through Azure Arc, as of 13 October 2026.
Windows IT Pro Blog: Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support, retrieved 10 November 2026.
Microsoft Support: Windows Server 2016 Essentials end of support, retrieved 10 November 2026.
Questions about this update?
Talk to us – we are happy to show you this feature in a demo.


