![](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(118.4, 93%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EUJ%3C/text%3E%3C/svg%3E)
274 questions
![](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(19.2, 28.999999999999996%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGW%3C/text%3E%3C/svg%3E)
Also seems like Installation is failing on the machine where already have another instance of SQL Server running.
I was able to repro this. I did not notice this when I installed CTP 2.1 initially, because I always install CTPs on separate VMs.
My understanding of this error in general is that it occurs when you already have installed the OLE DB provider (or the ODBC driver when you get that error message) on the machine. And indeed this is the case here, since you got both with SQL Server 2022. I can see in my log files, that the path for the MSI file for MSOLEDBSQL is wrong; it seems to related to the older install package of SQL Server. The path for SQL 2025 CTP 2.1 is not the same as for SQL 2022.
Your case is somewhat different from mine, because there are underscores in the filename, that is MS_OLEDB_SQL_18.msi. It should be msoledbsql.msi. That's really wild. I see that you also have an instance of CTP 2.0 on your machine. Maybe that is the reason. Personally, I don't think that is a valid test case, because once SQL 2025 is RTM, the CTP instances are of no interest anymore.
I will bring this up with some contacts I have inside Microsoft. I will also refer them to this thread.