You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/sql-server/sql-server-2025-release-notes.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Find information about SQL Server 2025 (17.x) limitations, known is
4
4
author: MikeRayMSFT
5
5
ms.author: mikeray
6
6
ms.reviewer: randolphwest
7
-
ms.date: 06/19/2025
7
+
ms.date: 06/26/2025
8
8
ms.service: sql
9
9
ms.subservice: release-landing
10
10
ms.topic: release-notes
@@ -27,13 +27,13 @@ For hardware and software requirements, see [Hardware and software requirements
27
27
28
28
## Known issues
29
29
30
-
### SQL Server on Windows fails to start after installation
30
+
### SQL Server on Windows fails to start on machines with more than 64 logical cores per NUMA node
31
31
32
32
**Issue**: SQL Server instances on Windows might fail to start after the installation if the machine has more than 64 logical cores per NUMA node.
33
33
34
34
For more information, see [Limit number of logical cores per NUMA node to 64](compute-capacity-limits-by-edition-of-sql-server.md#limit-number-of-logical-cores-per-numa-node-to-64).
35
35
36
-
### SQL Server on Linux fails to start after installation
36
+
### SQL Server on Linux fails to start on machines with hybrid CPU architecture
37
37
38
38
**Issue**: SQL Server instances on Linux might fail to start if the machine uses an Intel 12th Gen or later hybrid architecture CPU, and the host operating system is Linux.
If you want to use a Linux host operating system, you can work around the issue by disabling efficiency cores (E-cores) in your BIOS. If you use containers, or a hypervisor like Hyper-V on Windows (including WSL), you aren't affected.
47
47
48
+
### SQL Server fails to start if AVX2 CPU instructions aren't available
49
+
50
+
**Issue**: In CTP 2.1 (version 2025.170.800.3), SQL Server doesn't start if AVX2 CPU instructions aren't available on the machine.
51
+
52
+
In the Windows application event log, you see an **Error** event referencing exception code `0xc000001d` and a faulting module path that includes `sqllang.dll`.
53
+
54
+
To work around this issue, enable AVX2 CPU instructions on the machine. AVX instructions might be disabled in the machine BIOS or UEFI, or disabled in the hypervisor configuration. If SQL Server setup failed because of this issue, uninstall and reinstall SQL Server once AVX2 instructions are enabled.
55
+
48
56
### Upgrade in place
49
57
50
58
[!INCLUDE [sssql25-md](../includes/sssql25-md.md)] doesn't support in place upgrades from previous versions of [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], including SQL Server 2025 CTP releases.
0 commit comments