I'm trying to install SQL Server 2014 but it stays in the same spot (Install_VCRuntime_Cpu32_Action) for hours. It's already the third time I'm trying to install so I don't know what else to do.
SQL Server 2014 Installation
Maybe a couple of hours. If you mean getting building a database for some sort of use, it could be a few hours for a simple one, to a number of months for a moderate sized one. I did one for half of the data in a medium sized company in approximately five months.
Uninstall the existing SQL Server and all the components from the add remove program. Backup the registry. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
To upgrade an existing instance of SQL Server to a different edition, from the SQL Server Installation Center click Maintenance, and then select Edition Upgrade. If Setup support files are required, SQL Server Setup installs them.
I had this same issue on SQL express 2014. When I went to check there was indeed a Windows Installer running. I killed that process & SQL proceeded to install just fine.
Found this here: https://community.spiceworks.com/topic/483582-ms-sql-2014-install-freezing
I observed this very same issue in one of my colleague's windows 10 box with SQL Server 2014 Enterprise installer as well. As mentioned in this MS connect bug you can try either of the below mentioned options:
I used task manager and killed the Windows Installer instances, clicked Retry and the installation completed. What a beat down.
You can kill the Windows Installer process as shown below:
It's fixed!
http://support.microsoft.com/kb/2820068
I tested this solution with 2014 express and can confirm that using /SkipInstallerRunCheck works as advertised. The installer no longer goes into an endless loop when it can't shut down msiserver.
For my colleague who was facing this issue with SQL Server 2014 setup, solution # 1 above worked.
Regarding SQL Server 2017 : My colleague faced exactly same issue on SQL Server 2017 also. We didn't see the "Windows Installer" app in processes tab on his machine. So we went with solution # 2 i.e. launch the installer as Setup.exe /SkipInstallerRunCheck
and it worked for him. While running from PowerShell console the command looks like .\Setup.exe /SkipInstallerRunCheck
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With