Wait on the Database Engine recovery handle failed.
Applies to: Microsoft SQL Server 2019/2022 on Windows 11/Windows 10.
Date created: November 22, 2022.
 
Problem Description.
 
After installing SQL Server on your computer you receive an error saying SQL 
Server fails to start.
When you examine the 
Summary.txt log file created by SQL Server setup program, you get the 
following errors:
 
Detailed results:
Feature: Database Engine Services
Status: Failed
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this 
feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the 
SQL Server error log for potential causes.
Feature: SQL Server Replication
Status: Failed
Reason for failure: An error occurred for a dependency of the feature causing 
the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this 
feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery 
handle failed. Check the SQL Server error log for potential causes.
Feature: Client Tools Connectivity
Status: Failed
Reason for failure: An error occurred for a dependency of the feature causing 
the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this 
feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x84BB0001
Error description: The MOF compiler could not connect 
with the WMI server. This is either because of a semantic error such 
as an incompatibility with the existing WMI repository or an actual error such 
as the failure of the WMI server to start.
 
Workaround/Solution.
This could be related to 
a known issue related disk sector size greater than 4 KB. As a solution 
make the following changes on the Registry:
	- Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device.
- On the Edit menu, point to New, and then select Multi-String value. Name 
	it ForcedPhysicalSectorSizeInBytes.
- Modify the new value, type in "* 4095". Click OK and close the Registry 
	editor.
If the issue is not related to above mentioned issue, you can try running the 
following command using the Command Prompt from the drive where SQL Server media 
is located.
setup /ACTION=REBUILDDATABASE /QUIET /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=domain_or_computer\YourWindowsAccount 
/SAPWD=sapassword /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS