This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 51%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Action required: Use the following information to resolve the error, uninstall this feature, and then run the setup process again. Feature failure reason: An error occurred for a dependency of the feature causing the setup process for the feature to fail. Error details: § Error installing SQL Server Database Engine Services Instance Features Could not find the Database Engine startup handle. Error code: 0x851A0019 Visithttps://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025 to get help on troubleshooting.
The screenshot is useless. View and Read SQL Server Setup Log Files for more details
I can't find folder "140"
Копач Соломія Русланівна For SQL2022, the folder named '160'
What's next?
The error message about not finding the startup handle is a generic message that tells us at that SQL Server did not start when Setup wanted to configure the server.
To find out why it not start, check the SQL Server errorlog, which you find in C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\LOG\ERRORLOG. (Assuming that you were installing Express Edition. The actual path depends in your installation choices.)
If you see a message about 256 misaligned reads you are running into a known issue with Windows 11 and SQL Server not always being compatible. Microsoft has published an article with workarounds for that problem.
If you don't see that message, feel free to upload it here for assistance. You will need to rename it to ERRORLOG.txt for the forum software to accept it.
This is the critical part:
2024-02-08 13:15:03.43 spid26s Error: 17190, Severity: 16, State: 1.> 2024-02-08 13:15:03.43 spid26s Initializing the FallBack certificate failed with error code: 15, state: 29, error number: 0.> 2024-02-08 13:15:03.43 spid26s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.> 2024-02-08 13:15:03.43 spid26s Error: 17182, Severity: 16, State: 1.> 2024-02-08 13:15:03.43 spid26s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
This is usually due to that the WIndows profile for the default user is corrupted. If you are following the defaults, you are creating a new user NT Service\MSSQL$SQLEXPRESS, and it's Windows profile is created by copying the profile for the default user.
One way to work around that is to use a built-in user like LocalService, but I don't like that. And in any case, you will need to repair that corrupted user sooner or later.
As for how to do that - that is more of a Windows problem. I recall that I when I ran into this myself, I googled around, and one suggestion was to copy the default profile from another computer. I believe, though, that I ended up restoring the profile from a backup.
If you are using Windows 11, there is a known issue when you install sql server 2022 on Windows 11.
Try one of the resolutions in this article.
If this do not work, in the folder C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log there is one folder per install attempt. The one of most interest is Detail.txt. Feel free to attach it here.
Regards，
Zoe Hui
If the answer is helpful, please click "Accept Answer" and upvote it.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Thank you for your answer, but I use Windows10.