Updating Known issues fix information

Author: PiJoCoder

support/sql/releases/includes/patching-error-2019.md

@@ -26,5 +26,5 @@ If you want to prevent the patch from reporting an initial failure, you can perf
 
 - Remove CDC or replication from the database in the AG.
 
-A fix for this issue can be found in [SQL Server 2019, CU 29](../sqlserver-2019/cumulativeupdate29). For more information, see [CU 29, 3418490](../sqlserver-2019/cumulativeupdate29#3418490)
+A fix for this issue can be found in [SQL Server 2019, CU 29](../sqlserver-2019/cumulativeupdate29.md). For more information, see [CU 29, 3418490](../sqlserver-2019/cumulativeupdate29.md#3418490)
 

support/sql/releases/includes/patching-error-2022.md

@@ -26,4 +26,4 @@ If you want to prevent the patch from reporting an initial failure, you can perf
 
 - Remove CDC or replication from the database in the AG.
 
-A fix for this issue can be found in [CU 16](../sqlserver-2022/cumulativeupdate16). For more information, see [CU 16, 3418488](../sqlserver-2022/cumulativeupdate16#3418488)
+A fix for this issue can be found in [CU 16](../sqlserver-2022/cumulativeupdate16.md). For more information, see [CU 16, 3418488](../sqlserver-2022/cumulativeupdate16.md#3418488)

support/sql/releases/sqlserver-2019/cumulativeupdate14.md

@@ -32,11 +32,7 @@ After you install CU14, a parallel query that runs in batch mode might cause an
 
 ### Issue two
 
-SQL Server 2019 CU14 introduced a [fix to address wrong results in parallel plans returned by the built-in SESSION_CONTEXT](https://support.microsoft.com/help/5008114). However, this fix might create access violation dump files when the `SESSION` is reset for reuse. To mitigate this issue and avoid incorrect results, you can disable the original fix, and also disable the parallelism for the built-in `SESSION_CONTEXT`. To do this, use the following trace flags:
-
-- 11042 - This trace flag disables the parallelism for the built-in `SESSION_CONTEXT`.
-
-- 9432 - This trace flag disables the fix that was introduced in SQL Server 2019 CU14.
+[!INCLUDE [av-sesssion_context-2019](../includes/av-sesssion_context-2019.md)]
 
 ## Improvements and fixes included in this update
 

support/sql/releases/sqlserver-2019/cumulativeupdate28.md

@@ -55,7 +55,7 @@ App-consistent recovery point generation failed.
 
 The issue arises from a code change in SQL Server 2019 CU28 that checks if a database is online and ready to be frozen. The current solution is to roll back to SQL Server 2019 CU27 and perform the snapshot backup. For more information about how to roll back the package to a previous version, see [Uninstall a Cumulative Update from SQL Server](/sql/sql-server/install/uninstall-a-cumulative-update-from-sql-server).
 
-A fix for this issue can be found in [SQL Server 2019, CU 29](../sqlserver-2019/cumulativeupdate29). For more information, see [CU 29, 3459328](../sqlserver-2019/cumulativeupdate29#3459328)
+A fix for this issue can be found in [SQL Server 2019, CU 29](../sqlserver-2019/cumulativeupdate29.md). For more information, see [CU 29, 3459328](../sqlserver-2019/cumulativeupdate29.md#3459328)
 
 
 ## Improvements and fixes included in this update

support/sql/releases/sqlserver-2022/cumulativeupdate14.md

@@ -50,7 +50,7 @@ App-consistent recovery point generation failed.
 
 The issue arises from a code change in SQL Server 2022 CU14 that checks if a database is online and ready to be frozen. The current solution is to roll back to SQL Server 2022 CU13 and perform the snapshot backup. For more information about how to roll back the package to a previous version, see [Uninstall a Cumulative Update from SQL Server](/sql/sql-server/install/uninstall-a-cumulative-update-from-sql-server).
 
-A fix for this issue can be found in [CU 15](../sqlserver-2022/cumulativeupdate15). For more information, see [CU 15, 3459086](../sqlserver-2022/cumulativeupdate15#3459086)
+A fix for this issue can be found in [CU 15](../sqlserver-2022/cumulativeupdate15.md). For more information, see [CU 15, 3459086](../sqlserver-2022/cumulativeupdate15.md#3459086)
 
 ## Improvements and fixes included in this update