I cannot install the SQL Server 2022 Developer Edition

Question

I cannot install the SQL Server 2022 Developer Edition (x64) on windows 11 i tried alot of things even setup a new windows i get this error code 0x84B40002 and it says The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured this is the error log file 2025-03-10 17:23:41.48 Server Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64)

Oct  8 2022 05:58:25 

Copyright (C) 2022 Microsoft Corporation

Developer Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22631: ) (Hypervisor)
```2025-03-10 17:23:41.48 Server      UTC adjustment: 2:00

2025-03-10 17:23:41.48 Server      (c) Microsoft Corporation.

2025-03-10 17:23:41.48 Server      All rights reserved.

2025-03-10 17:23:41.48 Server      Server process ID is 15756.

2025-03-10 17:23:41.48 Server      System Manufacturer: 'LENOVO', System Model: '82K2'.

2025-03-10 17:23:41.48 Server      Authentication mode is MIXED.

2025-03-10 17:23:41.48 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Log\ERRORLOG'.

2025-03-10 17:23:41.48 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.

2025-03-10 17:23:41.48 Server      Registry startup parameters: 

```powershell
 -d C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\master.mdf

 -e C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Log\ERRORLOG

 -l C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
```2025-03-10 17:23:41.48 Server      Command Line Startup Parameters:

-s "MSSQLSERVER"

2025-03-10 17:23:41.49 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2025-03-10 17:23:41.49 Server      Detected 14188 MB of RAM. This is an informational message; no user action is required.

2025-03-10 17:23:41.49 Server      Using conventional memory in the memory manager.

2025-03-10 17:23:41.49 Server      Detected pause instruction latency: 33 cycles.

2025-03-10 17:23:41.49 Server      Page exclusion bitmap is enabled.

2025-03-10 17:23:41.64 Server      Buffer Pool: Allocating 2097152 bytes for 1604602 hashPages.

2025-03-10 17:23:41.66 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)

2025-03-10 17:23:41.70 Server      Buffer pool extension is already disabled. No action is necessary.

2025-03-10 17:23:41.74 Server      CPU vectorization level(s) detected:  SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2

2025-03-10 17:23:41.76 Server      Query Store settings initialized with enabled = 1, 

2025-03-10 17:23:41.77 Server      The maximum number of dedicated administrator connections for this instance is '1'

2025-03-10 17:23:41.77 Server      This instance of SQL Server last reported using a process ID of 17136 at 3/10/2025 5:09:03 PM (local) 3/10/2025 3:09:03 PM (UTC). This is an informational message only; no user action is required.

2025-03-10 17:23:41.78 Server      Node configuration: node 0: CPU mask: 0x0000000000000fff:0 Active CPU mask: 0x0000000000000fff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2025-03-10 17:23:41.78 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.

2025-03-10 17:23:41.85 Server      In-Memory OLTP initialized on standard machine.

2025-03-10 17:23:41.86 Server      [INFO] Created Extended Events session 'hkenginexesession'

2025-03-10 17:23:41.86 Server      Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.

2025-03-10 17:23:41.87 Server      Total Log Writer threads: 2, Node CPUs: 6, Nodes: 1, Log Writer threads per CPU: 1, Log Writer threads per Node: 2

2025-03-10 17:23:41.88 Server      clwb is selected for pmem flush operation.

2025-03-10 17:23:41.89 spid34s     Starting up database 'master'.

2025-03-10 17:23:41.89 Server      Software Usage Metrics is disabled.

2025-03-10 17:23:41.89 Server      CLR version v4.0.30319 loaded.

2025-03-10 17:23:41.90 spid34s     There have been 256 misaligned log IOs which required falling back to synchronous IO.  The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\master.mdf.

2025-03-10 17:23:41.90 spid34s     Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)

2025-03-10 17:23:41.90 spid34s     Stack Signature for the dump is 0x0000000000000000

2025-03-10 17:23:41.90 spid34s     CDmpClient::ExecuteAllCallbacks started.

2025-03-10 17:23:41.90 spid34s     XE_DumpCallbacks is executing...

2025-03-10 17:23:41.92 spid34s     DumpCallbackSOS is executing...

2025-03-10 17:23:41.92 spid34s     DumpCallbackEE is executing...

2025-03-10 17:23:41.92 spid34s     DumpCallbackSE is executing...

2025-03-10 17:23:41.92 spid34s     DumpCallbackSEAM is executing...

2025-03-10 17:23:41.92 spid34s     DumpCallbackSSB is executing...

2025-03-10 17:23:41.94 spid34s     DumpCallbackQE is executing...

2025-03-10 17:23:41.94 spid34s     DumpCallbackFullText is executing...

2025-03-10 17:23:41.94 spid34s     DumpCallbackSQLCLR is executing...

2025-03-10 17:23:41.94 spid34s     DumpCallbackHk is executing...

2025-03-10 17:23:41.95 spid34s     DumpCallbackRepl is executing...

2025-03-10 17:23:41.95 spid34s     DumpCallbackPolyBase is executing...

2025-03-10 17:23:41.95 spid34s     CDmpClient::ExecuteAllCallbacks completed. Time elapsed: 0 seconds.

2025-03-10 17:23:42.66 spid34s     External dump process return code 0x20000001.

External dump process returned no errors.

Answer 1

You are running into a known issue where Windows 11 for some disk drives reports a sector size that SQL Server does not cope with. Microsoft has published an article with workarounds for the problem.