Windows Server Insider Preview Build 17093 released
Posted on: 02/14/2018 09:15 AM

Microsoft has released Windows Server Insider Preview Build 17093

Windows Server Insider Preview Build 17093 released

Today we are releasing Windows Server Insider Preview Build 17093 to Windows Server Insiders. This build is a preview build of the next Semi-Annual Channel release of Windows Server. For more information on the Semi-Annual channel, please see the Windows Server Semi-Annual Channel overview. Also available is Project Honolulu Technical Preview 1802.

What’s New in Build 17093 for Windows Server
There are no new features in this build.

Known issues with Windows Server Build 17093
On builds 17088 and higher, after Server Core OS installation, the user is requested to set the password – when the user does so, an error message is presented “The remote procedure call failed”. The install will still accept the password as expected.
Upgrading a system to a preview build, starting with build 17088, may stall at 88% for 45 or more minutes before eventually being completed due to loading registry hives for each driver.
When BitLocker is enabled and a system is started, the system prompts the user for the BitLocker PIN. Upon providing the correct PIN the first time, the system says the PIN is incorrect; however, if the user presses Enter a second time, the PIN is accepted.
In‑place OS upgrade: BitLocker. Before performing an in-place OS upgrade, suspend (disable) BitLocker protection on any drives on the system. After the upgrade is complete, resume (re-enable) BitLocker protection.
In-place OS upgrade: Domain Controllers. During an in-place OS upgrade, Active Directory (AD) Domain Controllers (DC) might not be upgraded correctly. Back up any AD DCs before performing an in-place OS upgrade.
Using container images from Windows Insider Program on a Windows Server Core host will fail, and may crash the host. As a workaround, you can add isolation=hyperv when running or building the containers; for example: docker run -isolation=hyperv microsoft/nanoserver-insider.
When Hypervisor Code Integrity (HVCI) is enabled, a system may fail to start. On affected systems, firmware locates UEFI runtime services in memory described as Memory-Mapped I/O (MMIO).
Testing of the Windows core may fail because of a timeout while attempting to load the test libraries.

Printed from NT Compatible (