When a user session is killed in Microsoft SQL Server, it remains in a rollback state indefinitely until SQL Server is restarted. The user session might be also stuck while it waits for TRANSACTION_MUTEX or XACT_OWN_TRANSACTION waits.
This problem can occur if there is an XEvent session for sql_transaction events that has a sql_text action and a like_i_sql_unicode_string predicate for the sql_text action. When a user session is killed, its ongoing transaction goes through a rollback process. The user session may encounter an abort error because of the XEvent action and predicate. This leaves the transaction in the rollback state indefinitely.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem is fixed in the following cumulative update for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Learn about the terminology that Microsoft uses to describe software updates.