The main Windows Server 2025 features are hotpatching through Azure Arc, a modernised Active Directory with an optional 32k database page size, SMB over QUIC in Standard and Datacenter, stronger default security, GPU partitioning in Hyper-V and much higher virtual machine limits. It reached general availability on 1 November 2024 and is supported until November 2034.
| Area | What changed in Windows Server 2025 | Editions |
|---|---|---|
| Patching | Hotpatching via Azure Arc: most monthly security updates without a restart | Standard, Datacenter (Azure Edition built in) |
| Active Directory | Optional 32k database pages, new functional level, dMSA, LDAP over TLS 1.3 | All |
| File sharing | SMB over QUIC, SMB signing required on outbound connections, NTLM blocking option | Standard, Datacenter |
| Security defaults | Credential Guard on by default where supported, OpenSSH server installed, LAPS improvements | All |
| Hyper-V | GPU partitioning, Gen 2 VMs by default, 240 TB RAM and 2,048 vCPUs per VM | Standard, Datacenter |
| Storage | ReFS deduplication and compression, Storage Spaces Direct thin provisioning, NVMe optimisation | Varies (S2D Datacenter only) |
| Desktop and tools | In-place upgrade from 2012 R2, Wi-Fi and Bluetooth, WinGet and Windows Terminal included | All |
| Lifecycle | Mainstream to 13 November 2029, extended to 14 November 2034 | All |
Feature details below come from Microsoft's What's new in Windows Server 2025 documentation. Support dates are from the Windows Server 2025 lifecycle page.
What is new in Windows Server 2025?
Windows Server 2025 brings hotpatching to on-premises servers through Azure Arc, the first major Active Directory database change in decades, SMB over QUIC outside Azure, secure-by-default settings such as Credential Guard and stricter SMB and LDAP rules, larger Hyper-V limits with GPU partitioning, and a desktop experience aligned with Windows 11.
For most small and mid-sized businesses, the practical headline is fewer reboots and stronger defaults. The Active Directory and Hyper-V changes matter more as environments grow.
If you are still deciding between this release and its predecessor, our comparison of Windows Server 2025 vs 2022 weighs the upgrade case, licensing and hardware.
How does hotpatching work in Windows Server 2025?
Hotpatching installs most monthly security updates into running processes in memory, so the server does not need a restart. Microsoft plans a cycle of four baseline months per year, which require a restart, and eight hotpatch months. Outside Azure, Standard and Datacenter servers must be connected to Azure Arc with hotpatching enabled in the Azure portal.
Microsoft's hotpatch enablement guide for Arc-enabled servers lists the requirements:
- Windows Server 2025 Standard or Datacenter, build 26100.1742 or later, with Desktop Experience or Server Core.
- UEFI with Secure Boot and virtualisation-based security (VBS) running; Hyper-V guests must be Generation 2 VMs.
- An Azure subscription and the Azure Connected Machine agent, with hotpatching enabled through Azure Arc.
At the time of writing (November 2026), that Microsoft page states Arc-enabled hotpatching for Windows Server 2025 is available at no extra cost, after Microsoft initially announced it as a paid monthly subscription. Check the page before you plan, because Azure terms change. Datacenter: Azure Edition has hotpatching built in without Arc.
Cause and effect: hotpatching reduces restarts but does not remove them. Baseline months, unplanned baselines for fixes that cannot ship as hotpatches, and non-security updates such as driver or .NET updates can still require a reboot, so keep a maintenance window in the calendar.
What changed in Active Directory in Windows Server 2025?
Active Directory in Windows Server 2025 adds an optional 32k database page size, a new domain and forest functional level, delegated Managed Service Accounts (dMSA), LDAP over TLS 1.3, NUMA support beyond 64 cores, and stricter defaults such as LDAP signing for new deployments and no RC4 Kerberos tickets for TGTs.
- 32k pages: raise the limit on multivalued attributes to about 3,200 values, around 2.6 times the old 8k format. The switch is forest-wide and needs every domain controller to run Windows Server 2025 at the new functional level.
- Minimum levels: new forests require at least the Windows Server 2016 functional level.
- dMSA: lets you migrate a traditional service account to a managed account with randomised keys and disables the original password.
- Hardening: confidential attributes need an encrypted LDAP connection, and legacy SAM RPC password-change methods are blocked by default for remote calls.
Upgraded domain controllers keep the 8k format, so you gain 32k pages only after all DCs are replaced or rebuilt. Our step-by-step guide to migrating a domain controller to Windows Server 2025 covers the safe sequence.

Is SMB over QUIC available in Windows Server 2025 Standard?
Yes. SMB over QUIC, previously limited to Datacenter: Azure Edition, is now included in Windows Server 2025 Standard and Datacenter. It lets remote users reach file shares securely over UDP port 443 with TLS 1.3 encryption, without a traditional VPN, and Windows Server 2025 adds certificate-based client access control to restrict who can connect.
Other SMB changes tighten security by default, and they are the ones most likely to affect older devices:
- SMB signing is required for all outbound connections, not only SYSVOL and NETLOGON.
- An authentication rate limiter slows repeated failed NTLM sign-ins.
- The SMB client can block NTLM for outbound connections.
- Alternative ports can be configured for TCP, QUIC and RDMA.
What we commonly see: after an upgrade, older NAS boxes, scanners that save to a share, and legacy line-of-business apps are the usual casualties of signing and NTLM changes. Inventory these before upgrading and test them against a Windows Server 2025 test machine first.
What security features are on by default in Windows Server 2025?
Windows Server 2025 turns on Credential Guard by default on hardware that meets the requirements, installs the OpenSSH server component by default, enforces stronger SMB and LDAP signing, refuses default machine account passwords, and sets new Remote Access installations to reject PPTP and L2TP VPNs. Over 350 preconfigured security settings are available through OSConfig.
- Windows LAPS: can now create and manage the local administrator account itself, generate readable passphrases and detect image rollbacks.
- VBS enclaves and key protection: isolate secrets and sensitive workloads from administrators and the rest of the system.
- Certificates: the minimum RSA key length for TLS server authentication is 2,048 bits.
For remote administration, OpenSSH access is controlled through the OpenSSH Users group, which is useful for mixed Windows and Linux teams.
What is new in Hyper-V and storage in Windows Server 2025?
Hyper-V in Windows Server 2025 supports GPU partitioning with live migration and failover, Generation 2 VMs by default, workgroup clusters that can live migrate, and limits of 240 TB of memory and 2,048 virtual processors per VM. Storage adds ReFS deduplication and compression, block cloning, thin-provisioned Storage Spaces Direct volumes and optimised NVMe performance.
| Capability | Standard | Datacenter |
|---|---|---|
| Hyper-V and containers | Yes | Yes |
| GPU partitioning | Yes (standalone servers) | Yes (including clustered failover) |
| Storage Spaces Direct | No | Yes |
| Storage Replica | Yes | Yes |
| Network Controller (SDN) | No | Yes |
| Automatic VM Activation host | No (guest only) | Yes |
The edition rows follow Microsoft's Windows Server 2025 editions comparison. Licensing rules for virtual machines are covered in our Standard vs Datacenter vs Essentials guide; as a rule, Standard suits lightly virtualised hosts and Datacenter suits dense virtualisation or hyper-converged storage.
Can I upgrade to Windows Server 2025 in place?
Yes. Windows Server 2025 supports in-place upgrades from Windows Server 2012 R2 and later, up to four versions at a time, so Windows Server 2012 R2, 2016, 2019 and 2022 can upgrade directly while keeping roles, settings and data, provided the hardware and installed applications are supported on the new release.
Domain controllers are usually better migrated than upgraded in place, because a new DC can be introduced and the old one demoted with far less risk. With Windows Server 2016 extended support ending on 12 January 2027, our article on Windows Server 2012 R2 and 2016 end of support sets out the timeline and options.
Advanced nuance: Microsoft's in-place path covers the operating system only. Line-of-business software, backup agents and security tools need their own vendor support statements for Windows Server 2025, and these are what most often delay upgrades.
Which Windows Server 2025 edition should I buy?
Choose Windows Server 2025 Standard for physical servers or hosts running a small number of virtual machines, and Datacenter for heavily virtualised hosts, Storage Spaces Direct, software-defined networking or automatic VM activation. Both editions include hotpatching via Azure Arc, SMB over QUIC and the new Active Directory features.
For most small businesses running a file server, domain controller or a couple of VMs, Windows Server 2025 Standard is the practical choice; denser hosts suit Windows Server 2025 Datacenter. See each product page for current pricing, and remember that users or devices connecting to the server also need client access licences (CALs).
After purchase, our Windows Server 2025 Standard download, install and activation guide walks through setup.
Frequently asked questions
When was Windows Server 2025 released?
Windows Server 2025 reached general availability on 1 November 2024. It is a Long-Term Servicing Channel release under Microsoft's Fixed Lifecycle Policy, with mainstream support until 13 November 2029 and extended support until 14 November 2034, giving roughly ten years of security updates from launch.
Does Windows Server 2025 have a desktop like Windows 11?
Yes. The Desktop Experience installation option uses a Windows 11-style interface and includes Windows Terminal, WinGet and the Feedback Hub, along with Wi-Fi and Bluetooth support. Server Core remains available for administrators who prefer a smaller footprint without the graphical shell and manage the server remotely.
Is hotpatching free in Windows Server 2025?
At the time of writing, Microsoft's documentation states that hotpatching for Azure Arc-enabled Windows Server 2025 Standard and Datacenter is available at no extra cost. You still need an Azure subscription, the Azure Connected Machine agent and virtualisation-based security enabled. Datacenter: Azure Edition includes hotpatching natively when run on supported Azure platforms.
Can Windows Server 2025 domain controllers coexist with older ones?
Yes. Windows Server 2025 domain controllers can join existing domains running older domain controllers, provided the forest is at least at a supported functional level. New Active Directory features such as 32k database pages only become available once every domain controller runs Windows Server 2025 and you raise the functional level.
Do I need new CALs for Windows Server 2025?
Yes. Each user or device accessing Windows Server 2025 needs a Windows Server 2025 CAL, or a CAL for a later version. CALs for older releases such as 2019 or 2022 do not cover access to a 2025 server. Remote Desktop Services also needs its own RDS CALs in addition to the standard CALs.
Related guides
- Windows Server 2025 vs 2022: should you upgrade?
- Windows Server Standard vs Datacenter vs Essentials
- Migrate a domain controller to Windows Server 2025
- Windows Server 2025 Datacenter: download, install and activate
Links in this guide
| Link | Type | Why it helps |
|---|---|---|
| What's new in Windows Server 2025 (Microsoft Learn) | External | Microsoft's full feature list |
| Windows Server 2025 lifecycle (Microsoft Learn) | External | Official support end dates |
| Windows Server 2025 vs 2022 | Internal | Upgrade decision and differences |
| Enable hotpatch for Arc-enabled servers (Microsoft Learn) | External | Hotpatch requirements and current cost statement |
| Migrate a domain controller | Internal | Safe route to new AD features |
| Windows Server editions comparison (Microsoft Learn) | External | Standard vs Datacenter feature matrix |
| Standard vs Datacenter vs Essentials | Internal | Edition and VM licensing rules |
| Windows Server 2012 R2 and 2016 end of support | Internal | Timeline for older servers |
| Windows Server 2025 Standard | Internal | Licence for small business servers |
| Windows Server 2025 Datacenter | Internal | Licence for heavily virtualised hosts |
| Windows Server CALs explained | Internal | Access licences needed alongside the server |
| Windows Server 2025 Standard install guide | Internal | Setup and activation steps |
