To fix this issue, install Cumulative Update for Windows 10 Version 1607 and Windows Server 2016: December 9, 2016 (KB3201845). Resolves a problem that occurs when you set up a new system in which the MSDTC service does not start after you apply an image and run Sysprep.

The Microsoft Distributed Transaction Coordinator (MSDTC) service may stop unexpectedly on a computer that is running Windows Server 2012 or Windows Server 2008 R2 Service Pack 1 (SP1).

Fixes an issue in which new Distributed Transactions in an Availability group database may fail after restarting the DTC service in SQL Server 2016.

Assume that you use distributed transactions in Microsoft SQL Server together with MS DTC (Distributed Transaction Coordinator). You may sometimes notice lower throughput and long wait times for the DTC_STATE wait type if there are many concurrent distributed transactions.

Creating new VMs fails for Azure Stack Hub customers. This occurs when you add a new node to a cluster. This update addresses an issue that affects certain VMs.

In some scenarios, DTC transactions involving tempdb metadata-related operations could fail internally, with an error related to transactions on memory-optimized tables not being supported in DTC scenarios.

Improvement: Microsoft Distributed Transaction Coordinator is enabled on Linux in SQL Server 2017

This article describes a conflict between Microsoft SQL Server and Microsoft Distributed Transaction Coordinator service (MSDTC) in Windows Server 2012 R2. A hotfix is available to fix this issue.

When you restart Microsoft Distributed Transaction Coordinator (MS DTC), SQL Server instances might not be able to reconnect to MS DTC successfully. Therefore, distributed transactions might fail with the error message until you restart the SQL server instances.

Improvement: Microsoft Distributed Transaction Coordinator is enabled on Linux in SQL Server 2017