After January 12, 2027 Windows Server 2016 gets no more security updates unless you pay for Extended Security Updates (Standard and Datacenter only); IIS 10 on it and .NET Framework 4.6.2 lose support the same day. Here are Microsoft's options, an inventory script and the choices for each app.
| Product | End of support |
|---|---|
| Windows Server 2016: Datacenter, Essentials, MultiPoint Premium, Standard | January 12, 2027 |
| IIS 10 on Windows Server 2016 | January 12, 2027 |
| .NET Framework 4.6.2, which Windows Server 2016 ships with | January 12, 2027 |
| .NET Framework 4.7 to 4.8 and 3.5 SP1 on Windows Server 2016 | With the OS (they are OS components) |
| Containers released with Windows Server 2016 | With the OS, per the lifecycle page |
Microsoft's blog posts, ESU FAQ table and 2027 list say January 12, 2027. The lifecycle page says its dates are in Pacific Time, but its HTML stores times with no time zone (1/13/2027 6:59:59 AM for the end of extended support, 1/13/2027 8:00:00 AM for the start of ESU Year 1), and its script reads them in your computer's time zone before showing a Pacific date, so it can read Jan 12 or Jan 13 depending on where you open it. One ESU FAQ answer even says 2026. Plan for January 12, 2027.
After that, these products get no new security or non-security updates and no free or paid assisted support; ESUs for Windows Server 2016, below, are the paid exception.
| Target | In place from 2016 | Extended support ends | .NET Framework |
|---|---|---|---|
| Windows Server 2019 | Yes, from installation media | January 9, 2029 | 4.7.2 included, 4.8 installable |
| Windows Server 2022 | Yes, from installation media | October 14, 2031 | 4.8 included, 4.8.1 installable |
| Windows Server 2025 | Yes, from installation media | November 14, 2034 | 4.8.1 included |
server2025Upgrade, server2022Upgrade or server2019Upgrade) and need KMS activation and managed disks; afterwards features such as Hotpatching and Azure Update Manager aren't officially supported on that VM..NET Framework 4.x versions are in-place updates: Microsoft expects older 4.x apps to run without a recompile but recommends testing in pre-production first. Windows Server 2025 also disables TLS 1.0 and 1.1 by default, removes NTLMv1 and the SMTP Server feature (with no in-box replacement), and ships VBScript as a preinstalled feature on demand. Microsoft lists VBScript as removed in Windows Server 2028, now in preview, and says preview plans can change before release.
Run this as administrator on each 2016 server.
# Most lists go to CSV files in the current folder
Import-Module IISAdministration
Get-IISAppPool | Select-Object Name, ManagedRuntimeVersion, ManagedPipelineMode, Enable32BitAppOnWin64,
@{n='Identity';e={$_.ProcessModel.IdentityType}}, @{n='User';e={$_.ProcessModel.UserName}} |
Export-Csv apppools.csv -NoTypeInformation
Get-IISSite | ForEach-Object { $site = $_.Name; $_.Applications | Select-Object @{n='Site';e={$site}}, Path,
ApplicationPoolName, @{n='Folder';e={($_.VirtualDirectories | Where-Object Path -eq '/').PhysicalPath}} } |
Export-Csv apps.csv -NoTypeInformation
Get-IISSite | ForEach-Object { $site = $_.Name; $_.Bindings | Select-Object @{n='Site';e={$site}},
Protocol, BindingInformation, CertificateStoreName } | Export-Csv bindings.csv -NoTypeInformation
# .NET Framework 4.x: 394802 = 4.6.2 on Windows Server 2016, 528040 or higher = 4.8 or later
Get-ItemPropertyValue -LiteralPath 'HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Release
# Services whose binary is outside \Windows\, with the account they run as
Get-CimInstance Win32_Service | Where-Object { $_.PathName -notlike '*\Windows\*' } |
Select-Object Name, State, StartMode, StartName, PathName | Export-Csv services.csv -NoTypeInformation
# Scheduled tasks outside \Microsoft\: a list plus their full XML definitions
$tasks = Get-ScheduledTask | Where-Object { $_.TaskPath -notlike '\Microsoft\*' }
$tasks | Select-Object TaskPath, TaskName, State | Export-Csv tasks.csv -NoTypeInformation
$tasks | Export-ScheduledTask | Out-File tasks-xml.txt
# Certificates, HTTP.sys certificate bindings and URL reservations
Get-ChildItem Cert:\LocalMachine\My | Select-Object Subject, NotAfter, HasPrivateKey, Thumbprint |
Export-Csv certs.csv -NoTypeInformation
netsh http show sslcert > sslcert.txt
netsh http show urlacl > urlacl.txt
# COM+ applications, then installed roles and features
$apps = (New-Object -ComObject COMAdmin.COMAdminCatalog).GetCollection('Applications')
$apps.Populate(); foreach ($app in $apps) { $app.Name }
Get-WindowsFeature | Where-Object Installed | Select-Object Name | Export-Csv features.csv -NoTypeInformation
v4.0 is CLR 4 (.NET Framework 4.x), v2.0 CLR 2 (2.0, 3.0 or 3.5). Microsoft recommends but doesn't require No Managed Code for ASP.NET Core pools, so check web.config for an aspNetCore element.Enable32BitAppOnWin64 True lets the pool run 32-bit applications on 64-bit Windows: look for 32-bit COM or native DLLs that may need it.Server.CreateObject, Type.GetTypeFromProgID and Interop.*.dll.applicationHost.config: its globalModules section lists every native module, third-party ones included.Register-ScheduledTask -Xml.| What you found | Where it can go | Watch for |
|---|---|---|
| ASP.NET Web Forms, MVC or Web API on .NET Framework 4.x | App Service on Windows, or IIS 10 on Windows Server 2022 or 2025 | On App Service, v4.0 means the latest CLR 4. The App Service Migration Assistant and its scripts cover one IIS server; Azure Catalyst migrates in bulk from IIS servers in VMware environments. |
| COM components, registry values, GAC assemblies, MSI installers or the MSMQ client | Managed Instance on App Service, a Windows container or a VM | Managed Instance: generally available in select regions, Pv4 and Pmv4 plans only; no domain join, NTLM or Kerberos, no WebJobs, no TCP or NetPipes. |
| Windows services | A Windows Server 2022 or 2025 VM, or a .NET 10 Worker Service | Worker Services run as services via Microsoft.Extensions.Hosting.WindowsServices (AddWindowsService). COM+ (System.EnterpriseServices), Remoting and Workflow Foundation aren't on .NET 6+; WCF servers go to CoreWCF. |
| Scheduled tasks and console jobs | Task Scheduler on the new server | Run-as accounts, drive letters and paths. |
| Apps on .NET 8 or 9 | .NET 10 | Support ended November 10, 2026: see our .NET 10 upgrade guide. |
| Classic ASP | IIS on Windows Server 2025 for now | VBScript is on its way out: see our classic ASP guide. |
Images built on Windows Server 2016 run on 2022 or 2025 hosts only with Hyper-V isolation, and process isolation needs a matching base. The compatibility table also allows 2022 images with process isolation on 2025 hosts, while the same page's text names 2022 images on Windows 11 as the only exception. Rebuild on Microsoft's supported ASP.NET tags, such as mcr.microsoft.com/dotnet/framework/aspnet:4.8.1-windowsservercore-ltsc2022 or 4.8.1-windowsservercore-ltsc2025, which include IIS 10. App Service also runs Windows containers for apps that need the GAC. Microsoft's 2027 list still retires Windows Server 2022 on AKS on March 15, 2027, but the current AKS docs say AKS stops supporting Windows Server 2022 node pools on June 30, 2028. One more conflict: the base image table gives 01/11/2027 for the 2016 Server Core image, while the lifecycle page says 2016 containers follow the OS dates.
.NET 10, the current LTS release, is supported until November 14, 2028. Microsoft calls moving ASP.NET to ASP.NET Core "non-trivial for the majority of production apps", recommends incremental migration for large ones and offers the GitHub Copilot app modernization agent. Porting alone doesn't fix the host: .NET 10 still lists Windows Server 2016 as supported, but the OS loses support on January 12, 2027.