SQL server gave me data baste engine recovery failed AT EXIT CODE -2061893606 ERROR

after downloading and after doing the 4k setup provided here i tried installing but got an error -2061893606

and the Overall summary:

Final result: Failed: see details below

Exit code (Decimal): -2061893606

Start time: 2026-01-14 23:34:44

End time: 2026-01-14 23:40:32

Requested action: Install

Setup completed with required actions for features.

Troubleshooting information for those features:

Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.

Machine Properties:

Machine name: DESKTOP-C18H0V3

Machine processor count: 12

OS version: Microsoft Windows 11 Pro (10.0.26100)

OS service pack:

OS region: United States

OS language: English (United States)

OS architecture: x64

Process architecture: 64 Bit

OS clustered: No

Product features discovered:

Product Instance Instance ID Feature Language Edition Version Clustered Configured

Package properties:

Description: Microsoft SQL Server 2025

ProductName: SQL Server 2025

Type: RTM

Version: 17

SPLevel: 0

Installation location: C:\SQL2025\EntDev_ENU\x64\setup\

Installation edition: Enterprise Developer

Product Update Status:

User selected not to include product updates.

Notice: Please read Microsoft SQL Server Software License Terms at aka.ms/useterms.

User Input Settings:

ACTION: Install

ADDCURRENTUSERASSQLADMIN: false

AGTSVCACCOUNT: NT Service\SQLSERVERAGENT

AGTSVCPASSWORD: *****

AGTSVCSTARTUPTYPE: Manual

ASBACKUPDIR: Backup

ASCOLLATION: Latin1_General_CI_AS

ASCONFIGDIR: Config

ASDATADIR: Data

ASLOGDIR: Log

ASPROVIDERMSOLAP: 1

ASSERVERMODE: TABULAR

ASSVCACCOUNT: <empty>

ASSVCPASSWORD: <empty>

ASSVCSTARTUPTYPE: Automatic

ASSYSADMINACCOUNTS: <empty>

ASTELSVCACCT: <empty>

ASTELSVCPASSWORD: <empty>

ASTELSVCSTARTUPTYPE: 0

ASTEMPDIR: Temp

AZUREARCPROXYSERVER: <empty>

AZUREBILLEDEDITION:

AZUREREGION: <empty>

AZURERESOURCEGROUP: <empty>

AZURESERVICEPRINCIPAL: <empty>

AZURESERVICEPRINCIPALSECRET: <empty>

AZURESUBSCRIPTIONID: <empty>

AZURETENANTID: <empty>

AZUREVMNAME: <empty>

BROWSERSVCSTARTUPTYPE: Disabled

CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260114_233443\ConfigurationFile.ini

ENABLERANU: false

ENU: true

EXTSVCACCOUNT: <empty>

EXTSVCPASSWORD: <empty>

FEATURES: SQLENGINE

FILESTREAMLEVEL: 0

FILESTREAMSHARENAME: <empty>

FTSVCACCOUNT: <empty>

FTSVCPASSWORD: <empty>

HELP: false

IACCEPTDQUNINSTALL: false

IACCEPTSQLSERVERLICENSETERMS: true

IACKNOWLEDGEENTCALLIMITS: false

INDICATEPROGRESS: true

INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\

INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\

INSTALLSQLDATADIR: <empty>

INSTANCEDIR: C:\Program Files\Microsoft SQL Server

INSTANCEID: MSSQLSERVER

INSTANCENAME: MSSQLSERVER

ISMASTERSVCACCOUNT: NT AUTHORITY\Network Service

ISMASTERSVCPASSWORD: <empty>

ISMASTERSVCPORT: 8391

ISMASTERSVCSSLCERTCN: <empty>

ISMASTERSVCSTARTUPTYPE: Automatic

ISMASTERSVCTHUMBPRINT: <empty>

ISSVCACCOUNT: NT AUTHORITY\Network Service

ISSVCPASSWORD: <empty>

ISSVCSTARTUPTYPE: Automatic

ISTELSVCACCT: <empty>

ISTELSVCPASSWORD: <empty>

ISTELSVCSTARTUPTYPE: 0

ISWORKERSVCACCOUNT: NT AUTHORITY\Network Service

ISWORKERSVCCERT: <empty>

ISWORKERSVCMASTER: <empty>

ISWORKERSVCPASSWORD: <empty>

ISWORKERSVCSTARTUPTYPE: Automatic

NPENABLED: 0

PBDMSSVCACCOUNT: <empty>

PBDMSSVCPASSWORD: <empty>

PBDMSSVCSTARTUPTYPE: 0

PBENGSVCACCOUNT: <empty>

PBENGSVCPASSWORD: <empty>

PBENGSVCSTARTUPTYPE: 0

PBPORTRANGE: <empty>

PID: *****

PRODUCTCOVEREDBYSA: false

QUIET: true

QUIETSIMPLE: false

ROLE:

SAPWD: <empty>

SECURITYMODE: <empty>

SQLBACKUPDIR: <empty>

SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS

SQLMAXDOP: 12

SQLMAXMEMORY: 2147483647

SQLMINMEMORY: 0

SQLSVCACCOUNT: NT Service\MSSQLSERVER

SQLSVCINSTANTFILEINIT: true

SQLSVCPASSWORD: <empty>

SQLSVCSTARTUPTYPE: Automatic

SQLSYSADMINACCOUNTS: DESKTOP-C18H0V3\LENOVO

SQLTELSVCACCT: NT Service\SQLTELEMETRY

SQLTELSVCPASSWORD: <empty>

SQLTELSVCSTARTUPTYPE: Automatic

SQLTEMPDBDIR: <empty>

SQLTEMPDBFILECOUNT: 8

SQLTEMPDBFILEGROWTH: 64

SQLTEMPDBFILESIZE: 8

SQLTEMPDBLOGDIR: <empty>

SQLTEMPDBLOGFILEGROWTH: 64

SQLTEMPDBLOGFILESIZE: 8

SQLUSERDBDIR: <empty>

SQLUSERDBLOGDIR: <empty>

SUPPRESSPAIDEDITIONNOTICE: false

SUPPRESSPRIVACYSTATEMENTNOTICE: false

TCPENABLED: 0

UIMODE: Normal

UpdateEnabled: false

UpdateSource: MU

USEMICROSOFTUPDATE: false

USESQLRECOMMENDEDMEMORYLIMITS: false

Configuration file: C:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260114_233443\ConfigurationFile.ini

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.

Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=17.0.1000.7&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

Feature: SQL Browser

Status: Passed

Feature: SQL Writer

Status: Passed

Feature: Setup Support Files

Status: Passed

Rules with failures or warnings:

Global rules:

Warning IsFirewallEnabled The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at https://go.microsoft.com/fwlink/?linkid=2162127 for information about ports to open for each feature.

Scenario config specific rules:

Warning LargeSectorSizeCheck One or more disks intended for SQL Server data have a physical sector size greater than 4 KB. SQL Server currently supports physical sector sizes up to 4 KB. Review your storage configuration or refer to the documentation for guidance.

Rules report file: C:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260114_233443\SystemConfigurationCheck_Report.htm

0 comments No comments
Sign in to comment

Answer recommended by moderator

Erland Sommarskog 134.7K Reputation points • MVP • Volunteer Moderator

Warning LargeSectorSizeCheck One or more disks intended for SQL Server data have a physical sector size greater than 4 KB. SQL Server currently supports physical sector sizes up to 4 KB. Review your storage configuration or refer to the documentation for guidance.'

You are running into a known issue, which is discussed further in this article.

Also, please don't post the same question multiple times. I have marked your other posts as duplicates.

  1. Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

    Hi @mohmaed ahmed mohamed rahmo ,

    The issue isn’t permissions or a bad install. Your setup log shows LargeSectorSizeCheck, which means the disk uses 4 KB (4Kn) sectors. SQL Server Database Engine cannot start on 4Kn storage, so setup fails with the recovery handle error.

    Reinstalling won’t help. You need to install SQL Server on a 512e disk (or a 512e VHD/VM).

    You can confirm with: “fsutil fsinfo sectorinfo C:”

    If it shows 4096, that’s the cause.

    Once installed on 512e storage, SQL Server starts normally.

    Thanks,
    Akhil.

  2. Akhil Gajavelly 1,830 Reputation points • Microsoft External Staff • Moderator

    Hi @mohmaed ahmed mohamed rahmo ,

    Just following up to check whether moving the installation to a 512e disk resolved the issue.

    If this explanation helped, please mark the reply as accepted so others with the same LargeSectorSizeCheck / 4Kn error can find it easily. If you’re still blocked, let us know what fsutil fsinfo sectorinfo reports.

    Thanks,
    Akhil.

Sign in to comment

1 additional answer

  1. AI answer

    The error message you are encountering, "Wait on the Database Engine recovery handle failed," typically indicates that SQL Server did not start as expected during the installation process. This can be caused by several factors, including disk sector size incompatibility, corrupted service accounts, or remnants from previous installations.

    Here are some steps you can take to troubleshoot and resolve this issue:

    1. Check SQL Server Error Log: Look for the SQL Server error log located at C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\LOG\ERRORLOG. This log can provide more specific details about why the SQL Server instance failed to start.
    2. Disk Sector Size: Since you received a warning about the physical sector size being greater than 4 KB, you may need to check your disk configuration. SQL Server supports physical sector sizes up to 4 KB. You can run the command fsutil fsinfo sectorinfo C: in an elevated command prompt to check the sector size. If it's greater than 4096, you may need to apply a registry fix as suggested in the documentation.
    3. Uninstall Previous Installations: If there are remnants from previous SQL Server installations, they could interfere with the new installation. Uninstall all SQL Server components from Control Panel > Programs and Features, and delete the SQL Server installation folders located at:
      • C:\Program Files\Microsoft SQL Server
      • C:\Program Files (x86)\Microsoft SQL Server After cleaning up, try the installation again.
    4. Run Setup as Administrator: Ensure that you are running the SQL Server setup as an administrator to avoid permission issues.
    5. Check Firewall Settings: The warning about the Windows Firewall being enabled suggests that you should ensure the appropriate ports are open to allow SQL Server to operate correctly.

    If you continue to encounter issues, please share the contents of the SQL Server error log for further analysis.

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer