SQL Server 2022 Database Engine Recovery Handle Failed on Clean Windows 11 Installation

Question

SQL Server 2022 Database Engine Recovery Handle Failed on Clean Windows 11 Installation

Kiara Keys 0

Hello,

I am unable to install SQL Server 2022 (Express and Developer) on my Windows 11 Home laptop. Every installation fails with the following error:

Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.

System Information

Windows 11 Home 64-bit
Version: 25H2
OS Build: 26200.8973
HP Pavilion x360 14-ek0xxx
Intel Core i5-1235U
8 GB RAM
Approximately 365 GB free disk space

Troubleshooting Already Performed

Performed a Windows reset.
Removed all SQL Server installations using the SQL uninstaller and Revo Uninstaller.
Deleted remaining SQL Server folders.
Removed McAfee LiveSafe completely.
Ran sfc /scannow (no integrity violations found).
Verified sufficient disk space and memory.
Confirmed the SQL Server service is created but immediately terminates.
Event Viewer shows SQL Server setup failures, but no clear file permission errors.
SQL Server ERRORLOG reaches:
- "Starting up database 'master'"
  - followed immediately by server termination.
  - No "Access denied" or missing database file errors appear in the logs.

Additional Information

Earlier attempts left duplicate SQL Server MSI registrations, but after cleaning and resetting Windows, the installation still fails with the exact same Database Engine recovery error.

The SQL Server service (MSSQL$SQLEXPRESS) terminates immediately during startup.

Request

Could you advise what would cause the SQL Server Database Engine to terminate immediately after starting the master database on a clean Windows installation?

If there are specific diagnostic logs or crash dumps you would like me to collect, I can provide them.

Thank you.

0 comments

4 answers

Your answer

Answer 1

The gist of this error message is that SQL Server did not start when Setup wanted to run post-configuration. There can be multiple reasons for this. The by far most common reason is a known issue where Windows reports a disk sector size that SQL Server is not able to cope with. To verify that you are victim to this problem, you should look in the SQL Server error log which you find in C:\Program Files\Microsoft SQL Server\MSSQL17.SQLEXPRESS\MSSQL\LOG\ERRORLOG and look for a message that talks about 256 misaligned log IOs.

Microsoft has published the article Troubleshoot SQL Server errors related to system disk sector size greater than 4 KB which discusses workarounds for this problem. Basically, you need to make the registry edit described in the article. Very important! You need to reboot Windows for the change to take effect.

If you don't find the message about 256 misaligned log IOs, please upload the ERRORLOG so that we can take a look. (You will need to rename it to ERRORLOG.txt for the forum software to accept it.)

Answer 2

Senthil kumar 1,725

Hi @Kiara Keys

First check your logs

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

finally try with minimal mode :

Start SQL in minimal mode: Code
```
   NET START MSSQLSERVER /f
```

Reset TempDB location: sql

   ALTER DATABASE tempdb MODIFY FILE (NAME='tempdev', FILENAME='C:\tempdb\tempdb.mdf');

ALTER DATABASE tempdb MODIFY FILE (NAME='templog', FILENAME='C:\tempdb\templog.ldf');

   
1. Restart SQL normally.

some where your existing DB struct that is the issue. 

Thanks.

0 comments

Answer 3

Deepesh Dhake 820

The quickest way to find the real cause is to run the failed instance in console mode from an elevated command prompt, which prints the actual error to the screen:

cd "C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Binn" sqlservr.exe -c -s SQLEXPRESS

If the install rolled back and those binaries aren't there, the setup logs will have it instead:

C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\Summary.txt

along with the newest ERRORLOG in that timestamped folder.

0 comments

Answer 4

Wait on the Database Engine recovery handle failed is a generic setup symptom. It means SQL Server did not start successfully when Setup tried to run configuration steps. The immediate cause must be identified from the SQL Server ERRORLOG.

Given the Windows 11 laptop scenario and the fact that the service starts, reaches Starting up database 'master', and then terminates, the most likely cause in the provided guidance is the known Windows 11 disk sector size issue affecting some storage devices. In that case, the SQL Server error log typically contains a message like:

There have been 256 misaligned log IOs which required falling back to synchronous IO.

That issue is documented for SQL Server on Windows 11, including cases where SQL Server was installed on Windows 10 and then the machine was upgraded to Windows 11, and it is also called out in similar installation failures on Windows 11. Windows 11 native NVMe drivers can report the actual physical sector size from the device, and some devices report 8 KB or 16 KB instead of the 4 KB sector size SQL Server expects.

Actionable next step:

Open the SQL Server ERRORLOG for the failed instance.
- For SQL Server 2022 Express default instance, similar cases use: C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\LOG\ERRORLOG
- For a default non-Express instance, similar cases use: C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\LOG\ERRORLOG
Search the log for:
- 256 misaligned log IOs
- misaligned
- sector-size related messages
If that message is present, the failure matches the known Windows 11 storage-sector-size problem, and the documented workarounds in the sector-size troubleshooting article are the relevant path.
If that message is not present, then this specific known cause is not confirmed. In that case, the next supported conclusion is that Wait on the Database Engine recovery handle failed is still only a wrapper error, and the lines immediately before shutdown in ERRORLOG are required to determine the real cause.

Other supported causes for the same generic setup failure include:

T-SQL upgrade script failures during cumulative update installation, often associated with SQL Server errors 912 and 3417.
Missing Windows Installer cache files under C:\Windows\Installer, which can block repair or update operations.
Corrupted or incomplete setup media, where the documented fixes include downloading the SQL Server image again, installing from a local drive instead of a network location, or renaming Setup.rll and rerunning Setup.

Because this is a clean installation scenario rather than a CU/SP patching scenario, the most relevant documented cause from the available material is the Windows 11 disk sector size incompatibility. The highest-value diagnostic artifact to collect is the full ERRORLOG, specifically the lines just before termination, to confirm whether the 256 misaligned log IOs signature appears.

References: