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(224.00000000000003, 57.99999999999999%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
I tried to install QL server on my new laptop and seems it's not working at all. Herewith the summary:
Summary_TUFA1420250817_20260114_071102.txt
I installed using SQL2019-SSEI-Expr, even I tried uninstalled all and tried using SQL2022-SSEI-Expr but still failed. how to solve it?
Herewith my device spec:
Processor AMD Ryzen AI 7 350 w/ Radeon 860M (2.00 GHz)
Installed RAM 32,0 GB (31,1 GB usable)
System type 64-bit operating system, x64-based processor
Edition Windows 11 Pro
Version 24H2
OS build 26100.7623
Experience Windows Feature Experience Pack 1000.26100.275.0
Core component of SQL Server for storing, processing, and securing data
Answer recommended by moderator
Did you reboot the machine after making the registry change?
After reboot run
fsutil fsinfo sectorinfo C:
To verify that you have actually made the change.
If you have other drives that you are using for SQL Server, you need to check these as well.
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.
![](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(284.8, 66%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
Hi Santos,
Just wanted to check if the above explanation helped you address your query.
If you still have any issues, you can reach out.
Thank You
Yes, I already used fsutil to check and my Physical sector for performance = 64 KB
So I just need to make "ForcedPhysicalSectorSizeInBytes = 4096" and can install the SQL without any problem?
So I just need to make "ForcedPhysicalSectorSizeInBytes = 4096" and can install the SQL without any problem?
I think you should first uninstall the half-baked installation you have now, and then start over. But just run the uninstall, don't try any manual clean. That could cause new problems.
seems the problem still there even I already have ForcedPhysical ERRORLOG.txt
is there any step that i miss?
![](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(134.4, 49%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAG%3C/text%3E%3C/svg%3E)
HI @Santos ,
Thanks for the update and thanks to Erland Sommarskog for guiding so far.
Since you already set ForcedPhysicalSectorSizeInBytes, just quickly confirm these:
If it’s still failing, then the issue is something else please share the ERRORLOG.txt (last lines) so we can pinpoint the exact cause.
Thanks,
Akhil.
Hi @Santos ,
Just checking back on this since we haven’t heard from you after the last steps.
If the install worked after validating the sector size and reinstall, then you should be all set.
If not, the key next step is still to review the ERRORLOG.txt (last lines), as that will clearly point to what’s blocking the setup.
If you’re still facing the issue, feel free to share that log here and we can take it further. Otherwise, we’ll assume this is resolved from your end.
Thanks,
Akhil.