How to resolve install failures for SQL Server 2022 Developer edition

Question

I have been trying to install SQL Server 2022 Developer edition without success. After more than 10 attempts I am at a complete loss as to what to do next. I have attached the log of my last attempt and hopefully someone can shed some light on my issues and help me complete the SS 2022 install successfully. Before embarking on the last install I did the following 1 Removed all SQL Server components from 'Programs and Features' - excluding those used by Visual Studio 2 Backed up the registry 3 Deleted the following keys using regedit: (a) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server (b) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer (c) For HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, I deleted all the sub-keys referencing SQL Server (d) For HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services, I deleted all the keys that referenced SQL Server 4 Finally, I Restarted the machine before trying to install the latest version of SS for developers. Having endlessly searched the internet, I can see that I am not the only one in the asylum. Help! ScreenShot.pdf Summary_SamaanTree_8500_20240218_093518.txt

Answer 1

The failure appears to be related to the insufficient permissions to modify the file system ACEs. Try disabling fully (but temporarily) UAC (disable the User Account Control: Run all administrators in Admin Approval Mode policy setting), ensure that you launch the installation using the elevated privileges, and re-run it hth
Marcin

Answer 2

This seems to be where things break down:

(01) 2024-02-18 09:45:56 Slp: Running Action: Slp_Config_Install_Core_WMI_Provider_Cpu64
(01) 2024-02-18 09:45:56 Slp: Action Data:
(01) 2024-02-18 09:45:56 Slp:   Feature = CommonFiles_sql_common_core_Cpu64
(01) 2024-02-18 09:45:56 Slp:   Scenario = install
(01) 2024-02-18 09:45:56 Slp:   Timing = ConfigNonRC
(01) 2024-02-18 09:45:56 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate
(01) 2024-02-18 09:45:56 Slp:   ServiceMode = WMIProvider
(01) 2024-02-18 09:45:56 Slp:   FeatureName = CommonFiles
(01) 2024-02-18 09:45:56 Slp:   FeatureCpuType = Cpu64
(01) 2024-02-18 09:45:56 Slp:   FeaturePackageId = sql_common_core
(01) 2024-02-18 09:45:56 Slp: Installing WMI Provider
(01) 2024-02-18 09:45:56 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2024-02-18 09:45:56 Slp: Sco: Attempting to open registry subkey 
(01) 2024-02-18 09:45:56 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\160
(01) 2024-02-18 09:45:56 Slp: Sco: Attempting to get registry value SharedCode
(01) 2024-02-18 09:45:56 Slp: SharedDirPath is 
(01) 2024-02-18 09:45:56 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2024-02-18 09:45:56 Slp: Value cannot be null.
Parameter name: path1
(01) 2024-02-18 09:45:56 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2024-02-18 09:45:56 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2024-02-18 09:45:56 Slp: System.ArgumentNullException: Value cannot be null.
(01) 2024-02-18 09:45:56 Slp: Parameter name: path1
(01) 2024-02-18 09:45:56 Slp:    at System.IO.Path.Combine(String path1, String path2)

It tries to read from the registry, but it seems that it comes back empty-handed.

Then again, this is not the first exception in the file, nor is the last. But the ones before are very early and related to performance counters. They are usually benign and do not cause installation to fail. And later exceptions may be due to this exception.

Since you say that you have been deleting registry keys etc, I suspect that you have messed things up so that Setup gets confused. It would be kind of interesting to see your first detail.txt, as that could give information about the original error. Then again, that information is only useful, if you are able to bring back the machine to the original state.

You could try following this article: https://www.sql-easy.com/learn/how-to-uninstall-sql-server/ Another poster I tried to help found this article, and he was actually eventually able to install SQL Server successfully after following this article (and addressing what the original root cause in his case).

But it may be a better option to create a virtual machine and install SQL Server on the VM.

I asked for the ERRORLOG file, because sometimes Setup fails when SQL Server does not start when Setup is to run configuration actions, and in that case, that file has the answer. But Setup may fail at an earlier stage, in which case you don't have that file.

Answer 3

Hi @Robert Higgins, You may follow the steps to uninstall the failed installation and reinstall it. Please follow the below steps to remove all components of previous installed SQL Server completely: 1. Remove all SQL Server components from 'Programs and Features' 2. Backup the registry 3. Delete the following keys in regedit: --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer 4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server 5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server 6. Reboot the machine In addition, please use an administrator account to reinstall SQL Server on your computer(Right click->run as administrator). Regards， Zoe Hui

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Answer 4

Click on link: https://youtu.be/tlf1kQOzQjw