Issue in the Installing the SQL Server

Question

Issue in the Installing the SQL Server

Dhivya Krishnan 0

Hi Team,

I'm using the Window 11 OS and the Processor - Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz, 2592 Mhz, 2 Core(s), 4 Logical Processor(s).

When i tried to install Microsoft SQL I was getting this error, please help me to resolve the issue.

User's image

Dhivya Krishnan 0 Reputation points

2026-07-30T17:44:54.1633333+00:00

Hi,

Hi All,

When i checked the logs in the path - C:\Program Files\Microsoft SQL Server\170\SSEI\LogFiles in the file "SSEI-Expr_20260730140611", im getting this error

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key Microsoft SQL Server to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key Uninstall to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_

(05) 2026-07-30 14:19:34 Sco: Unable to open hklm registry key SOFTWARE\Microsoft\MSSQLServer, error The system cannot find the file specified.

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key Microsoft SQL Server to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key Uninstall to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key MSSQLServer to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_

(07) 2026-07-30 14:19:34 Error opening installation log file. Verify that the specified log file location exists and that you can write to it.

Please help me to resolve it...

Thanks and Regards,

Dhivya R K
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-07-30T21:37:54.1666667+00:00

So why is want to write log files to the D: drive? Do you have a D: drive? Did you explicitly specify D: when you started the installation? Have you redefined ProgramFilesDir somewhere?

I can't say where the error is, but there is all indication that your machine/setup does not follow the regular template - and in most cases, that would be because you have been poking around yourself. We might be able to help you, but we need to know more details.
Dhivya Krishnan 0 Reputation points

2026-07-31T07:32:28.77+00:00

Hi @Erland Sommarskog ,

I have mentioned in any form to be in D: drive...

D Drive exists

Shortly will attach all the screenshots.

Thanks for your response.
Dhivya Krishnan 0 Reputation points

2026-07-31T10:03:08.05+00:00

1.     Uninstalled OLE

2.     Uninstalled SQL

3.     I downloaded everything will be shown

4.     Rebooting the system,

5.     Moved to C: drive

6.     Installing msoledbsql as Adminstrator

7.     OLE DB Driver installation is completed

8.     Now will begin the installation of SQL2025-SSEI-StdDev.

9.     Will use “Download Media” on these option Basic / Custom / Download Media

10. Choosen only these feature

If I cancel(Multiple) it, it will throws error

When I checked the logs in the path “D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260731_143622” I found the issue was

(18) 2026-07-31 14:36:53 SQLArcOnboard: IsItAzureVM cannot reach IMDS, exception System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 169.254.169.254:80

   at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)

   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)

   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

   --- End of inner exception stack trace ---

   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)

   --- End of inner exception stack trace ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at Microsoft.SqlServer.Configuration.InstallWizard.AzureDetailsHelper.<IsItAzureVM>d__5.MoveNext()

(16) 2026-07-31 14:36:53 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid

(16) 2026-07-31 14:36:53 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
Deepesh Dhake 820 Reputation points

2026-07-31T13:41:15.68+00:00
To find the real cause, could you do two things?

Let setup run all the way through without cancelling. You mentioned it errors when you cancel so if the errors only appear at that point, they may just be abort messages rather than a real failure. Seeing whether it completes or stops on its own will tell us a lot.

If it does fail on its own, please run this to surface the genuine error line: findstr /S /I /C:"Error result" /C:"return value 3" /C:"Watson bucket" /C:"failed with" "D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260731_143622*.log"
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-07-31T21:36:04.4566667+00:00

If you select Download Media that should not result in any error. But you could get errors in the next step. I'm sorry, but it is difficult to help when I don't know exactly what you are doing.

Can you check what is the value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ProgramFilesDir?

As for installing OLE DB separately, that may not be the best of ideas. I have the impression that if you have an OLEDB version which is newer than the one in Setup, Setup gets sad and fails.
Dhivya Krishnan 0 Reputation points

2026-08-02T15:02:19.7+00:00

Hi @Erland Sommarskog ,

I have the screenshot with the sequece.

I haven't installed OLEDB. I begin the installation of SQL2025-SSEI-StdDev. After begin my installation process selection also attached. But the logs shows same error. Not sure how to sort it out.

OLE DB is not installed.PFA
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-02T15:07:56.25+00:00

After begin my installation process selection also attached.

Hm, I can't see any such image.

Were you able to run Download Media?
Dhivya Krishnan 0 Reputation points

2026-08-02T16:34:06.4933333+00:00

Yes I'm able to downloaded media. PFA (Yesterday my task)

Downloaded successfully

This will download the SQLServer2025-x64-ENU file. Then I will run the setup file.

When i tried to install same error.

Could you please help me on this issue?
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-02T17:19:45.26+00:00

I'm trying to help you, but I am need to rely the information you share with me. I asked you to tell me the value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ProgramFilesDir, but you have not answered yet.

When you run the Setup wizard, when do you get this error?

I can see in the screenshot that you have a D drive, but there is a warning triangle. What does that warning say?
Dhivya Krishnan 0 Reputation points

2026-08-03T06:58:43.8033333+00:00

Hi @Erland Sommarskog ,

Even i got it, but not sure how to sort out this issue

When i tried to open the "REGEDIT" in run window. I'm able to open the "Registry Editor", Not able to find in the ProgramFilesDir under the CurrentVersion.

I download the software in C: and installed the software in C:\Users\kdhiv\Downloads. Please find the screenshot attached.

Running the software with Admin Rights

The path im finding as D: drive, is this one(Not sure how it was assigned)

Error came in while installation
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-03T08:43:29.26+00:00

Your problem is displayed in your first screenshot where you were looking in the wrong place. I have highlighted the critical part, which is on the right side:

Change this to C:\Program Files.

I like to add that with a fresh install of Windows, ProgramFilesDir is C:\Program Files, so the fact it has a different value suggests that Some One has deliberately changed it.

There may also be reason to investigate that warning triangle on the D: drive. Not that it should affect the SQL Server installation once you have corrected ProgramFilesDir, but it still looks spooky.

You may also want to search the registry from start to end for the string D:\ to see if there other settings relating to that drive.
Dhivya Krishnan 0 Reputation points

2026-08-03T12:22:52.3133333+00:00

Hi @Erland Sommarskog ,

When i tried to open the "REGEDIT" in run window. I'm able to open the "Registry Editor", able to find in the ProgramFilesDir under the CurrentVersion.

I download the software in C: and installed the software in C:\Users\kdhiv\Downloads. Please find the screenshot attached.

Downloaded

But now we are getting this error
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-03T12:25:21.59+00:00

When i tried to open the "REGEDIT" in run window. I'm able to open the "Registry Editor", Not able to find in the ProgramFilesDir under the CurrentVersion.

Please look more closely at my screenshot. ProgramFilesDir is a value directly under CurrentVersion, it is not a subkey. Look right - not down!
Dhivya Krishnan 0 Reputation points

2026-08-03T12:53:15.07+00:00

Hi @Erland Sommarskog ,

I apology i missed to with older image. Please find the details below :

Changed the “ProgramFilesDir” to C Drive

And restarted the system

Dowloaded the new SQL Server and did the installation

But now getting this error
"MDF compiler could not connect with the WMI Server"
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-03T14:05:34.3433333+00:00

Well, that's a completely different error. And an error which suggests that you are coming a lot further than the last time. I've seen people running to errors like this one before, but unfortunately, I don't know the solution. Then again, if someone had poked fun with ProgramFilesDir, who knows, maybe they have done more things which is not really healthy for the computer. I hope you realise that it is very difficult to troubleshoot things on a computer I don't have access to.

Is this computer your personal laptop, or are you trying to help someone else?

Before we give, you could share the log files. In C:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log there is one folder per setup attempt. Each folder has a number of log files. The ones of most interest are summary.txt and detail.txt. Can you attach these? (Please don't paste them into a posting window.)
Dhivya Krishnan 0 Reputation points

2026-08-03T14:23:04.69+00:00

Hi,

It is my personal laptop.

Please find the Summary_Dhivya_20260803_170638.txt and Detail.txt Detail file attached.

Thanks in Advance,

Thanks and Regards,

Dhivya
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-03T21:04:20.2833333+00:00

I don't have much hopes that I will be able to help you with this - this goes way outside my comfort zone. But as a last-ditch attempt, also upload the files sql_engine_core_inst_Cpu64_1.log and sql_engine_core_inst_Cpu64_loc_1033_1.log from the same folder.
Dhivya Krishnan 0 Reputation points

2026-08-04T07:18:23.2866667+00:00

Please find the file attached sql_engine_core_inst_Cpu64_1.log and I'm not able to find the logs sql_engine_core_inst_Cpu64_loc_1033_1.log.
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-04T07:48:32.2633333+00:00

I'm afraid that there is nothing in that log file that I can make sense from. I should point out that to understand these log files, I would need to have expertise in MSI installs and that - quite a different world from SQL Server.

It seems that your machine is not in best shape, and we've already seen a few other examples of this. (The changed value of ProgramFilesDir and the D drive with the warning triangle.) I don't know what you have been doing with it, but maybe you should consider to reformat and reinstall. SQL Server may not be the only software you will have problem installing.

The other alternative is look into creating a virtual machine and install SQL Server on the VM. Yet an alternative is to have SQL Server running in a container. Both these alternatives comes with a learning curve, but mastering virtual machines and containers is an asset in itself for a developer, so it is not a useless investment.

Also check out this article: https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size. It describes a problem you are not running into - because you are not coming far enough to run into it. However, it is worth to check out if you reformat or build a VM, so you avoid this issue in future install attempts.
Dhivya Krishnan 0 Reputation points

2026-08-06T08:25:16.48+00:00

Hi All,

Anyone know how to solve the below issue.

When i checked the logs it is showing the folder - 'SOFTWARE\Microsoft\Microsoft SQL Server\170\ConfigurationState' is not available.

Exit message: Cannot find registry key 'SOFTWARE\Microsoft\Microsoft SQL Server\170\ConfigurationState'.

Start time: 2026-08-03 16:49:43

When we checked **REGEDIT,**we are not having the key. PFA

Please help to resolve this error.

Space in the drive is more than 4KB
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-06T09:06:30.4333333+00:00

Still trying, eh? I noticed that error when I checked your logs earlier. I have the impression that you can get this error if you have made failed attempts previously and then attempted some random manual cleanups and messed things up. Since Setup continued, I did not focus on that error. But maybe this error has some relation to the fatal error that comes later.

Anyway, the second screenshot makes it painfully clear what your problem is: You need more disk space. I don't know on the top of my head what the format requirements are, but even if you were able to install SQL Server on those 9.4 GB you have left, there would be much space for the databases.

So you would need to clean up your disks quite a bit. But with only 182 GB on the C drive from the start and a warning triangle on the D drive... I hate to say this, but maybe it's time for a new laptop with bigger disks.

I realise that your budget may not permit this, but if you want to learn SQL Server, you could make use of the offer for a free Azure SQL Database. Although, the offer is limited so you may run out of credits after some time. But if you change the service tier to S0, the cost for the database is moderate. (And far less than a new laptop.)
Dhivya Krishnan 0 Reputation points

2026-08-06T10:07:23.5733333+00:00

Thanks for the Information..

3 answers

Your answer

Dhivya Krishnan 0 Reputation points

2026-07-30T17:44:54.1633333+00:00

Hi,

Hi All,

When i checked the logs in the path - C:\Program Files\Microsoft SQL Server\170\SSEI\LogFiles in the file "SSEI-Expr_20260730140611", im getting this error

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key Microsoft SQL Server to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key Uninstall to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_

(05) 2026-07-30 14:19:34 Sco: Unable to open hklm registry key SOFTWARE\Microsoft\MSSQLServer, error The system cannot find the file specified.

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key Microsoft SQL Server to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key Uninstall to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_

(05) 2026-07-30 14:19:34 Sco: Attempting to write hklm registry key MSSQLServer to file D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260730_140631\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_

(07) 2026-07-30 14:19:34 Error opening installation log file. Verify that the specified log file location exists and that you can write to it.

Please help me to resolve it...

Thanks and Regards,

Dhivya R K
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-07-30T21:37:54.1666667+00:00

So why is want to write log files to the D: drive? Do you have a D: drive? Did you explicitly specify D: when you started the installation? Have you redefined ProgramFilesDir somewhere?

I can't say where the error is, but there is all indication that your machine/setup does not follow the regular template - and in most cases, that would be because you have been poking around yourself. We might be able to help you, but we need to know more details.
Dhivya Krishnan 0 Reputation points

2026-07-31T07:32:28.77+00:00

Hi @Erland Sommarskog ,

I have mentioned in any form to be in D: drive...

D Drive exists

Shortly will attach all the screenshots.

Thanks for your response.
Deepesh Dhake 820 Reputation points

2026-07-31T13:41:15.68+00:00

To find the real cause, could you do two things?

Let setup run all the way through without cancelling. You mentioned it errors when you cancel so if the errors only appear at that point, they may just be abort messages rather than a real failure. Seeing whether it completes or stops on its own will tell us a lot.

If it does fail on its own, please run this to surface the genuine error line: findstr /S /I /C:"Error result" /C:"return value 3" /C:"Watson bucket" /C:"failed with" "D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260731_143622*.log"
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-07-31T21:36:04.4566667+00:00

If you select Download Media that should not result in any error. But you could get errors in the next step. I'm sorry, but it is difficult to help when I don't know exactly what you are doing.

Can you check what is the value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ProgramFilesDir?

As for installing OLE DB separately, that may not be the best of ideas. I have the impression that if you have an OLEDB version which is newer than the one in Setup, Setup gets sad and fails.
Dhivya Krishnan 0 Reputation points

2026-08-02T15:02:19.7+00:00

Hi @Erland Sommarskog ,

I have the screenshot with the sequece.

I haven't installed OLEDB. I begin the installation of SQL2025-SSEI-StdDev. After begin my installation process selection also attached. But the logs shows same error. Not sure how to sort it out.

OLE DB is not installed.PFA
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-02T15:07:56.25+00:00

After begin my installation process selection also attached.

Hm, I can't see any such image.

Were you able to run Download Media?
Dhivya Krishnan 0 Reputation points

2026-08-02T16:34:06.4933333+00:00

Yes I'm able to downloaded media. PFA (Yesterday my task)

Downloaded successfully

This will download the SQLServer2025-x64-ENU file. Then I will run the setup file.

When i tried to install same error.

Could you please help me on this issue?
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-02T17:19:45.26+00:00

I'm trying to help you, but I am need to rely the information you share with me. I asked you to tell me the value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ProgramFilesDir, but you have not answered yet.

When you run the Setup wizard, when do you get this error?

I can see in the screenshot that you have a D drive, but there is a warning triangle. What does that warning say?
Dhivya Krishnan 0 Reputation points

2026-08-03T06:58:43.8033333+00:00

Hi @Erland Sommarskog ,

Even i got it, but not sure how to sort out this issue

When i tried to open the "REGEDIT" in run window. I'm able to open the "Registry Editor", Not able to find in the ProgramFilesDir under the CurrentVersion.

I download the software in C: and installed the software in C:\Users\kdhiv\Downloads. Please find the screenshot attached.

Running the software with Admin Rights

The path im finding as D: drive, is this one(Not sure how it was assigned)

Error came in while installation
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-03T08:43:29.26+00:00

Your problem is displayed in your first screenshot where you were looking in the wrong place. I have highlighted the critical part, which is on the right side:

Change this to C:\Program Files.

I like to add that with a fresh install of Windows, ProgramFilesDir is C:\Program Files, so the fact it has a different value suggests that Some One has deliberately changed it.

There may also be reason to investigate that warning triangle on the D: drive. Not that it should affect the SQL Server installation once you have corrected ProgramFilesDir, but it still looks spooky.

You may also want to search the registry from start to end for the string D:\ to see if there other settings relating to that drive.
Dhivya Krishnan 0 Reputation points

2026-08-03T12:22:52.3133333+00:00

Hi @Erland Sommarskog ,

When i tried to open the "REGEDIT" in run window. I'm able to open the "Registry Editor", able to find in the ProgramFilesDir under the CurrentVersion.

I download the software in C: and installed the software in C:\Users\kdhiv\Downloads. Please find the screenshot attached.

Downloaded

But now we are getting this error
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-03T12:25:21.59+00:00

When i tried to open the "REGEDIT" in run window. I'm able to open the "Registry Editor", Not able to find in the ProgramFilesDir under the CurrentVersion.

Please look more closely at my screenshot. ProgramFilesDir is a value directly under CurrentVersion, it is not a subkey. Look right - not down!
Dhivya Krishnan 0 Reputation points

2026-08-03T12:53:15.07+00:00

Hi @Erland Sommarskog ,

I apology i missed to with older image. Please find the details below :

Changed the “ProgramFilesDir” to C Drive

And restarted the system

Dowloaded the new SQL Server and did the installation

But now getting this error
"MDF compiler could not connect with the WMI Server"
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-03T14:05:34.3433333+00:00

Well, that's a completely different error. And an error which suggests that you are coming a lot further than the last time. I've seen people running to errors like this one before, but unfortunately, I don't know the solution. Then again, if someone had poked fun with ProgramFilesDir, who knows, maybe they have done more things which is not really healthy for the computer. I hope you realise that it is very difficult to troubleshoot things on a computer I don't have access to.

Is this computer your personal laptop, or are you trying to help someone else?

Before we give, you could share the log files. In C:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log there is one folder per setup attempt. Each folder has a number of log files. The ones of most interest are summary.txt and detail.txt. Can you attach these? (Please don't paste them into a posting window.)
Dhivya Krishnan 0 Reputation points

2026-08-03T14:23:04.69+00:00

Hi,

It is my personal laptop.

Please find the Summary_Dhivya_20260803_170638.txt and Detail.txt Detail file attached.

Thanks in Advance,

Thanks and Regards,

Dhivya
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-03T21:04:20.2833333+00:00

I don't have much hopes that I will be able to help you with this - this goes way outside my comfort zone. But as a last-ditch attempt, also upload the files sql_engine_core_inst_Cpu64_1.log and sql_engine_core_inst_Cpu64_loc_1033_1.log from the same folder.
Dhivya Krishnan 0 Reputation points

2026-08-04T07:18:23.2866667+00:00

Please find the file attached sql_engine_core_inst_Cpu64_1.log and I'm not able to find the logs sql_engine_core_inst_Cpu64_loc_1033_1.log.
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-04T07:48:32.2633333+00:00

I'm afraid that there is nothing in that log file that I can make sense from. I should point out that to understand these log files, I would need to have expertise in MSI installs and that - quite a different world from SQL Server.

It seems that your machine is not in best shape, and we've already seen a few other examples of this. (The changed value of ProgramFilesDir and the D drive with the warning triangle.) I don't know what you have been doing with it, but maybe you should consider to reformat and reinstall. SQL Server may not be the only software you will have problem installing.

The other alternative is look into creating a virtual machine and install SQL Server on the VM. Yet an alternative is to have SQL Server running in a container. Both these alternatives comes with a learning curve, but mastering virtual machines and containers is an asset in itself for a developer, so it is not a useless investment.

Also check out this article: https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size. It describes a problem you are not running into - because you are not coming far enough to run into it. However, it is worth to check out if you reformat or build a VM, so you avoid this issue in future install attempts.
Dhivya Krishnan 0 Reputation points

2026-08-06T08:25:16.48+00:00

Hi All,

Anyone know how to solve the below issue.

When i checked the logs it is showing the folder - 'SOFTWARE\Microsoft\Microsoft SQL Server\170\ConfigurationState' is not available.

Exit message: Cannot find registry key 'SOFTWARE\Microsoft\Microsoft SQL Server\170\ConfigurationState'.

Start time: 2026-08-03 16:49:43

When we checked **REGEDIT,**we are not having the key. PFA

Please help to resolve this error.

Space in the drive is more than 4KB
Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-08-06T09:06:30.4333333+00:00

Still trying, eh? I noticed that error when I checked your logs earlier. I have the impression that you can get this error if you have made failed attempts previously and then attempted some random manual cleanups and messed things up. Since Setup continued, I did not focus on that error. But maybe this error has some relation to the fatal error that comes later.

Anyway, the second screenshot makes it painfully clear what your problem is: You need more disk space. I don't know on the top of my head what the format requirements are, but even if you were able to install SQL Server on those 9.4 GB you have left, there would be much space for the databases.

So you would need to clean up your disks quite a bit. But with only 182 GB on the C drive from the start and a warning triangle on the D drive... I hate to say this, but maybe it's time for a new laptop with bigger disks.

I realise that your budget may not permit this, but if you want to learn SQL Server, you could make use of the offer for a free Azure SQL Database. Although, the offer is limited so you may run out of credits after some time. But if you change the service tier to S0, the cost for the database is moderate. (And far less than a new laptop.)
Dhivya Krishnan 0 Reputation points

2026-08-06T10:07:23.5733333+00:00

Thanks for the Information..

Answer 1

The real error in your log is the last line: setup can't write to its log folder on the D: drive.

Please try, in order:

Confirm the D: drive exists and has free space. If it's missing, full, or read-only, that's your cause.

Test write access - open Command Prompt as Administrator and run:

 echo test > "D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\test.txt"

Fails then it's a D: access/space issue (the root cause).

Succeeds then D: is fine; likely admin rights.

Run setup as Administrator, or point it to a writable path:

setup.exe /INSTALLPATH="C:\Program Files\Microsoft SQL Server"

Answer 2

Deepesh Dhake 820

Your setup is failing on the step that installs the OLE DB Driver 18 (Install_msoledbsql18_Cpu64_Action). The most common cause is a newer version of that driver already being on the machine.

Please try this in order:

Uninstall existing OLE DB drivers - Control Panel then Programs and Features then remove any "Microsoft OLE DB Driver for SQL Server" (18 or 19), then reboot.

Run setup as Administrator (right-click then Run as administrator). SQL 2025 will reinstall its own driver cleanly.

If it still fails, check the real cause here:

   findstr /S /I /C:"msoledbsql" /C:"return value 3" "D:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log\20260729_165856\*.log"

Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator

2026-07-30T21:39:52.9066667+00:00

Deepesh, I think the setup fails in the pre-stage before the real setup starts, and maybe you have also realised that you were in error. I'm inclined to delete this first response of yours as it is more confusing than helpful. Please let me know.
Dhivya Krishnan 0 Reputation points

2026-07-31T08:05:40.78+00:00

Currently i don't have OLE DB Driver or SQL... Please find the screenshot...

Now will freshly download and install only install in the C Drive, Now i will install "SQL2025-SSEI-StdDev and vs_SSMS as an Administator.

Please let me know whether we have to follow anything else.

Downloaded as New one.PFA

Running as Adminstrator

Installed with the Download Media option

Downloaded successfully

Then run the file -

Installed as standard developer, skipped Azure Extenstion for SQL Server with below option installed

With Instance Name as "MSSQLServer", But getting this error

Please let me know how this has to be handled.

Answer 3

The screenshot shows the SQL Server installer failing very early with "Unable to install SQL Server (setup.exe)". The log snippet also shows a write attempt to the SQL Server setup bootstrap log path. On Windows 11, the supported path depends on the SQL Server version, and the next step is to identify the exact setup failure from the setup logs.

Use this path first:

Open File Explorer.
Go to: C:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log
Open the latest dated folder.
Check Summary.txt and Detail.txt / Details.txt.

If the failure is "Wait on the Database Engine recovery handle failed" or similar:

Open the SQL Server error log at: C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\LOG\ERRORLOG or for Express: C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\LOG\ERRORLOG
Look for a message about "256 misaligned log IOs" or misaligned reads.
If that message exists, the failure matches the known Windows 11 disk sector size issue described in Microsoft guidance.

If the setup media is damaged or corrupted, use these fixes:

Download the SQL Server image again from the original location, then rerun Setup.
If installing from a network location, copy the installation files to a local drive and run Setup from there.
If the log or error mentions Setup.rll, rename this file and rerun Setup: C:\Program Files\Microsoft SQL Server\1XX\Setup Bootstrap\SQLXXX\resources\1033\Setup.rll Rename it to setup.rll.old.
If using a localized SQL Server version, verify the operating system language settings are compatible. Different language versions of SQL Server instances on the same computer aren’t supported.

Also verify version support on Windows 11:

SQL Server 2025: supported on Windows 11
SQL Server 2022: supported on Windows 11
SQL Server 2019: supported on Windows 11
SQL Server 2017: supported on Windows 11
SQL Server 2016 and earlier: not supported on Windows 11

The processor shown is not the problem based on the provided information.

The most useful next action is to inspect Summary.txt and the SQL ERRORLOG for the exact failure point. If the error log contains the misaligned IO / sector size message, follow the disk sector size troubleshooting guidance. If not, the failure is more likely corrupted setup media or another setup-specific issue shown in Summary.txt.

References: