Windows Server 2019 build 17709 (rs prerelease)

10.0.17709.1000.rs_prerelease.180629-1430
	Build of Windows Server 2019
OS family	Windows 10 (NT 10.0)
Version number	10.0
Build number	17709
Build revision	1000
Architecture	x64
Build lab	rs_prerelease
Compiled on	2018-06-29
Expiration date
Timebomb	2018-12-14 (+168 days)
SKUs
	Standard Server; Standard Server Core; Datacenter Server; Datacenter Server Core; Hyper-V Server
About dialog

Windows Server 2019 build 17709 (rs_prerelease) is the seventh Insider Preview build of Windows Server 2019. It was released on 10 July 2018.

New features and changes[edit | edit source]

Improved the scalability and reliability of containers that use group managed service accounts (gMSA) to access network resources. You no longer have to set the container's host name to be identical to the gMSA. A bug was also fixed that prevented you from using gMSAs with Hyper-V isolated containers.
Added a new base image to the Windows Server container collection. This image carries more components than the Nano Server and Server Core images. This means it can support applications that have additional API dependencies.
You can now upgrade from a previous build of Windows Server 2019 to another build of the operating system.

If a server is upgraded from build 17692 to this build, System Insights encounters errors when parsing or visualizing the prediction results.
The PowerShell cmdlet Get-HgsAttestationBaselinePolicy, which is the cmdlet that generates an attestation baseline policy, will fail with the error “Failed to retrieve TPM information.”
On the Server Core SKUs of this build, the Advanced Query Syntax (AQS) parser may fail if the default language and locale are changed to something other than US English. This results in search functionality in Exchange to not work.
In the Nano SKU, creating or modifying environment variables by using setx will fail. This is because setx requires the HKCU\Environment\ to be present by default. To fix this issue, change where this variable is stored in the registry, or add the expected registry path before you execute a setx command. To specify that the variable be set for system-wide use in HKLM rather than in HKCU, which is the default, add the /M switch to a setx command. To add the expected registry path, run reg add HKCU\Environment before executing a setx command.
The Virtual Machine Management Service (VMMS) may randomly error out with an APPLICATION_FAULT_INVALID_POINTER_READ in Cluster Manager.
If you create or edit a policy for AppLocker, the associated MMC snap-in can crash when generated rules for a packaged app.