The last message shown by SQL Server Setup is often only a wrapper around the real failure. Start with the setup summary, identify the failed feature, and then read the corresponding detailed log.
Last updated: October 16, 2026.
$root = Join-Path $env:ProgramFiles 'Microsoft SQL Server'
$summary = Get-ChildItem $root -Filter Summary.txt -Recurse |
Sort-Object LastWriteTime -Descending |
Select-Object -First 1
$summary.FullName
Select-String -Path $summary.FullName -Pattern 'failed|error|exception' -Context 2,3Run PowerShell with enough permission to read the setup folders. Record the newest summary path before launching Setup again, because another attempt creates another timestamped log set.
Read the logs in order
Microsoft stores setup logs below %ProgramFiles%\Microsoft SQL Server\<version>\Setup Bootstrap\Log. Its setup-log guide recommends starting with Summary.txt. This file identifies the overall result, failed component, error code, and timestamped folder containing that run.
Open Detail.txt in that folder and search from the bottom for error, exception, or failed. Then inspect the MSI log named for the failed feature. Preserve the earliest actionable error; later rollback messages are frequently consequences rather than causes.
Match the remedy to the first failure
Do not repeatedly rerun Setup or delete installation folders before saving the logs. Check the failed rule, Windows version support, pending restart state, free space, service-account rights, installation media, and language or locale only when the log points there. Record the SQL Server edition, build, Windows build, selected features, and exact error code.
Also check Windows Event Viewer at the same timestamp. Service Control Manager, Windows Installer, or storage events can explain why Setup could not start a service or write a file. Correlate those events with the setup log instead of treating an unrelated warning as the cause.
For failed updates, Microsoft also provides a SQL Server patching troubleshooting guide. Apply the documented remedy for the specific component, restart when required, and run Setup once more. Continue with identifying installed instances, configuring encrypted connections, and diagnosing SQL Server access errors.
