Windows Server 2019 build 17677

Windows Server 2019 build 17677 is the fifth Insider Preview build of Windows Server 2019. It was released on 29 May 2018.

New features and changes

 * This build now starts to include the "Windows Server 2019" branding, as opposed to just "Windows Server".
 * Improvements to the performance history feature of Storage Spaces Direct. These include the  gaining self-diagnostic logic. If the cmdlet finds nothing to report, it now looks for common issues that would prevent performance history from working properly (for example, if its storage is missing) so that the cmdlet can provide improved error text, as well as two new cmdlets (  and   that are new to this build. These new cmdlets make it easier to solve issues with the performance history by cleaning up and/or re-provisioning the performance history. This build also adds some new series to record how much Storage Spaces Direct data needs to repair or resync per server.
 * Improvements to Windows Server Core, to reduce the image size, non-critical font components into optional components in the Core SKUs, and removed the fonts from the Server Core container image. Users have the ability to enable or disable non-critical font components, while for Server Core container images, only the Arial font is supported.

Bugs

 * Active Directory domain controllers may not upgrade correctly during an in-place OS upgrade, unless the NT Directory Service is stopped before initiating the upgrade.
 * The Failover Clustering feature may not install correctly, leaving it stuck at a "Pending" state as a result.
 * Some network adapter drivers from specific manufacturer may not work on this build.
 * In the Nano SKU, creating or modifying environment variables by using  will fail. This is because   requires the   to be present by default.
 * The Local Security Authority Subsystem Service may randomly crash, which in turn causes the Active Directory server service to fail. When a domain removal is attempted on an affected system, it gives out an error that says: "The operation cannot continue because LDAP connect/bind operation failed."
 * The Virtual Machine Management Service (VMMS) may randomly error out with an  in Cluster Manager.
 * Windows Server Containers may experience an idle time of 240 milliseconds before Docker is started.
 * Virtual Machines that use the Microsoft Virtual BIOS may not start and instead report an error that states “Failed to restore with Error ‘Indicates two revision levels are incompatible.’ (0x8007051A)”
 * Creation of a basic Linux system image in a Hyper-V container will fail. Docker reports an error that states “The command ‘ ’ returned a non-zero code.”
 * Some third-party apps don't start when run in a Hyper-V container, possibly due to an incorrect character set. A workaround is to manually set the character set to UTF-8 in the JVM for the container by running.
 * If you create or edit a policy for AppLocker, the associated MMC snap-in can crash when generated rules for a packaged app.
 * After an upgrade, the AppX database may have corrupted entries, which can cause problems for components that use said entries. This results in problems such as when a user tries to generate packaged app rules or when they try to manage an installed package. Doing such actions on affected machines will result in errors saying that “This wizard has encountered a fatal error and cannot continue” and “MMC has detected an error in a snap-in and will unload it.”