Hi @Obehi ,
This thread mentions a similar error, of course some of them are obsolete, in the official doc, win11 has been already list as supported SQL Server 2019.
At the same time, at lease one problem still exists as mentioned in the thread above, this issue seems to be due to a change in how Windows handles the reported sector size for certain NVMe SSDs but the investigation is still ongoing.
If you find you have the same error after you check your error log, there is a possible solution:
Install SQL on a secondary drive(if able) that is separate physical disk from the system's C: drive, creating a VHD to use for the SQL Server installation, or enabling TF1800. There are additional documentation updates planned to provide more information regarding this scenario.
-------------
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.