Assume that you configure an Extended Event session that monitors the Latch_Suspend_End event in Microsoft SQL Server 2016. When a worker thread is aborted or receives an abort attention, the Latch_Suspend_End event is incorrectly triggered while a latch is obtained successfully. This causes a latch leakage assertion. Additionally, SQL Server stops responding.
The fix for this problem is included in the following updates:
Each new build for SQL Server 2016 contains all the hotfixes and all the security fixes that were included with the previous build. We recommend that you install the latest build for SQL Server 2016.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology Microsoft uses to describe software updates.