Windows Server 2025 on a VPS: What Changed for IIS, Hyper-V and SMB Signing Defaults

Windows Server 2025 does not change what a server is, but it changes several defaults that a hosted VPS owner will hit within the first week. SMB signing is now required by default for outbound client connections, the SMB over QUIC option has matured, Hyper-V gained new virtual processor support, and IIS now ships HTTP/3 enabled more broadly. Deploying 2025 with the habits you built on 2019 is a reliable way to break file shares and RDP-adjacent workflows in ways that look like network faults.

This is a practical what-changed list for people running Windows Server on rented infrastructure — a single NIC, a public IP, no domain controller in sight. If you have not provisioned the instance yet, our Windows VPS guides cover the base build; this article assumes an installed 2025 Datacenter or Standard edition.

SMB Signing Is On by Default for Clients

The headline change is behavioural, not cosmetic. On Windows Server 2025 the SMB client requires signing by default, and the server also enforces signing for SYSVOL and NETLOGON shares. The client-side policy is Computer Configuration → Windows Components → SMB Client → Require signing, backed by the registry value RequireSecuritySignature under HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters, now defaulting to 1.

The practical consequence: connecting a 2025 server to an older NAS appliance, a third-party SMB gateway, or a legacy backup target that does not sign will fail with STATUS_ACCESS_DENIED (0xC0000022) at the tree-connect stage, or the vaguer 0x80070035 “network path was not found”. Use Get-SmbClientConfiguration | Select RequireSecuritySignature and Get-SmbConnection to see whether a mapping is signed. To investigate a specific path, enable the SMB client log: Set-SmbClientConfiguration -EnableSecuritySignature $true is separate from requiring it, and auditing lives in Microsoft-Windows-SMBClient/Connectivity.

If you must talk to an unsigned third party, scope the relaxation rather than turning signing off globally. Windows 2025 supports per-server exceptions through the SMB client’s “insecure guest auth” and signing exemption settings, but the cleanest fix is to replace the endpoint. Turning off required signing on the whole server is the kind of shortcut that survives into production and quietly weakens every subsequent share.

What IIS Ships With Now

IIS 10 in Server 2025 continues to default HTTP/2 on for HTTPS bindings, and HTTP/3 over QUIC is available without the separate Windows feature dance that 2022 required in some builds. HTTP/3 listens on UDP 443, so a hosted VPS firewall that only permits TCP 443 will silently negotiate down to HTTP/2 — no error, just no QUIC. Verify with Get-NetFirewallRule -DisplayName "*HTTP/3*" and confirm the provider’s edge allows UDP.

Application pool defaults have shifted slightly: idle timeout remains 20 minutes but the default start mode and rapid-fail protection thresholds are worth reviewing for a low-traffic VPS where an app pool stopping under five rapid failures looks identical to an application crash. Check with Get-IISAppPool | Select Name,State,ProcessModel and set rapidFailProtectionMaxCrashes deliberately in applicationHost.config.

One additional 2025 detail: the ASP.NET Core Hosting Bundle for .NET 8 and .NET 9 must be installed separately, exactly as before, and the ANCM module version must match your runtime. A mismatch produces HTTP 500.30 or 500.31 on the first request, with the real cause in the Application event log rather than the IIS log.

Hyper-V: Bigger Guests and Stricter Defaults

Hyper-V in 2025 raises the ceiling per VM — more virtual processors and more memory per guest — and adds support for newer CPU generations in generation-2 VMs. On a rented VPS, the practical limit is nested virtualisation: your provider must expose VT-x/AMD-V and, for Hyper-V inside the guest, the host must not strip the CPU features. Check with systeminfo for “A hypervisor has been detected” and Get-VMHost | Select LogicalProcessorCount,MemoryCapacity once the role is installed.

Default VM network adapter type is now a synthetic adapter on a virtual switch that must exist before you create the VM. Creating a VM on a fresh install with one NIC and no external switch yields a VM with no connectivity and no obvious error — New-VMSwitch -Name External -NetAdapterName Ethernet first, then attach. Also note that dynamic memory is enabled by default on new VMs, which is fine for Linux guests but can starve a Windows guest doing a large build unless you set a sensible minimum.

Storage and the New Default Volume Format

New volumes created by the 2025 setup and by New-Volume default to larger cluster sizes in some scenarios and ReFS is offered more prominently for data volumes. For a VPS with a single virtual disk, NTFS remains the right answer for most workloads — ReFS block cloning is excellent for Hyper-V and Veeam-style backup targets, not for a general file server. Check what you actually got with Get-Volume | Select DriveLetter,FileSystem,AllocationUnitSize.

Storage Spaces Direct is out of reach on a single VPS, but Storage Spaces (non-direct) still works and is occasionally useful for mirroring two attached data disks. Do not enable it on the system disk; the boot volume must stay a plain NTFS partition for recovery simplicity.

Security Defaults That Change Your Scripts

Several legacy protocols are now disabled or absent by default: TLS 1.0 and 1.1 are off, SMB1 is not installed, and the Print Spooler service starts in a more restricted mode on servers that are not print servers. Any deployment script that relied on Enable-WindowsOptionalFeature -FeatureName SMB1Protocol succeeding will now need an explicit re-enable and a security exception, which is usually the correct answer to “why is my old app failing”.

Credential Guard and Virtualization-Based Security are enabled by default on new installs where the hardware supports them. On a VPS this can conflict with nested Hyper-V or with third-party hypervisor-based agents. If a VM or agent refuses to start with a hypervisor-related error, check Get-CimInstance -ClassName Win32_DeviceGuard and the SecurityServicesRunning value before assuming the provider is at fault.

A Short Checklist Before You Deploy

Confirm UDP 443 if you want HTTP/3; confirm SMB signing compatibility with every appliance you mount; create the Hyper-V virtual switch before creating VMs; install the correct .NET Hosting Bundle; and decide deliberately whether VBS and Credential Guard should stay on. Each of these is a default that changed, not a bug.

Finally, size for 2025 rather than for 2019. The baseline footprint is larger, and a 2 GB instance that ran a 2019 file server comfortably will page under 2025 with the same role set. If you are choosing a plan now, compare Windows VPS plans with 4 GB as the realistic floor for anything beyond a single IIS site.

Leave a Comment