1)Install the latest version of the SQL server
in this scenario, you could download and install the latest version of SQL. Hopefully, after downloading and installing the newer version of the SQL server, your issue will be resolved.
2) Delete the affected registry key
In this solution, we will delete the registry keys that are related to the previously installed version of SQL Server. Even if you don’t have any instance of SQL Server installed on your system, you should still delete the files mentioned hereinafter as during the installation process they are created and can hinder another attempt of installation. Deleting the affected registry key should be done with caution, as we know that Windows Registry is a database that contains information and settings for all hardware, software, and users.
Open Registry Editor.
Now, delete the following keys.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
Now, navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
and then delete all the keys associated with SQL Server.
Then, move to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
Windows 11 Problems, Issues with solutions, and fixes
Advanced Settings
FullscreenPlayRewind 10 SecondsUp Next
Windows 11 Problems, Issues with solutions, and fixes
Finally, restart the system.
Hopefully, this will do the job for you.
3) Make changes to the sector size of the drive

The SQL server installation is influenced by the potential impact of the disk sector size. SQL Server is compatible with 4 KB of sector size, which is represented by 4096, if the size is any different, it will not be compatible.
Let’s check the sector size of the drive:
Press the Windows + X key and select Terminal (Admin) or open Command Prompt as administrator.
Enter the following command and make sure to replace the C drive if you are installing the SQL server in other drives.
fsutil fsinfo sectorinfo C:
Find out the PhysicalBytesPerSectorForAtomicity and PhysicalBytesPerSectorForPerformance values.
Old hard drives often use a 512-byte sector size, while newer Advanced Format (AF) drives typically use a 4K (4096-byte) sector size. If the values are different here, then you should locate the one that has a higher value. If the sector size value is higher than 4096 then it needs some changes in the registry.
Open the Command Prompt as administrator.
Enter the following command to add the key:
REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes" /t REG_MULTI_SZ /d "* 4095" /f
Run the following command to confirm if the key is added successfully:
REG QUERY "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes"
Now make sure the disk sector size is not higher than 4096.
Enter the following command:
fsutil fsinfo sectorinfo C:
This command will display information about the sectors per cluster on the specified drive.
Finally, check if the issue is resolved.
We hope that you can resolve the issue using the solutions