Microsoft’s upcoming Windows Server 2028 preview combines a redesigned Native NVMe storage stack with stronger security defaults intended to harden Server Core deployments. The NVMe stack, introduced in Windows Server 2025 but previously requiring manual activation, is enabled by default in Windows Server 2028. Microsoft cautions that the hardened configuration may cause compatibility problems with older protocols, legacy authentication systems, management tools, and scripts, and is asking administrators to test the preview and report issues before public release.
Credit: Microsoft blog
Native NVMe support enabled by default
Microsoft first introduced its Native NVMe storage stack through an update for Windows Server 2025. Administrators initially had to enable it manually. The redesigned stack improves performance and reduces overhead by eliminating the need to route NVMe traffic through the SCSI stack. In Windows Server 2028, the technology is enabled by default.
Hardened defaults may affect compatibility
Microsoft says the enhanced security settings could create problems for software and infrastructure that depend on older protocols, legacy authentication methods, or existing management tools and scripts. The company is asking users to test their real-world workloads and report any configuration changes required.
“We want to hear where the hardened defaults are holding you back in your real-world workloads: what settings, which applications, and what did you need to change to make it work?” the Windows Server team said in its blog post. “This way, the defaults are improved before public release.”
Security features are still being phased in
Microsoft recommends using the preview builds as test environments to identify compatibility and other issues. The current build is not a release candidate and should not be treated as one.
Although the preview introduces a more security-focused default configuration, hardware-based protections such as Secure Boot and DMA requirements will not be enforced until later preview builds. Kerberos is currently preferred over NTLM by default, but Microsoft will not block NTLM until a future preview release.
Known TLS issue
The current build also contains a known issue that conflicts with its security goals. According to the release notes, “A race condition in the implementation of TLS Hybrid Key Exchange can cause the LSASS service to crash when hybrid groups are negotiated by the TLS server.” Microsoft recommends disabling Hybrid Key Exchange groups until the problem is fixed.
System administrators and interested home users can register to test Windows Server 2028 through the Microsoft Windows Insider Program.
Source: arstechnica.com


