Windows Server build 18317

Windows Server build 18317 is a build of Windows Server version 1903. It was released on 22 January 2019 to Windows Insiders.

New features and changes

 * Windows Defender Application Control (WDAC) brings users the ability to support multiple code integrity policies. This build brings three new scenarios, which are detailed in the official announcement.

Bugs

 * Dynamic Update setup shows "Installing Windows 10" instead of Server.
 * Scheduled startup tasks may not run. If this occurs, the system logs an event, which is ID 101 with the error code.
 * Virtual machines may not report all virtual fibre channel (VFC) LUNs after starting them if there are over 2000 VFC LUNs. WMI queries from the host show the LUNs as available. Restarting the VMs may show the LUNS again as available.
 * DCPromo will fail if the interface metric of the physical NIC is larger than the loopback interface.
 * ADFS requests with invalid domain suffixes fail after a 3 minute delay with the error . This bug can cause queued legitimate requests to experience delays or also timeout.
 * Server FODs aren't retained after upgrades, regardless if it's an in-place or build-to-build upgrade.
 * If a domain controller is renamed, the system does so, but it updates incorrect attributes in AD, leaving orphaned data behind . This bug can be reproduced by adding a new FQDN, setting that as primary, restarting the domain controller, then removing the current FQDN. Checking the,   and the   attributes will show incorrect values.
 * An invalid file may be created in  by the User Access Logging service.
 * The operating system may attempt to reuse an expired DHCP lease if the lease expired while the OS was shutdown.
 * Self-service users can't install Feature on Demand and Language Pack packages for Windows Server Update Service (WSUS), System Center Configuration Manager (SCCM), and Autopilot scenarios.
 * Container hosts can become unresponsive due to a deadlock when attempting to mount a volume. If this happens, Docker will hang on all commands.
 * An unnecessary utility account for Windows Defender Application Guard is present.
 * When a Windows Defender Application Guard container crashes, the resulting type of dump may be unexpected.
 * Server FODs aren't retained after upgrades, regardless if it's an in-place or build-to-build upgrade.
 * The CPU usage may spike if the operating system logs obsolete Windows Error Reporting reports  and.