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).

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.

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

Fixes an issue in which you cannot use the performance counter instance for the Distributed Transaction Coordinator performance object to monitor the performance metrics of a clustered MSDTC resource in Windows Server 2008.

Fixes a problem in which a Transaction Integrator application configured to use the "2 Phase Commit" protocol does not enlist a transaction with MS DTC in a Host Integration Server 2010 environment.

This update addresses an issue that affects the Microsoft Distributed Transaction Coordinator (DTC). It has a handle leak. Because of this, the system runs out of memory. This update addresses an issue that affects the Resultant Set of Policy (RSOP). The Windows LAPS "BackupDirectory" policy setting was not being reported.

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

Resolves an error that occurs if you use Service Broker to run a distributed query in SQL Server 2012.