“Wait on the Database Engine recovery handle failed” means Setup could not confirm that the new Database Engine started successfully. It is a summary error, not a diagnosis. Read the logs from the failed attempt before reinstalling or changing service accounts, folders or permissions.
Last updated: November 18, 2026.
$root = Join-Path $env:ProgramFiles 'Microsoft SQL Server'
$setup = Get-ChildItem $root -Filter 'Setup Bootstrap' -Directory -Recurse |
Get-ChildItem -Directory |
Sort-Object LastWriteTime -Descending |
Select-Object -First 1
Get-Content (Join-Path $setup.FullName 'Summary.txt') |
Select-String 'error|failed'
Get-Content (Join-Path $setup.FullName 'Detail.txt') -Tail 250 |
Select-String 'error|exception|failed' -Context 2,3If the latest folder does not contain both files, open the path shown on the Setup failure screen. SQL Server versions use different numbered parent folders, so locating the newest time-stamped attempt is safer than hard-coding 160.
Read the logs in the right order
Microsoft’s Setup log reference recommends searching Summary.txt for “error” or “failed,” then examining the end of Detail.txt and its surrounding errors. Use the time-stamped folder matching the failed attempt. The summary identifies the failed feature; the detail log shows the setup action that failed.
For a Database Engine startup failure, continue to the instance ERRORLOG. A default SQL Server 2022 instance commonly writes it under MSSQL16.MSSQLSERVERMSSQLLog, but named instances and custom paths differ. Find the actual instance path in the Setup logs. The first fatal startup message is more useful than the later recovery-handle message.
Fix the recorded cause, then retry once
Resolve the specific error shown in ERRORLOG or the feature-specific MSI log. Examples include an inaccessible data directory, a service account that cannot read or write the configured path, damaged installation media, or a storage-sector-size incompatibility. Microsoft’s installation troubleshooting guide notes that startup-handle failures can have different causes and explicitly recommends identifying the underlying error first.
Save the complete time-stamped log folder before cleanup. Confirm that the chosen data and log directories exist and are local, then rerun the same installer only after correcting the recorded cause. Repeated reinstalls can replace useful evidence or leave a partial instance; if Setup reports an inactive instance, follow Microsoft’s documented partial-installation removal procedure rather than deleting SQL Server folders manually.