Windows Server 2019 testers can get their hands on a fresh new build today. Microsoft has shipped out build 17744, bringing along several Hyper-V improvements and new features. But while the new features and fixes may grab most of your attention, there's also a healthy list of known issues to be aware of.
- Installation no longer prompts for a product key. Microsoft Hyper-V Server is an enterprise hypervisor that is provided at no additional cost.
- Administrators are now properly prompted to change their passwords when initially signing in.
- Updated installation branding.
- Failover Clustering hardening. Failover Clustering no longer requires the use of NTLM.
- Server Message Block (SMB) hardening. SMB 1.0 is disabled by default.
- Windows Subsystem for Linux is built in.
- Windows Defender Advanced Threat Protection is built in.
- .NET Framework 4.7 is built-in. (Microsoft Hyper-V Server 2016 included .NET Framework 4.6).
- Finally, Microsoft Hyper-V Server can be fully managed by Windows Admin Center to provide a modern, remote management solution that integrates with Azure Backup, disaster recovery, and more.
- [NEW] After a system running Server Core is transitioned (transmogrified) to Server Datacenter–for example, by running the command dism /online /setedition:ServerDatacenterCor /ProductKey:product-key/AcceptEula–the operating system is not licensed. On an affected system, the administrator is not instructed to restart the system, and the operating system indicates that it is a retail channel version rather than a Generic Volume License Key (GVLK) version, even when the product key is a GVLK key. To make an affected system licensed, run the following command: cscript c:\Windows\System32\slmgr.vbs /ipkproduct-key.
- [NEW] The Italian language (it-IT) text of the End-User License Agreement (EULA) for Hyper-V Server is formatted incorrectly.
- The operating system has an unnecessary utility account for Windows Defender Application Guard.
- Authentication that uses Public Key Cryptography User-to-User (PKU2U) to access an SMB volume can result in an error, STATUS_LOGON_FAILURE, due to an invalid private key in the certificate for a cluster-created user account (CSUSR) on each cluster node. This issue can cause cross-cluster migration in cluster sets to fail, as well as possibly cause global namespace mappings to fail, leading to virtual machines being unable to access storage.
- The Base Filtering Engine service may consume an inordinate amount of memory after starting and stopping thousands of containers.
- The Virtual Hard Disk Miniport Driver (Vhdmp.sys) may experience a bug check, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e).
- When a Windows Defender Application Guard container crashes, the resulting type of dump may be unexpected.
- On recent preview builds, database applications might not be able to initialize a database and fail with a stack overflow or insufficient privileges when the database is located on an SMB volume.
- Shielded VMs running Linux do not boot. The loader (LSVMLoad) waits for a passphrase for the boot partition.
- Creating or modifying environment variables by using setx fails on a system running in a Nano Container (that is, Nano Server as a container image). On an affected system, setx requires a specific path in the registry, HKCU\Environment\, to exist by default. You can work around this issue by changing where the variable is stored in the registry, or you can add the expected registry path before executing setx commands. To specify that the variable be set for system-wide use in HKLM rather than in HKCU, the default, add the /M switch to a setx command. To instead add the expected registry path, run reg add HKCU\Environment before executing setx commands.
Windows Server preview build 17744 is available to download now via Microsoft. The build is set to expire on December 14, 2018.
We may earn a commission for purchases using our links. Learn more.