Unable to install SQL Express 2019 on Windows 11, Error code: 2061893606, Wait on the database engine recovery handle failed

Kevin Liu 21

I've been unable to install the program and I've seen in the forums that people should start a new thread.

247668-sqlserver-errorlog-2022-10-05t131433.txt

247758-summary-kiwi-20221005-131349.txt

Shivam Kumar 536 Reputation points

2022-10-05T12:31:36.497+00:00

Hi @Kevin Liu

Where is your setup file located ? If its in C drive or downloads etc move it some other directory D: E: or any XYZ: depends on what you have.
Run the setup by right clicking on setup file and Run as Administrator not by just double clicking it.

Regards,
Shivam
Kevin Liu 21 Reputation points

2022-10-05T12:39:33.9+00:00

Both in the C: Drive, I only have that one drive. Didn't work running as admin
Shivam Kumar 536 Reputation points

2022-10-05T12:44:23.867+00:00

Try changing service accounts for database engine to NT Authority\SYSTEM during installation settings and see if that works.
Shivam Kumar 536 Reputation points

2022-10-05T12:50:04.187+00:00

search for sql server configuration manager in start menu windows and see if you are able to find instance that you just tried to install if yes according to setup error log it says :

2022-10-05 13:14:31.87 Server The service account is 'NT Service\MSSQL$SQLEXPRESS01'. This is an informational message; no user action is required.

Try changing this service account to NT Authority\SYSTEM or give read write permissions to NT Service\MSSQL$SQLEXPRESS01 in sql server files directory ie. C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS01\MSSQL\DATA\ and C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS01\MSSQL\Log\

Accepted answer

YufeiShao-msft 7,056 Reputation points

2022-10-06T08:24:27.563+00:00

Hi @Kevin Liu ，

Please check out this doc:
Troubleshoot errors related to system disk sector size greater than 4 KB

The simplest way has been stated by ShivamKumar, other methods are described in this doc, you can also try these operations

Search for SSCM:

find SQL Server service, right-click and choose properities

Startup Parameters and add -T1800

Another:
Use the Registry Editor, add a registry key:
Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device.

On the Edit menu, point to New, and then select Multi-String value. Name it ForcedPhysicalSectorSizeInBytes.

Modify the new value, type in * 4095. Click OK and close the Registry editor.

-------------

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.
Please sign in to rate this answer.

1 person found this answer helpful.
Kevin Liu 21 Reputation points

2022-10-07T08:36:12.627+00:00

Thank you for your help, it seems to work now. Edited the registry, deleted the program and reinstalled. The -T1800 trick didn't do anything.
Sign in to comment

1 additional answer

Shivam Kumar 536 Reputation points

2022-10-05T13:00:30.367+00:00

Also as in error log misaligned log IO is being reported :

There have been 256 misaligned log IOs which required falling back to synchronous IO.

try starting the database engine service with trace flag 1800 enabled if that doesn't works here is the article it seems in windows 11 there is some difference in disk sector size which is causing this issue:

On systems running Windows 11, some new storage devices and device drivers will expose a disk sector size greater than the supported 4 KB sector size.

When this occurs, SQL Server will be unable to start due to the unsupported file system as SQL Server currently supports sector storage sizes of 512 bytes and 4 KB.

User with same problem

Enable Trace Flag
Please sign in to rate this answer.

1 person found this answer helpful.
Kevin Liu 21 Reputation points

2022-10-05T13:22:50.747+00:00

I'm very confused, I'm not familiar with the SQL program and all the technical aspects of the computer. I just needed the program for my studies.

Shivam Kumar 536 Reputation points

2022-10-05T13:40:48.477+00:00

Alright not an issue here is what you need to do :
Go to Windows Start > Search for "SQL Server configuration Manager" open it > Go to SQL Server services in left pane > On right pane Select SQL Server(MSSQLSERVER) service and right click on it and go to properties > Click on Startup Parameters >In specify a startup parameter input box type
-T1800 (with minus sign) and then click add > Apply > OK
Once done , right click on SQL server service again and select start and see if it starts, if yes your problem is resolved if no then we will work further...

Shivam Kumar 536 Reputation points

2022-10-07T07:50:49.853+00:00

Hi @Kevin Liu

Any update on this , did it resolved your issue?

Regards,
Shivam

Kevin Liu 21 Reputation points

2022-10-07T07:59:07.613+00:00

It's funny, I'm having SQL class and I had to reinstalled the program succesfully it says the moment you asked for updates.
Editing the registry alone wasn't enough and/or using the -T1800. I'll find out soon if it all works, thank you. I had to edit the registry, delete the program and reinstall.

Shivam Kumar 536 Reputation points

2022-10-07T08:13:46.83+00:00

Well looks like it is indeed fun.
Hope this time it works, we try changing registries as last resort always as its more technical thing to do and a small wrong change there can cause issues in whole OS which is why I started small with Run as admin and then to trace and then if nothing would have worked eventually would have moved to registries.
Make sure you always backup the registries before making any changes ,just in case things dont go the way we want.

Let us know if it works or what worked once it gets installed successfully, it helps.

Kevin Liu 21 Reputation points

2022-10-07T08:50:59.143+00:00

It works now, again thank you for your help.

Shivam Kumar 536 Reputation points

2022-10-07T10:30:08.293+00:00

Great! thanks for update.
Sign in to comment