Can't install SQLServer on Windows server 2022 but no problem in Server 2019

KZS 151 Reputation points
2021-10-07T00:40:10.477+00:00

I clean installed Windows server 2022 and I can't install SQL Server 2019. I receive error
"Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes."

The same server was working without problem with Windows server 2019 and Microsoft Sql 2019

I attached the log

138268-detail.txt

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,676 questions

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. YufeiShao-msft 7,056 Reputation points
    2021-10-07T05:51:22.307+00:00

    Hi @KZS ，

    The possible cause is a corruptied user profile for the user account used to start the database.
    When you come to Server Configuration page, change the Account Name of SQL Server Database Engine to NT AUTHORITY\NETWORK SERVICE (if it failed, you can also try to ues NT AUTHORITY\SYSTEM)

    1 person found this answer helpful.
    0 comments
  2. KZS 151 Reputation points
    2021-10-07T07:13:30+00:00

    I tried both Account name and still the same error

    1 person found this answer helpful.
    0 comments
  3. Erland Sommarskog 100.9K Reputation points MVP
    2021-10-07T22:02:27.807+00:00

    This error message means that SQL Server does not start, when Setup wants to run installation scripts.

    You need to look in the errorlog file to find more information. You find it in C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG assuming a default instance.

    When Yufeishao suggested a corrupted user profile, it was a shot from a hip. It is a common reason, but you really need to look at the errorlog first.

    1 person found this answer helpful.
    0 comments
  4. KZS 151 Reputation points
    2021-10-18T08:43:33.557+00:00

    Unfortunately I wasn't able to fix the problem with Windows 2022. Tried all fixes I found without success.
    I had to use Windows 2019 to fix the problem and be able to use MSSQL.