Windows Server 2019 build 17692

Windows Server 2019 build 17692 is the sixth Insider Preview build of Windows Server 2019. It was released on 19 June 2018. It is also the first Insider Preview build of Windows Server 2019 to include the Hyper-V Server SKU.

New features and changes

 * The Windows Server 2019 branding is now included at the start of Setup, as well as in.
 * Introduced System Insights. This feature aims to bring local predictive analytics capabilities natively to the operating system. Each of these predictive capabilities is backed by a machine-learning model to locally analyze Windows Server system data, such as performance counters and events, which helps to provide an insight into the user's deployments and helping them reduce the operational expenses associated with monitoring their Windows Server instances. Because each of these capabilities runs locally, all of their data is collected, persisted, and analyzed directly on their Windows Server machine, which allows them to use predictive analytics capabilities without any cloud connectivity. The interface of this feature includes capabilities focused on capacity forecasting, predicting future usage for compute, networking, and storage. It can be managed by an extension in Windows Admin Center or directly via PowerShell. Custom schemes can be created to run each capability and remediation scripts can be created to automatically address any issue detected by a capability.

Bugs

 * If a server is upgraded from an older operating system, administrator credentials do not work. As a result, administrator accounts are not accessible, and using administrator credentials won't work for the elevation of privilege.
 * Event Viewer can become unresponsive when you try to view the details of an event if App Compatibility, a Feature on Demand (FoD), is installed on the system. To workaround this issue, close Microsoft Management Console via Task Manager.
 * Docker commands may fail when run on a Windows Server container. After a Docker command has failed on an affected system, subsequent Docker commands will also fail as well.
 * In the Nano SKU, creating or modifying environment variables by using  will fail. This is because   requires the   to be present by default.
 * The Virtual Machine Management Service (VMMS) may randomly error out with an  in Cluster Manager.
 * 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)”
 * If you create or edit a policy for AppLocker, the associated MMC snap-in can crash when generated rules for a packaged app.