Windows Server 2019 build 17723

10.0.17723.1000.rs5_release.180720-1452
	Build of Windows Server 2019
OS family	Windows 10 (NT 10.0)
Version number	10.0
Build number	17723
Build revision	1000
Architecture	x64
Build lab	rs5_release
Compiled on	2018-07-20
Expiration date
Timebomb	2018-12-14 (+147 days)
SKUs
	Standard Server; Standard Server Core; Datacenter Server; Datacenter Server Core; Hyper-V Server
About dialog

Windows Server 2019 build 17723 is the ninth Insider Preview build of Windows Server 2019. It was released on 31 July 2018.

New features and changes[edit | edit source]

You can now add new predictive capabilities to System Insights without the need to install any OS updates. Some new capabilities were added to System Insights as well. These include some new capabilities to specify any performance counter or ETW event, which will be collected, persisted locally, and returned to the capability for analysis when the capability is invoked, as well as some new ones to leverage the existing Windows Admin Center and PowerShell management planes. These new capabilities are discoverable in System Insights, and can be customized with custom schedules and remediation actions.
You can deploy Kubernetes-made Containers. Features include scheduling, when it is given a container image and a resource request, it can find a suitable machine on which to run the container, Health monitoring, which enables users to watch for container failures and to automatically reschedule them, Networking, which can provide a network for coordinating containers to communicate across machines, service discovery, which enables containers to locate each other automatically even as they switch hosts or change IP addresses, and scaling, which allows you to add or remove container instances to match demand, either manually or automatically.
Added a new feature called "LEDBAT" (Latency Optimized Background Transport), which uses whatever network bandwidth is available on the network, and uses it

Bugs[edit | edit source]

On the Nano Server SKU, copying a file from an SMB volume in a container to local storage will fail.
A specific distributed search and analytics engine may by denied access when it queries C:\Windows\temp as ContainerUser. To fix this bug, set the paths for temporary folders to another location by executing setx /M TEMP “c:\sample” setx /M TEMP “c:\sample”.
A Multi-Resilient Volume (MRV) may fail to mount during node maintenance for a software-defined datacenter (SDDC) cluster, which causes virtual machines to go offline.
Services.exe should not launch Upfc.exe when the system starts if it's running inside a container.
Database applications might not be able to initialize a database and fail with either a stack overflow or insufficient privileges error when the database is located on an SMB volume.
Virtual machines can randomly crash with exit reason 3, and they migrate repeatedly every few minutes.
The operating system may fail to detect a specific family of RAID controllers.
Shielded VMs running Linux do not boot because the loader (LSVMLoad) waits for a passphrase for the boot partition.
Draining a node may fail with an error stating “Cannot create a file when that file already exists. (0x800700b7).”
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.