You run the SWITCH PARTITION statement on a disk-based history table of a memory-optimized system-versioned temporal table. If you run some In-Memory online transaction processing (OLTP) workloads that update the system-versioned temporal table in parallel, a deadlock condition may occur. Additionally, the process that is running the OLTP workloads is selected as the deadlock victim.
The fix for this issue is included 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: