fatal error during installation (0x80070643) SQL Server MAnagement Studio: A valid destination folder for the install could not be determined

▲
4
▼

I am installing the Microsoft SQL Server Management Studio (17.2).

It was installed before, but I re-install it because I forgot the admin password (shouldn't do this actually).

However, the re-installation is not successful. The same error message occurs:

fatal error during installation (0x80070643) SQL Server MAnagement Studio: A valid destination folder for the install could not be determined

I've found one solution here

A valid destination folder for the install could not be determined when installing SQL Server Management Studio 2016

But it didn't work on my machine. I even couldn't find the BootstrapDir.

Any ideas what I might look for to solve this problem?

Thanks.

sql-server
sql-server-2008
smss
asked on Stack Overflow Sep 23, 2017 by Fzn • edited Sep 23, 2017 by TheGameiswar

4 Answers

▲
4
▼

Sorry for digging up this grave. If anyone has the same problem there is one registry key that blocks the instalation. Copying from this article. https://help.act.com/hc/en-us/articles/360024248314-Error-A-computer-restart-is-required-or-Reboot-pending-When-Attempting-to-Install-Act-or-the-Microsoft-SQL-Server-ACT7-Instance HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Control\Session Manager\PendingFileRenameOperations HKEY_LOCAL_MACHINE\SYSTEM\ControlSet[00n]\Control\Session Manager\PendingFileRenameOperations. This key can be a leftover sometimes and it signals the installer that there is a reboot pending after some other instalation. After deleting it installation goes without any problems.

answered on Stack Overflow Aug 10, 2020 by atomicicebreaker
▲
3
▼

Jumping ahead to 2020, this problem resurfaced for me while installing SSMS version 18. After many other suggestions did not fix the issue, I found that updating the version of Visual Studio Installer (VS 2019) to current version solved the issue. Since this error code shows up in many different install scenarios, but many different MS products also now share pieces with VS, I hope this might help someone else get to a solution faster.

answered on Stack Overflow Sep 28, 2020 by Gardoglee
▲
2
▼

I had the same problem and I "resolved" it by installing SSMS 16.5.3, which was successful. I then was able to install SSMS 17.2 without issue. After 17.2 is installed, 16.5.3 can be uninstalled.

answered on Stack Overflow Oct 5, 2017 by Bob Klimes
▲
2
▼

Simply make sure the bellow path is already created and exists on the designated machine!

"C:\Program Files (x86)\Microsoft SQL Server\130\Setup Bootstrap\"

answered on Stack Overflow Jan 17, 2019 by Mehrdad Alemi

User contributions licensed under CC BY-SA 3.0