Key facts
- Microsoft said the preview's hardened security settings may break software using older protocols, legacy authentication or management scripts.
- The Windows Server Team asked testers to report which setting, application and change were involved when a hardened default blocked a workload.
- Microsoft said Secure Boot and DMA requirements will not be enforced until a later preview build.
- NTLM blocking will wait for a later preview release, though Kerberos is now the default preference.
- Microsoft's release notes said a race condition in the TLS hybrid key exchange may crash the LSASS service, and recommended disabling hybrid-key exchange groups.
Microsoft published a public preview of Windows Server 2028 on November 18, 2026, with hardened security settings switched on by default. The company's native NVMe storage stack, first offered through an update to Windows Server 2025 that administrators had to enable manually, is default-on in the new build. Microsoft said the redesign removed NVMe translation through a SCSI stack, improving speeds and reducing overhead.
Microsoft said the hardened defaults may break things because of software compatibility issues with older protocols, legacy authentication, or management tools and scripts. "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," the Windows Server Team said in a blog post. "That is how the defaults get better before general availability."
Microsoft said the build is not a release candidate and should not be treated as one. Hardware-backed protections including Secure Boot and DMA requirements will not be enforced until a later preview build, and NTLM blocking will also wait for a later preview release, though Kerberos is now the default preference over NTLM.
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. Microsoft recommended disabling hybrid-key exchange groups until the problem is addressed. Administrators can test the build by registering with the Microsoft Windows Insider Program.
