Windows Server build 18356

Windows Server build 18356 is a build of Windows Server version 1903. It was released on 19 March 2019 to Windows Insiders.

Bugs

 * This build will get stuck at bootup if you're using VMware Workstation. To fix this, paste the following three lines in the VM's  file:


 * You will encounter an error after remoting to a machine with RDP post FoD installation. The error message indicates immediately that the remote session has ended with potential reasons, followed by a black screen. This bug only affects remoting to a physical machine with Server Core + FOD.
 * (This bug only impacts the  found in the 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.
 * A local user's last logon time output from the  command may not be recorded even when the user has accessed the server’s network share.
 * 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.
 * Third-party password filter DLLs may not be notified when the local administrator account’s password was changed.
 * Attempting to do a system image recovery from an image located on a network share may result in the error “A specified logon session does not exist. It may already have been terminated”.
 * 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.
 * 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.
 * When a Windows Defender Application Guard container crashes, the resulting type of dump may be unexpected.