Table of contents
TOC
Collapse the table of content
Expand the table of content

Release Notes: Important Issues in Windows Server 2016

Jaime Ondrusek|Last Updated: 11/9/2016

Applies To: Windows Server 2016

These release notes summarize the most critical issues in the Windows Server® 2016 operating system, including ways to avoid or work around the issues, if known. For information about by-design changes, new features, and fixes in this release, see What's New in Windows Server 2016 and announcements from the specific feature teams. Unless otherwise specified, each reported issue applies to all editions and installation options of Windows Server 2016.

This document is continuously updated. As critical issues requiring a workaround are discovered, they are added, as are new workarounds and fixes as they become available.

Server Core installation option

When you install Windows Server 2016 by using the Server Core installation option, the print spooler is installed and starts by default even when the Print Server role is not installed.

To avoid this, after the first boot, set the print spooler to disabled.

Containers

  • Before you use containers, install Servicing stack update for Windows 10 Version 1607: August 23, 2016 or any later updates that are available. Otherwise, a number of problems can occur, including failures in building, starting, or running containers, and errors similar to "CreateProcess failed in Win32: The RPC server is unavailable."
  • The NanoServerPackage OneGet provider does not work in Windows Containers. To work around this, use Find-NanoServerPackage and Save-NanoServerPackage on a different computer (not a container) to download the needed package. Then copy the packages into the container and install them.

Device Guard

If you use virtualization-based protection of code integrity or Shielded virtual machines (that use virtualization-based protection of code integrity), you should be aware that these technologies could be incompatible with some devices and applications. You should test such configurations in your lab before enabling the features on production systems. Failure to do so could result in unexpected data loss or stop errors.

Microsoft Exchange

If you attempt to run Microsoft Exchange 2016 CU3 on Windows Server 2016, you will experience errors in the IIS host process W3WP.exe. There is no workaround at this time. You should postpone deployment of Exchange 2016 CU3 on Windows Server 2016 until a supported fix is available.

Remote Server Administration Tools (RSAT)

If you are running a version of Windows 10 older than the Anniversary Update, and are using Hyper-V and virtual machines with an enabled virtual Trusted Platform Module (including shielded virtual machines), and then install the version of RSAT provided for Windows Server 2016, attempts to start those virtual machines will fail.

To avoid this, upgrade the client computer to Windows 10 Anniversary Update (or later) prior to installing RSAT. If this has already occurred, uninstall RSAT, upgrade the client to Window 10 Anniversary Update, and then reinstall RSAT.

Shielded virtual machines

  • Ensure that you have installed all available updates before you deploy Shielded virtual machines in production.

  • If you use virtualization-based protection of code integrity or Shielded virtual machines (that use virtualization-based protection of code integrity), you should be aware that these technologies could be incompatible with some devices and applications. You should test such configurations in your lab before enabling the features on production systems. Failure to do so could result in unexpected data loss or stop errors.

Start menu

This issue affects Windows Server 2016 installed with the Server with Desktop Experience option.

If you install any applications which add shortcut items inside a folder on the Start menu, the shortcuts will not work until you log out and log back in again.

Go back to the main Windows Server 2016 hub.

This document is provided "as-is". Information and views expressed in this document, including URL and other Internet Web site references, may change without notice.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

© 2016 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Hyper-V, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

This product contains graphics filter software; this software is based in part on the work of the Independent JPEG Group.

1.0

© 2017 Microsoft