Rebuild installer cache

NET Framework 2. I was looped into the thread to diagnose the issue and found that the Windows Installer package and the patch package were both missing from the installer cache. Since a. Any patches that are registered from previous installs must also exist, so when any of these files are missing it is a big problem.

While only a couple of machines out of many exhibited this problem, it raised questions about why those files were missing. This does, however, yield a good opportunity to show how important verbose logs are when performing any Windows Installer action, as well as showing how source resolution works. If using Windows Installer 3. We could also use scripting. This way, the CCMCache will always be clean and will have enough space for other operations.

So, if the MSI is copied to a location that will not be interfered with, it will find the required source during any operation. As a downside to this approach, we can consider that during an upgrade, we need to make sure that we delete the previous MSI that was copied to the temporary location.

Otherwise, the client will be filled with unused MSIs. This is the solution we recommend - try to debug the MSI to find out why it is asking for media during the upgrade or uninstall operation. For repair operations, there is nothing to debug and you should use only one workaround for that scenario. It's worth mentioning that this debugging solution is not an exact science and it is not really meant for beginners. Most likely the issue will appear when a file that is the key of a certain component needs to be verified to see if the component is overwritten or not.

Make your job easier with our best practices guide for installation packaging. Caching in Windows Installer Folder - How does it work? The status of an MSI's digital signing process is represented in colors. For SQL Server installation, first use the repair process that's described in the following articles to verify your current installation:.

You should run the repair from the original installation media by using the following command line:. Repair the common shared components and features first, and then repeat the command to repair the instances installed.

During the process, the setup dialog box disappears. As long as the progress window does not show an error, the process is proceeding as expected.

If the installer cache file for a specific component is missing, the repair process will encounter an error. As an extra resolution, you can point the tool to the original media location and re-cache the missing files. This script is used against the source locations to make sure that all MSP packages are in the Windows Installer cache directory. After executing the commands indicated in the Action needed lines in the script output file, the missing packages will be re-added if the original source media is available.

Open the file from step 2 in a text editor such as Notepad, and identify the problems that cause the failure. To do this, search the text file for string patterns such as the following:. Look for more information about these steps in the Examples section. Repeat steps 2 through 4 until the text file that is created in step 2 no longer contains text that references invalid paths or missing files for the component that is being updated. The following examples are entries and explanations of actions that are outlined in the output file that is generated when you run the FindSQLInstalls.

The following is an example of the output that is generated when you are missing an. The Action needed line shows you the full path that must exist in order to update missing files for the original installation media:. The following section of the output advises you of actions that are required to resolve the missing files:. Missing patches may result in entries that resemble those in Example 1. This command forces the executable to extract the files to the previous missing location, and this re-creates the structure that is required to update the Windows installer cache with any missing files.

The actual location will vary, and a single patch such as a service pack may have to be extracted to multiple locations. Each installed product includes a section that contains the following information for Patches Installed:.

Best Smart Displays. Best Home Security Systems. Best External Solid State Drives. Best Portable Chargers. Best Phone Chargers. Best Wi-Fi Range Extenders. Best Oculus Quest 2 Accessories.

Best iPad Air Cases. Awesome PC Accessories. Best Linux Laptops. Best Wireless iPhone Earbuds. Best Bluetooth Trackers. Best eReaders. Best VPN. Browse All News Articles. Windows 11 Uninstall Clock. Teams Walkie-Talkie. PCI Express 6. Wordle Scams. T-Mobile iCloud Private Relay.