Windows Server build 18917

Windows Server build 18917 is a build of Windows Server, version 2004. It was released on 18 June 2019 to Windows Insiders.

Changes

 * Bug fixes listed in the official release announcement.

Bugs

 * Using  to move Active Directory files may fail with the error message "“Move file failed with source   and Destination   with error 5 (Access is denied.)”.
 * Auto-logons that are configured by login scripts do not work properly.
 * The status of the online/offline files icon and status bar may not display an accurate status. The OfflineFiles event manager logs will show the actual state of the files.
 * PowerShell may report an incorrect  result on an IPoIB adapter.
 * (This bug only impacts the  found in the Application Compability Feature on Demand package set) Multiple instances of the Active Directory Users and Computers snap-in added to the same   instance could show inconsistent or no data on part of the snap-ins after adding extra columns to the UI view. The workaround is to use a separate MMC session for each ADUC  snap-in.
 * Scheduled startup tasks may not run. If this occurs, the system logs an event, which is ID 101 with the error code.
 * DCPromo will fail if the interface metric of the physical NIC is larger than the loopback interface.
 * 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.
 * 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.
 * After disabling and re-enabling SR-IOV capability on a Linux VM, Windows may report the error "Error applying Network Adapter changes.” Analyzing the details will show “The Hyper-V Virtual Machine Management service encountered an unexpected error: Call was canceled by the message filter. (0x80010002).” Because of this error, the VM will remain in a stopping state when shutting it down, thus making it impossible to shut the VM down until the computer is restarted.
 * When deploying a controller VM, after the last reboot in the deployment process, the controller VM is not visible.