Windows Server 2028 Preview Hardens Server Core by Default in Build 29706, but NTLM Is Still Open
Security / news
Windows Server 2028 Preview Hardens Server Core by Default in Build 29706, but NTLM Is Still Open
Hundreds of settings are on from first boot, Microsoft warns Server 2025 workloads may break, and the 33 percent of servers still on 2019 are untouched.

Windows Server 2028 Server Core installs with hundreds of security settings switched on from the first boot, starting with Insider Preview build 29706, Microsoft said on Nov. 17. Anything that relied on older protocols, legacy authentication or old management scripts on Windows Server 2025 may stop working, and Microsoft's own post says so in plain terms. The preview covers Server Core only, and NTLM is not yet blocked.
The announcement comes from the Windows Server team's post "Announcing Hardened Server Core for Windows Server Insiders", written by Carlos Mayol Berral and Christina Curlette. It sets the hardened state as the default for new installs, measured against the CIS and DISA STIG benchmarks. BleepingComputer and The Register covered it on Nov. 18.
What Microsoft turns on by default
Microsoft groups the defaults into six areas. The post gives no total, only "Hundreds of security settings are on from first boot." A sample scoring run in it shows a PolicyCount of 237, which is a figure from that run and not a count of settings.
| Area | Examples from Microsoft's list |
|---|---|
| Identity | Kerberos preferred, LSASS protection, stricter lockout rules |
| Network | SMB signing and encryption, firewall on in every profile, legacy name resolution off |
| Cryptography | Modern TLS cipher suites, hybrid post-quantum ML-KEM key exchange |
| Remote access | RDP with NLA and TLS, WinRM without Basic or Digest |
| Code integrity | Stricter signature checks, encrypted paging file |
| Auditing | PowerShell script block logging, larger event logs |

What is not hardened yet
The gaps matter more to an administrator than the list above. Microsoft says the preview does not yet block NTLM, require Secure Boot and DMA protection, enable kernel shadow stacks, or harden printing and RPC, including Windows Protected Print.
Scoring is also incomplete. TLS cipher suites and ECC curves are not measured, and on domain controllers some settings can show as unmet even when applied. The cmdlet names may change in a later preview.
How to loosen it
Three cmdlets control the baseline. Restore-MSHardenedPolicy reverts a category, or the whole server when run without one, and Set-MSHardenedPolicy re-applies the hardened values. Get-MSHardenedPolicyCategories lists the category names.
A restored setting returns to stock Windows Server behaviour, not to whatever the machine had before. On servers managed through OSConfig or Group Policy, Microsoft warns that applying values with the in-box tools can conflict with the management tool.
The installed base is far from 2028
Lansweeper figures cited by The Register put Windows Server 2019 at 33 percent of installs and Windows Server 2025 at 7 percent as of October 2026. Esben Dochy of Lansweeper told the outlet that Microsoft indicated the hardening applies only to new installations, so existing servers would not change. Windows Server 2025 remains under extended support until 2034.
That gap is why the default matters. Microsoft's Christina Curlette, a Senior Product Manager, said Windows Server used to ship compatible by default, with securing it left to administrators. Servers still running 2019 were never hardened that way, and no setting in this preview reaches them.
The related reading is our report on CISA's Nov. 18 KEV additions, where an Apache Axis 1.x flaw has no fix at all, and the GitLab Ruby2Shell advisory, another case of unpatched software left in place.
What happens next
Microsoft has not announced a general availability date. Access is through the Windows Server Insider Program, and later preview builds are expected to add NTLM blocking and the hardware-backed protections. Test compatibility on a non-production Server Core VM before any date is set.
Sources
More in Security
- 01VicOne's 28 Robotics Zero-Days Come From a Sponsored Article With No CVE IDs and No Named ProjectsThe Tokyo security firm's count ran as paid content on IEEE Spectrum and The Robot Report. An independent March paper counted 38 flaws in three named consumer robots.
- 02Synology's Third Critical DSM Advisory in 62 Days Hits OAuth, and the Last Patch Does Not Cover ItCVE-2026-120382 scores 9.8 and needs no login. DSM 7.4 and 7.3 builds ending -2 and -6 fix it; 7.2 and 7.1 have none yet.
- 03Codex's Sandbox Uses Seatbelt, bubblewrap and MXC, and Lets Commands Read Broadly by DefaultOpenAI's Nov. 18 engineering post says writes are confined to the workspace and the network is off, while reads stay wide open.
- 04UK Tribunal Orders Home Office to Stop Hiding Apple Encryption NoticeThe Investigatory Powers Tribunal's Nov. 19 judgment confirms the order exists. What it requires of Apple stays sealed until a hearing expected in the first half of 2027.