Technology

Windows Server 2016 stops receiving updates on January 13, 2027: what to do in your business with the time left

About two months are left. After that date, only servers enrolled in Extended Security Updates (ESU) will receive security patches. We explain what that means, what options you have and how to approach the decision.

Published on November 17, 2026 · The mitza.es team

On 16 November 2026, BleepingComputer reported on a notice in Microsoft's message center: on 13 January 2027 all editions of Windows Server 2016 will reach the end of extended support. Microsoft's own lifecycle page confirms it. If your company has a file, application, domain or virtualization server running this version, now is the time to decide.

What "end of extended support" means

  • From that date, Microsoft stops publishing free security updates for Windows Server 2016.
  • According to BleepingComputer, monthly security updates will continue afterwards only for machines enrolled in Extended Security Updates (ESU).
  • An unpatched server keeps running, but every new flaw that is discovered, and we already know they are published by the hundreds every month, will stay unfixed. Servers are a very attractive target: they hold data and credentials.

For a small business there are also practical consequences: your cyber insurance may ask about unsupported systems (more in our cyber insurance guide), and the NIS2 directive and the GDPR expect measures appropriate to the risk.

The dates, according to Microsoft's lifecycle page

  • End of mainstream support: 12 January 2022.
  • End of extended support: 13 January 2027.
  • ESU: Year 1 from 13 January 2027 to 11 January 2028; Year 2 until 9 January 2029; Year 3 until 8 January 2030.

In the sources we have read, we have not found how to purchase ESU for Windows Server 2016 or what it costs. Ask your provider or Microsoft before counting on it.

The options

  1. Migrate to a supported version. This is the long-term option: install a new server with a current version of Windows Server and move the services and data over. It requires planning, testing your applications and having a cutover window.
  2. Upgrade in place (changing the version on the same server). It is possible in many cases, but it is best done with a full backup, prior testing and confirmation that your applications and hardware are compatible.
  3. Move the workload to the cloud (virtual machines or managed services), if it fits your case. You can find a guide in cloud computing for small businesses.
  4. Buy ESU as a stopgap, only if there is no other way out, knowing that it is a temporary solution and that it is purchased by the year (three at most, according to Microsoft's schedule).
  5. Retire the server if it is no longer used. It is more common than it seems: a forgotten server is an open door.

A two-month plan

  1. This week: inventory. Which servers you have, which version of Windows Server they run, what they do and who depends on them. Include virtual machines and "single-purpose" servers.
  2. Weeks 2 and 3: decision. For each server, choose between migrating, upgrading, moving to the cloud, buying ESU or retiring it. Take into account old applications that don't work on newer versions.
  3. Weeks 3 to 6: preparation. Tested backups (3-2-1 rule), a new server, tests with key users and a rollback plan.
  4. Weeks 6 to 8: migration and monitoring. Ideally on a quiet weekend, avoiding critical dates for your business. Keep the old server switched off but available for a few days.
  5. Afterwards: document what was done and set an update schedule. Indicative deadlines are in our guide to reading a security advisory.

If you can't migrate in time, reduce the risk in the meantime: isolate the server on its own network, limit who can connect to it (and don't expose it to the internet), require two-step verification to administer it and monitor its logs.

A pattern that keeps repeating

It is the same problem we already saw with the end of support for Windows 10 (ESU) and with Windows 11 24H2 and Office 2021: a date that seems far away and then arrives. The sooner you decide, the cheaper and less stressful it is. If you also have machines that struggle to update, see our guide on Windows Update not working.

Quick questions

Will my server stop working on January 13?

No. It will keep running, but without new security patches (unless you buy ESU). The risk grows over time.

What about Windows Server 2012 R2 or 2019?

The lifecycle page we consulted covers only Windows Server 2016, so we don't give dates for other versions. Check them on Microsoft's lifecycle page for each product.

How much does it cost to migrate?

It depends on the number of servers, the applications and the option chosen. That is why it is best to start with the inventory and ask for a fixed quote.

How we can help at Mitza

We take an inventory of your servers, weigh the options and plan the migration. Take a look at our IT maintenance for small businesses, our computer repair and maintenance service, or write to us from the contact page.

Related reading: the November 2026 Patch Tuesday and whether your business needs a NAS.

Do you have a Windows Server 2016 machine and don't know what to do?

We take an inventory of your servers, weigh the options and plan the migration without unnecessary downtime.

No spam. No sales calls. Just your personalised reply.