Windows Server 2019, Windows Server 2022, and Azure Stack HCI: Enabled by default. Windows Server 2016 and earlier: Disabled by default. See CVE-2022-21127 for more information and this article for applicable registry key settings .

Fixes an issue in which an event ID 4227 is logged when a client application tries to connect to a Windows Server 2008 SP2-based server during a dynamic port allocation process.

To work around this issue, you can update the SQL Server 2012 RTM setup binary files by using Cumulative Update 1 for SQL Server 2012 or with a later cumulative update before you perform the installation process. To do this, use the /UpdateSource switch. For a stand-alone installation, follow these steps:

You add new Publication to the Distribution database in the AG. The collation is set to BIN or case-sensitive. In this situation, the publication may fail with an error message that resembles the following: Error 4104, Level 16, State 1, Procedure ProcedureName, Line LineNumber.

Describes an update for new component d3dcompiler_47.dll in Windows Server 2012, Windows Server 2008 R2 SP1, or Windows 7 SP1.

When a Microsoft Internet Security and Acceleration Server (ISA) 2004-based computer is operating under heavy load conditions, you may experience high CPU use. For example, CPU use on the ISA Server computer may be more than 50 percent. Cause.

You may encounter an Access Violation exception using Availability Groups (AG) in SQL Server 2017 and 2019, under the following conditions: There are large log backups of the secondary replica (The size of each log backup may be measured in few GBs).

Fixes an issue in which recycled files are deleted permanently if you delete files from a DFS link in a network environment on a client computer that is running Windows 7 or Windows Server 2008 R2 after you redirect the Recycle Bin to the DFS link.

Fixes an issue in which communication transactions between IEEE 1394-compatible devices and a computer that is running Windows 7 or Windows Server 2008 R2 are never completed. This issue occurs when the computer is not the IEEE 1394 bus manager.

If many users try to log on to or log off from the terminal server at the same time, some connection requests are denied, and then you receive the following error message: The remote procedure call failed and did not execute. For example, this issue may occur when 20 to 30 users try to log on or log off at the same time.