SQL Server 2022 Express installation error -2061893606 and service error 1067

Error -2061893606 with message “Wait on the Database Engine recovery handle failed” together with service error 1067 means the SQL Server Database Engine service fails to start during setup. The setup error itself is generic; the exact cause is only visible in the SQL Server error log.

To identify the cause in this scenario, follow these steps on the machine where SQL Server 2022 Express is being installed:

1. Locate the SQL Server error log for the failing instance
   • For a default 2022 Express instance SQLEXPRESS, the error log is typically at:
     • C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\LOG\ERRORLOG
   • If EBP creates a named instance, adjust the path accordingly (the MSSQL16.<InstanceName> folder will match the instance name).
2. Open the ERRORLOG file in a text editor
   • Search from the bottom upwards for the last startup attempt.
   • Look for messages around the time setup or the service start failed.
3. Check specifically for disk/sector size issues
   • If the log contains a message about “256 misaligned reads” or similar sector-size errors, this indicates a known compatibility issue on some Windows 11 systems where the reported disk sector size is not supported by SQL Server.
   • In that case, apply the workarounds described in the Microsoft article referenced in the Q&A posts about misaligned reads on Windows 11 (for example, using a supported virtual disk/volume configuration) and then rerun the installation.
4. If there is no “256 misaligned reads” message
   • The failure is due to another startup problem (for example, configuration, environment, or platform compatibility). In that case, the next step is to use the exact messages from the ERRORLOG as the basis for further troubleshooting.
5. Platform and edition considerations
   • On some secured Windows 11 devices with VBS/HVCI enforced, SQL Server 2022 Express has been observed to crash with EXCEPTION_STACK_OVERFLOW and error 1067. In such cases, installing SQL Server 2022 Developer Edition instead of Express (or using LocalDB if a lightweight instance is sufficient) has been reported to work reliably.
   • If the machine is ARM-based, full SQL Server (including Express) is not supported; only LocalDB under emulation or other workarounds may function.
6. If LocalDB is sufficient for the EBP scenario
   • Verify LocalDB installation and instance status:

          sqllocaldb info
          sqllocaldb info MSSQLLocalDB
     

   • Start the instance if needed:

          sqllocaldb start MSSQLLocalDB
     

   • If LocalDB fails to start, review its error log at:
     • %LOCALAPPDATA%\Microsoft\Microsoft SQL Server Local DB\Instances\MSSQLLocalDB\error.log

In summary, the exact cause cannot be determined from the exit code alone; it must be read from the SQL Server ERRORLOG. The most common causes matching this pattern on Windows 11 are:

• Disk sector-size incompatibility (look for “256 misaligned reads” in the log).
• Environment/compatibility issues on secured or unsupported platforms, where switching to Developer Edition or LocalDB resolves the startup failure.

References:

• Unable to install SQL Express - Microsoft Q&A
• Unable to install SQL server (Setup.exe) Exit code:-2061893606 - Microsoft Q&A
• Wait on the Database Engine recovery handle failed - Microsoft Q&A
• SQL Server 2022 Express Edition Install Error - Microsoft Q&A
• SQL Server Express LocalDB
• SQL Server startup errors on a standalone server
• MSSQLSERVER_17826
• SQL Server installation errors