Not able to install Microsoft SQL Express

Question

Not able to install Microsoft SQL Express

Bobbala Anusha 0

I have attempted installation multiple times, but it keeps failing. Steps I have already tried:

Cleaned up old SQL Server components and services
Verified prerequisites (.NET Framework 4.8, Visual C++ Redistributables, Windows updates)
Ran installer as Administrator
Attempted Safe Mode cleanup and ownership resets
Verified disk partitions and created local directories outside OneDrive sync

System Details:

Windows 11 (64‑bit)
Local disk setup: C: and D: partitions configured for SQL data/logs/temp/backups
OneDrive is active but SQL directories are excluded
Device is out of warranty

Despite all this, the installation still does not complete successfully. Please guide me on how to resolve this issue so I can continue practicing SQL.

Bobbala Anusha 0 Reputation points

2026-03-26T16:18:45.2266667+00:00

tried and tired for time wasting
Viorel 126.8K Reputation points

2026-03-26T16:35:45.43+00:00

How do you realize that it is not installing successfully?
Akhil Gajavelly 1,735 Reputation points Microsoft External Staff Moderator

2026-04-14T04:29:18.99+00:00

Hi @Bobbala Anusha ,

Just checking back on this. Were you able to review the SQL Server setup logs or capture any specific error message during installation?

The exact failure detail (from Summary.txt or the installer screen) is important to identify the root cause without that, it’s mostly guesswork.

If you can share the error code or a snippet from the latest log folder, I’ll help narrow it down to a precise fix.

Thanks,
Akhil.
Akhil Gajavelly 1,735 Reputation points Microsoft External Staff Moderator

2026-04-17T03:41:53.11+00:00

Hi @Bobbala Anusha ,

Just following up were you able to check the setup logs or capture the exact error message?

A quick snippet from Summary.txt (under Setup Bootstrap\Log) will help identify the root cause. Without that, it’s mostly guesswork.

Please share when you can, and I’ll help narrow it down quickly.

Thanks,
Akhil.

2 answers

Your answer

Bobbala Anusha 0 Reputation points

2026-03-26T16:18:45.2266667+00:00

tried and tired for time wasting
Viorel 126.8K Reputation points

2026-03-26T16:35:45.43+00:00

How do you realize that it is not installing successfully?
Akhil Gajavelly 1,735 Reputation points Microsoft External Staff Moderator

2026-04-14T04:29:18.99+00:00

Hi @Bobbala Anusha ,

Just checking back on this. Were you able to review the SQL Server setup logs or capture any specific error message during installation?

The exact failure detail (from Summary.txt or the installer screen) is important to identify the root cause without that, it’s mostly guesswork.

If you can share the error code or a snippet from the latest log folder, I’ll help narrow it down to a precise fix.

Thanks,
Akhil.
Akhil Gajavelly 1,735 Reputation points Microsoft External Staff Moderator

2026-04-17T03:41:53.11+00:00

Hi @Bobbala Anusha ,

Just following up were you able to check the setup logs or capture the exact error message?

A quick snippet from Summary.txt (under Setup Bootstrap\Log) will help identify the root cause. Without that, it’s mostly guesswork.

Please share when you can, and I’ll help narrow it down quickly.

Thanks,
Akhil.

Answer 1

Hi @Bobbala Anusha ,

It sounds like you’ve already covered most of the common fixes, so this likely needs a more specific error from the setup logs rather than repeating general steps.

When you say it’s “not installing successfully”, could you share:

The exact error message / code shown in the installer
Or the Summary.txt from: C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log<latest folder>

That will help pinpoint whether it’s:

Engine startup failure
Permission issue
Disk/sector size problem (common on Windows 11)
Or corrupted media

Right now it’s hard to narrow it down without the exact failure point once you share that, the community can give a precise fix instead of trial-and-error

Thanks,
Akhil.

Answer 2

Follow these steps in order, focusing on identifying the exact cause from logs and media, then reinstalling cleanly.

Confirm installation media and method

Download a fresh SQL Server Express installer from the official SQL Server downloads page (not from a third‑party mirror).
Prefer the offline / media / custom installer instead of the Basic web installer to avoid partial downloads or network issues.
Store the installer on a local drive (for example, C:) that is not a OneDrive‑synced folder.
Run the installer by right‑clicking setup.exe → Run as administrator.

Rule out damaged or corrupted media If setup fails with errors like:

“The system cannot open the device or file specified.”
“Setup.rll is either not designed to run on Windows or it contains an error.”
“The cabinet file 'Sql.cab' required for this installation is corrupt and cannot be used.”

Then do the following:

Download the SQL Server image/installer again from the original Microsoft location.
If installing from a network share, instead copy the media to a local drive and run setup from there.
If you see errors specifically mentioning Setup.rll, rename it:
- Open File Explorer.
- Go to:
  C:\Program Files\Microsoft SQL Server\1XX\Setup Bootstrap\SQLXXX\resources\1033
- Right‑click Setup.rll → Rename → change to setup.rll.old.
- Rerun setup.
Check for localization issues If using a non‑English or localized SQL Server Express installer:

Ensure Windows regional/language settings support that localization.
If the log shows “The ENU localization is not supported by this SQL Server Media”, switch to a matching language build or adjust OS language settings as described in Local Language Versions in SQL Server.

Verify installation locations and disk setup When running the SQL Server Installation Wizard:

Ensure program files and data files are not placed:
- On a removable disk drive.
- On a compressed file system.
- In a directory where system files are located.
If specifying non‑default data directories (for example on D:):
- Use folders unique to this instance (do not share with other SQL instances).
- Avoid mapped network drives for Database Engine data directories.
If using SMB/file shares for data directories, the account running setup must have:
- Full Control NTFS permissions on the share.
- SeSecurityPrivilege (Manage auditing and security log) on the file server.

Read the SQL Server setup logs When setup fails, always inspect the logs to identify the real blocker:

Go to the setup log folder, typically under:
C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\<latest_timestamp_folder>
Open Summary.txt and the detailed component logs.
Also check the SQL Server error log for the instance being installed (for example, under MSSQLXX.<InstanceName>\MSSQL\LOG).
Look for:
- “Wait on the Database Engine recovery handle failed” (engine did not start).
- Disk/sector size or misaligned reads messages.
- “Network error occurred while attempting to read from the file.”

If the error is “Wait on the Database Engine recovery handle failed”, the SQL error log will usually indicate whether the cause is disk sector size, permissions, or something else.

Handle common engine‑startup failures If the logs show:

Disk sector size / misaligned reads on Windows 11:
- This is a known issue with some drives reporting sector sizes SQL Server cannot use.
- Follow the workaround in the referenced article on troubleshooting OS 4KB disk sector size (for example, using the ForcedPhysicalSectorSizeInBytes registry setting for NVMe, then reboot and reinstall).
Media or source corruption:
- Re‑download the installer.
- Ensure antivirus or security software is not blocking read access to the setup files.

If installation partially succeeded, use repair If there is a partially installed instance and the summary log states:

“SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, and then repair your installation.”

Then:

Launch the SQL Server setup from the same media.
Choose Repair for the affected instance.

If the summary log instead says only:

“SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem.”

Then the instance cannot be repaired and must be fully uninstalled and reinstalled.

Additional checks for SSMS vs. engine If the failure is for SQL Server Management Studio (SSMS) rather than the Database Engine:

Uninstall Microsoft ODBC Driver 17 for SQL Server from Control Panel → Programs and Features.
Restart if prompted.
Install the latest SSMS again.

If issues persist After applying the above and re‑running setup with fresh media from a local path, re‑check the latest setup logs and SQL error log. Focus on the first serious error (often marked with Error, failed, or return value 3) and address that specific cause (media, permissions, disk, localization, or sector size).

References:

Share via

Not able to install Microsoft SQL Express

2 answers

Your answer