You use automatic seeding for the secondary replica of an AlwaysOn Availability Group in Microsoft SQL Server. You back up a database [db1], you add files [f1] and [f2], and then you remove backup file [f1].

SQL Server Management Studio runs a query against the backupset table when you to try to expand the Databases node in SQL Server Management Studio. The fix for this issue was first released in Cumulative Update 3.

Fixes an issue in which automatic seeding fails when you use an Always On availability group in SQL Server.

Assume that you use the SqlLocalDB feature in Microsoft SQL Server 2019 or 2017. In this situation, you can't start correctly or connect to a shared instance of SqlLocalDB. This problem is fixed in the following cumulative updates for SQL Server:

Provides guidance for installing a DBX update to fix a vulnerability that exists in some Secure Boot modules if they trust the Microsoft third-party UEFI CA.

To help keep Windows devices secure, Microsoft adds vulnerable bootloader modules to the Secure Boot DBX revocation list (maintained in the system UEFI-based firmware) to invalidate the vulnerable modules.

Fixes an issue in which you receive illegal name character error when you parse the module_end event output in SQL Server 2014.

Provides guidance for installing a DBX update to fix a vulnerability that exists in some Secure Boot modules if they trust the Microsoft third-party UEFI CA.

After you install an update for Microsoft Exchange Server 2019, you may get incomplete results when you search for items in a mailbox. During each Exchange Server upgrade, the Microsoft Search Foundation is reinstalled.

Microsoft .NET Framework security updates support different command-line switches. Which switches are supported depends on the chain installer that is used to build the update package.