Windows Server: 17738

A new build of the Windows Server vNext LTSC has been released with build 17738. Make sure to check the known issues before installing. Also, I believe the old adage “everything can be production if you’re brave enough” doesn’t apply to these builds!

Known Issues

  • [NEW] Notepad may crash or display an empty pane when a user selects File > Open.
  • [NEW] 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.
  • [NEW] The Base Filtering Engine service may consume an inordinate amount of memory after starting and stopping thousands of containers.
  • [NEW] The operating system has an unnecessary utility account for Windows Defender Application Guard.
  • 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 a preview build of the operating system, Narrator is not available by default after installation. On an affected system, the audio service is disabled by default.
  • 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.