Thoughts from the EPS Windows Server Performance Team
Hello AskPerf – my name is Digvijay Nath, and I’m a Support Engineer on the Performance team in our Bangalore office. Today, I’m going to quickly cover the .MSP file used by the Windows Installer. The installer uses different file types to glean data about software installs, uninstalls and upgrades. So, let’s get started. There are a number of different files that are used:
As I mentioned above, the .MSP files contain information about updates to installed applications, as well as the versions of the applications to which the updates are applicable. The patch carries the metadata needed for applying the update and the updates files. These updated files are stored within embedded cabinet (.CAB) files. The files may be in whole, or in binary form. To explain, a patch in binary form is the byte-level difference between two files - .MST format). A patch package may only contain summary information and transform information and the cabinet files may be downloaded separately. In this fashion, only the necessary components needed for the upgrade are downloaded.
One of the advantages of patching an application that is already installed as opposed to doing a full install of the new version is that the patch only contains the bits required to update the application. This reduces the size of the file that needs to be downloaded or deployed. In addition, patching as opposed to reinstalling helps to preserve user settings and customizations. When installing a patch, the .MSP file is cached in %windir%\installer in the GUID folder that matches the registry entry in HKCR\Installer\Products. With Windows Installer 3.0 and later, any patches that contain the MsiPatchSequence table cause the installer to cache the original files being replaced into a baseline cache. This cache is used for patch uninstall operations since it stores the original files that were replaced. The original files can be copied back to their application folder locations as part of the patch uninstall process. The baseline caches are created separately for per machine and per user managed / per user unmanaged installs.
We have seen scenarios where the Installer folder is consuming large amounts of disk space. Although you may read advice on the internet that it is safe to delete files from this folder to recover disk space, we strongly advise against this course of action. These files are required for application repair, uninstall and reinstallation of patches – if the files are not there, then attempted actions against the applications will fail.
With that, we’ve reached the end of this post. Thanks for stopping by!
- Digvijay Nath
Thank you was a good article article will try to follow the continuous
Nice post Digvijay. Thanks for the information.
What can you tell us about how these files can affect the boot process? A Windows Performance Tool trace revealed to me that the Windows Installer service spent 9 seconds interacting with just one MSP file on my computer during the boot process. It spent another seven seconds on other MSP files. Can you provide any insight?
this is really what I needed
thanks you .)
this is really what I needed yous
very good about security