For years Windows Server followed a simple rule. The machine arrived open, compatible with almost everything that had come before it, and the administrator closed the doors one at a time, if anyone found the time to do it. On November 17, 2026, in a post on the Windows Server blog, Christina Curlette and Carlos Mayol Berral of Microsoft’s Windows Server team said the rule was being reversed. Starting with Windows Server Insider Preview build 29706, Server Core installs hardened. Hundreds of security settings are on from the first boot, lined up with the benchmarks auditors already use: CIS, and DISA STIG, the US Defense Department’s checklist.
The company’s own announcement of Windows Server 2028, now in public preview, sells this as saving administrators the work of building a secure baseline on day one. Nick Indge, writing for Ars Technica, describes the deal more bluntly: compatibility is traded for security out of the box, and there will be growing pains.
The doors that close
The blog post lists what changes. On identity, Kerberos is preferred over NTLM, LSASS (the Windows process that holds credentials) is protected, strong passwords and account lockout are enforced, and consumer accounts are not allowed. On the network, SMB traffic is signed and encrypted, the firewall is on in every profile, and legacy name resolution and unauthenticated RPC are switched off. TLS is restricted to modern cipher suites, and key exchange is hybrid post-quantum, built on ML-KEM.

Take it as a reflection rather than a finding: every empire of software builds its walls late, after the old roads have been worn deep by traffic nobody remembers approving. A default is a decision made once on behalf of millions of machines. Leaving the gates open was a choice too, though for many years nobody called it one.
A confession in advance
Microsoft does not claim the change is free. The team writes that “some things that worked on Windows Server 2025 may not work on Windows Server 2028 without changes,” and names the likely casualties: older protocols, legacy authentication, and some of the management tools and scripts that hold real server rooms together. Administrators are told to test before deploying and to loosen only the settings a workload actually needs.
We want to hear where a hardened default gets in the way of a real workload: which setting, which application, and what you had to change to get it working. That is how the defaults get better before general availability.

That is the Windows Server Team, asking the people who keep the old systems running to report every place where the new walls get in the way. Microsoft has also supplied the tools for that bargaining. Get-MSHardenedPolicyScore rates a server, category by category, against the hardened state. Set-MSHardenedPolicy puts the hardened values back. Restore-MSHardenedPolicy takes them out, and the team is careful to say that it restores standard Windows Server behaviour, not whatever configuration the machine had before. Another warning sits in the notes: tools such as gpresult will report these settings as Not Configured, because they are built into the image rather than written to a policy file.
Walls still unfinished
The preview is not a release candidate, and Microsoft asks that nobody treat it as one. The hardening itself is incomplete. Hardware-backed protections such as Secure Boot and DMA requirements will not be enforced until a later preview build, and the blog adds kernel shadow stacks to that list. Kerberos is now preferred, but actually blocking NTLM also waits for a later release, as does print and RPC hardening, including Windows Protected Print. Scores below 100 percent, the team says, are expected on this build.

Then comes the flaw inside the fortress. According to the release notes, “A race condition in the TLS hybrid key exchange implementation may cause the LSASS service to crash when hybrid groups are negotiated by a TLS server.” So the new post-quantum key exchange can bring down the very credential process the release sets out to protect. Microsoft’s advice for now is to disable the hybrid key-exchange groups until the bug is fixed. Microsoft’s fixes have opened holes before: earlier this month a repair to its most-exploited driver became a fresh route to SYSTEM.
The quieter change
One change has nothing to do with security. Microsoft’s native NVMe storage stack arrived in an update to Windows Server 2025, but administrators had to turn it on by hand. It removes the old practice of translating NVMe through a SCSI stack, which makes storage faster and cuts overhead. In Windows Server 2028 it is on by default. A rundown by 4sysops also lists booting from ReFS and Intune management among the new features, and BleepingComputer likewise put the hardened security at the centre of the launch.
System administrators, along with the homelabbers who run servers in their spare rooms, can download the preview by registering with the Windows Insider Program. Feedback goes to the Windows Server Insiders forum, and organisations that want to work directly with the team can join its Technology Adoption Program.

