Here’s something that seems to keep coming up, but not frequently enough for me to write a blog post about until now:
You should not install SQL Server from a mounted ISO file. Instead, you should extract the contents of the ISO file first before installing it.
In June 2019 I tweeted:
[…] some ISO files need to be extracted to install the software that’s on them. Mounting them as a virtual device doesn’t always work.
In the old days, software used to be distributed on physical media like diskette, CD, and finally DVD. Nowadays we download and install software as standalone files. Even enterprise software like SQL Server is available for download in this way, usually distributed as an ISO file. Once you’ve downloaded it, you can mount that ISO file as a virtual drive and access it as though it was on physical media.
Or you can do the right and proper thing, and extract the ISO file to a network drive or local storage first, using a tool like 7-Zip.
In my professional experience, there appears to be a problem with how SQL Server is packaged, which can randomly cause the installation to fail. Either there is a bug in the ISO maker, in the virtual device driver, or in the number of files. I don’t know for sure. It doesn’t seem to matter if you use the built-in feature in Windows Explorer (also known as File Explorer), or a third-party ISO mounting tool like Virtual CloneDrive; every so often you will run into an installation problem that is resolved by extracting the ISO and trying the install again from the extracted files.
Perhaps I’ve installed SQL Server so many times that the odds were higher for me to run into this problem, so I hope this heads-up helps someone!
Share your installer woes in the comments below.