Forum Discussion
SQL Server installation issues
aolawoyin Hi Aminat,
When I searched your error message from the screenshot, I found the following article:
SQL Server error Wait on the Database Engine Recovery Handle Failed (mssqltips.com)
It suggests that the user account that was selected as the service account somehow does not have sufficient privileges to start SQL Server. In this case it would be "SQLSVCACCOUNT: NT Service\MSSQL$MYSQL", which is the default, inbuilt account for an instance named "MYSQL".
Please attempt to reinstall the instance using "NT AUTHORITY\SYSTEM" as your service account. Please note, it is not recommended to use "SYSTEM" for this, but needs must.
I would also like to mention that I've had issues installing SQL Server 2022 on systems where I've already installed SQL Server Management Studio.
If you still have issues, and SSMS is installed, please uninstall SSMS and the ODBC and OLE DB drivers for SQL Server before attempting a reinstall.
Based on the text in your ERRORLOG, this is the more likely culprit:
https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size#:~:text=for%20potential%20causes.-,Scenario%20%232%3A,-You%20install%20any
You're attempting to install SQL Server on a drive with a "physical sector size" larger than 4k on a Windows 11 machine, and most likely need to enable emulation of 4k "physical sector size".
You can verify this using the following in command or powershell (administrator)
fsutil fsinfo sectorinfo C
Compare the values PhysicalBytesPerSectorForAtomicity and PhysicalBytesPerSectorForPerformance, and if either of them are larger than 4096, your symptoms would be likely to show up.
Using powershell as administrator, you can add a registry key value pair.
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" -Name "ForcedPhysicalSectorSizeInBytes" -PropertyType MultiString -Force -Value "* 4095"
After a reboot, you should be able to start SQL Server.
Alternatively, you can start SQL Server using traceflag 1800.
This article describes how to add trace flags as startup parameters to SQL Server.
https://www.sqlshack.com/microsoft-sql-server-trace-flags-and-usage-details/#:~:text=Adding%20a%20trace%20flag%20into%20the%20Microsoft%20SQL%20Server%20startup%20parameters