Windows Server 2019 build 17738

Windows Server 2019 build 17738 is the eleventh Insider Preview build of Windows Server 2019. It was released on 21 August 2018.

New features and changes

 * Added the capability to assign simple buses to process-isolated Windows Server containers. Applications running in containers that need to talk over SPI, I2C, GPIO, and UART/COM will now be able to do so.
 * Added support for Software Defined Network (SDN) high performance gateways.

Bugs

 * Notepad may crash or display an empty pane when a user selects the Open command on the File menu.
 * Authentication that uses Public Key Cryptography User-to-User (PKU2U) to access an SMB volume can result in the error . This is due to an invalid private key in the certificate for a cluster-created user account (CSUSR) on each of the cluster nodes. It can cause cross-cluster migration in cluster sets to fail, as well as possibly cause global namespace mappings to fail, which in turn leads to virtual machines being unable to access storage.
 * The Base Filtering Engine service may consume an unusually large amount of memory after starting and stopping thousands of containers.
 * The operating system has an unnecessary utility account for Windows Defender Application Guard.
 * The system may crash with a  blue screen of death in the Virtual Hard Disk Miniport Driver.
 * When a Windows Defender Application Guard container crashes, the resulting type of dump may be unexpected.
 * On a preview build of the operating system, Narrator is not available by default after installation. On an affected system, the audio service is also disabled by default.
 * 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.
 * Shielded VMs running Linux do not boot because the loader (LSVMLoad) waits for a passphrase for the boot partition.
 * In the Nano SKU, creating or modifying environment variables by using  will fail. This is because   requires the   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   command. To specify that the variable be set for system-wide use in HKLM rather than in HKCU, which is the default, add the   switch to a   command. To add the expected registry path, run   before executing a setx command.