SQL Server 2022 express download problem unable to install SQL Server. Exit code(Decimal): -2061893606

Mehmed Aras 20 Reputation points
2024-05-09T12:23:12.46+00:00

I'm trying to download SQL Server 2022 Express, but it's giving the following error.Screenshot 2024-05-09 111307

I checked the log and click the SystemConfigurationCheck_Report

Screenshot 2024-05-09 110404

I received the warning shown in the image above. Is the download error caused by this? I had already disabled my Windows Defender. I saw similar questions about this issue but couldn't find a solution for my problem. I would appreciate it if you could help. I can provide additional information if needed.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,948 questions
{count} votes

Accepted answer
  1. LucyChenMSFT-4874 1,815 Reputation points
    2024-05-23T08:13:22.5466667+00:00

    Hi Hi @Mehmed Aras ,

    Thanks for your kindly feedback.

    From the screenshot you provide, we can get the error message :

    User's image

    This is a known issue, from this article, we can get the solutions below:

    User's image

    • If you have multiple drives on this system, you can specify a different location for the database files after installation of SQL Server is complete. Make sure that drive reflects a supported sector size when querying the commands. SQL Server currently supports sector storage sizes of 512 bytes and 4096 bytes.fsutil
    • You can add a registry key, which will cause the behavior of Windows 11 and later to be similar to Windows 10. This forces the sector size to be emulated as 4 KB. To add the registry key, use the Registry Editor or run commands as described in the PowerShell as Administrator section. You must reboot the device after adding the registry key in order for this change to take effect.ForcedPhysicalSectorSizeInBytes

    Registry Editor

    1. Navigate to .Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device
    2. On the Edit menu, point to New, and then select Multi-String value. Name it .ForcedPhysicalSectorSizeInBytes
    3. Modify the new value, type in . Select OK and close the Registry editor.* 4095

    You can get more detailed information from the article I provide. Hope this can help you well.

    User's image

    Regards,

    Lucy Chen


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    https://docs.microsoft.com/en-us/answers/support/email-notificationsHi


2 additional answers

Sort by: Most helpful
  1. Erland Sommarskog 102.5K Reputation points
    2024-05-09T13:32:12.1366667+00:00

    The message Wait on the Database Engine recovery handle failed is a generic error that means that SQL Server did not start when Setup wanted to run configuration steps. To understand why it did not start, you need to look in the SQL Server errorlog, which you find in C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\LOG\ERRORLOG.

    If you see a message about 256 misaligned reads, you are running into a known issue where Windows 11 for some disk drives reports a sector size that SQL Server does not cope with. Microsoft has published an article with workarounds for the problem.

    If you don't see the message about misaligned reads, feel free to upload the errorlog here, so we can look at it. You will need to rename to ERRORLOG.txt for the forum software to accept it.

    0 comments No comments

  2. LucyChenMSFT-4874 1,815 Reputation points
    2024-05-10T02:19:18.57+00:00

    Hi @Mehmed Aras ,

    Thanks for your information.

    We can get the error message "Wait on the Database Engine recovery handle failed" from the screenshot you provided. Please check out this article, it explains detailed steps in how to troubleshoot this issue.

    However, we cannot rely on old threads completely. The above article can only be used as a reference, could you please provide detailed logs to help us narrow down your issue? Thanks for your understanding, we are looking forward to hearing from you to assist further.

    Best regards,

    Lucy Chen


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    https://docs.microsoft.com/en-us/answers/support/email-notifications