On 1 November 2024, Microsoft made Windows Server 2025, the new long-term servicing (LTSC) release of Windows Server, generally available. The official announcement appeared on 4 November on the Windows Server blog, and the 180-day evaluation version can be downloaded from the Evaluation Center. Under the Fixed Lifecycle Policy, the release gets five years of mainstream support and a further five years of extended support; you can find the exact dates on Microsoft’s lifecycle page.
In this article we round up what’s new, what to watch for when upgrading, and when it’s worth switching – or waiting.
First lesson: check your update management
In the first week after the release, several sysadmins woke up to find that their Windows Server 2022 machines had upgraded to Windows Server 2025 overnight. Microsoft published the server version’s upgrade package under the same KB number (KB5044284) as the Windows 11 24H2 update, and some third-party patch management tools treated it as a regular security update. According to Microsoft, the fault was in how the third-party tools classified it; according to the vendors, it was in Microsoft’s labelling – for those affected, it makes no difference.
The problem is not only the unexpected change: Windows Server 2025 needs a new licence, so an accidental upgrade also causes a licensing problem, and rolling back is only possible from a backup. If you use a patch management tool, check now how it classifies feature updates, and block the Windows Server 2025 upgrade until you have decided on it. Cases like this also show why you need a fresh backup before an update; we wrote about this in our article on the lessons of the CrowdStrike outage too.
What’s new in Windows Server 2025?
| Area | Change |
|---|---|
| Updates without restarting | Hotpatch on Standard and Datacenter machines connected to Azure Arc too (as a preview; later with a monthly subscription) |
| Active Directory | New forest and domain functional level, optional 32k database page size, TLS 1.3 for LDAP, LDAP encryption by default |
| File sharing | SMB over QUIC in the Standard and Datacenter editions too, mandatory SMB signing for outbound connections |
| Hyper-V | Up to 2,048 virtual processors and 240 TB of memory per Generation 2 VM, GPU partitioning with live migration |
| Storage | Optimised NVMe handling, up to 60% more IOPS according to Microsoft’s measurements |
| Management | OpenSSH server and WinGet installed by default, Windows 11 desktop interface |
| Licensing | Usage-based (pay-as-you-go) licensing is also available through Azure Arc |
For most companies, the security defaults matter most: Credential Guard enabled by default, mandatory SMB signing, stricter Kerberos and LDAP settings. These are good, but they can cause surprises with old applications, NAS devices and printers if those don’t support the newer protocols. Hotpatch lets some of the security fixes be installed without a restart – but without Azure Arc, on your own machines, it isn’t available.
How can you upgrade?
Windows Server 2025 can skip at most four versions in one step: from Windows Server 2012 R2 and later you can do a direct in-place upgrade. This is fast, but the old settings and faults carry over too.
For critical roles, we still recommend a fresh installation:
- Domain controllers: add a new 2025 domain controller, transfer the roles (FSMO), then demote the old machine. Only raise the functional level once every domain controller is on 2025.
- Application servers: a new machine, moving the application and the data across, with the old machine kept as a fallback.
- File servers: Storage Migration Service helps move the shares and permissions.
Before you start, check with the vendors whether the applications you use – accounting software, antivirus, backup software – already support the 2025 version, and read Microsoft’s list of known issues on the Windows Server 2025 release health page. The new version needs new server licences and client access licences (CALs), unless you have a Software Assurance agreement.
Is it worth switching now?
It depends on where you are starting from:
- For a new server: yes, the 2025 version is the natural choice, since it’s supported the longest.
- From Windows Server 2022: not urgent. Extended support for the 2022 release lasts until October 2031, so you can safely wait until the 2025 version matures and the vendors catch up.
- From Windows Server 2019: extended support lasts until January 2029, so you have time to plan.
- From Windows Server 2016: this is where it’s worth starting now. Support ends on 12 January 2027, and planning and testing a migration can take months.
- From Windows Server 2012 R2 or older: these are already out of support (or running on paid ESU), so the move can’t be postponed. We wrote about handling end-of-life systems in our article on EOL strategies.
For a critical production server, we would definitely wait for the first few monthly cumulative updates, and try the upgrade on a test machine first.
Windows Server 2025 as a virtual machine
At most smaller companies, Windows Server no longer runs on bare metal but as a virtual machine, and this makes upgrading simpler too: the old and the new server can run side by side for a while, and a snapshot gives you a quick way back.
If the hypervisor isn’t Hyper-V but, for example, Proxmox VE or another KVM-based system, Windows Server 2025 can be installed just the same, but watch out for a few things:
- VirtIO drivers: for the disk and network controllers, you have to load the drivers from the virtio-win package during installation. With the new release it’s worth using a recent virtio-win version, and testing disk performance extensively before going live.
- UEFI and Secure Boot: install it with OVMF (UEFI) firmware, the Q35 machine type and a virtual TPM, so nothing will stand in the way of the security features later.
- QEMU Guest Agent: install the guest agent too, for clean shutdowns and consistent backups.
- Licensing: the Windows Server licence is tied to the cores of the physical machine even if the hypervisor isn’t a Microsoft product. The Standard edition covers two virtual machines on a fully licensed host, Datacenter an unlimited number.
If you are planning to switch hypervisors anyway because of VMware’s licensing changes, it’s worth combining the two projects. We wrote in detail earlier about why Proxmox VE is a good choice for smaller companies.
Do you need Windows Server at all?
A new Windows Server version is a good opportunity to ask, role by role: do we need this in this form? An internal file server can be replaced with a Samba share running on Linux or with cloud storage, a PHP application running on IIS is happier on Linux, even in a container, and DNS and DHCP can run on a small Linux machine too. Where Windows Server stays because of Active Directory or a Windows-only application, you don’t have to keep everything else on Windows as well.
We help on the Linux side: we assess which services can be moved, we plan and carry out the migration, and we build a Proxmox VE-based virtualisation environment on which the remaining Windows servers can also run safely. You can read about this on the Infrastructure and operations page.