There are two common issues. The first is that your computer is an arm cpu and not supported. The second is the the disk sector size is too large. Check the install log file for actual error.
NOT BEING ABLE TO INSTALL SQL SERVER IN MY DEVICE
![](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(265.6, 32%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
Arpit Sharma
0
Reputation points
I can't insatall SQL SERVER 2025 , tried all the version and failed on every please help me !!!
SQL Server | Other
1 answer
Sort by: Most helpful
-
![](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(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Bruce (SqlWork.com) 83,666 Reputation points2026-03-29T16:11:08.0233333+00:00 -
![](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)
Akhil Gajavelly 1,725 Reputation points Microsoft External Staff Moderator2026-03-31T04:11:14.4033333+00:00 Hi @Arpit Sharma ,
Just checking in were you able to review the installation logs and identify the exact error?
As mentioned by the super users, the most common causes are:
- Unsupported CPU (ARM-based systems)
- Disk sector size issues (4KB mismatch)
The log file will point to the exact failure reason, so that’s the best next step if you haven’t checked it yet.
If you can share the specific error message from the logs, we can help you pinpoint the fix quickly.Also, thanks to the @Bruce (SqlWork.com) for pointing out the likely root causes.
Thanks,
Akhil.
Sign in to comment -