I'm running Windows Server 2008 Standard running in VMware. It has 2 disks:

  • system disk: 16 GB
  • data disk: 500 MB

I installed Visual Studio 2008 SP1 + MSDN and some small tools and libraries that don't take much space. Over time the system disk's free space has been going down (I suspect because of regular system updates - NetFx (.NET), service packs, and regular updates).

Questions 1
How do you remove Windows Update uninstall files from Windows Server 2008?

Question 2
I also found lots of files in C:/Windows/Installer folder.
Is it possible to determine which .msp file goes with which patch?
I would like to delete some of them, because they do take a lot of space.


8 Answers 8


Associating the files with patches. The "WINDOWS\Installer\" folder has several key sub-folders.
You can search for the sub-folder name (without the braces {}) in the registry.

The key can be searched within the "HKLM\SOFTWARE\" tree
to get the Software association.

The key would be placed in the Installer sub-tree on the name ENU_GUID.

Similarly, in the registry path "HKEY_CLASSES_ROOT\Installer\Products\",
The key will usually match in a subtree against the "ProductIcon" name.
There will be a "ProductName" field next to it that will give you an association.

This search should be script-able with a dir WINDOWS\Installer /d output
stored to a text file that is processed with a registry search.

The .MSP files have a level of indirection in the registry.
You should search for the MSP name first in, HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\

That will give you a Patch number (the sub-tree name string) which is to be then searched again in the same path as above. The associated registry sub-tree will give you details for the patch.

Meanwhile, the mouse-over context in my Windows XP explorer also gives basic information on the patch. Have you checked that already?

Older data:
Use msizap to remove orphaned cached Windows Installer Data Files to increase free disk space.

Msizap is a command-line tool that can delete the configuration data that Windows Installer maintains for products that it installs, including the directories, files, registry subkeys, and registry entries in which Windows Installer stores configuration data.

Running msizap.exe with the G parameter removes orphaned cached Windows Installer data files for all users

The article discusses up to Windows Server 2003.
Update: This Microsoft KB description also limits at Server 2003.
It should work for Server 2008, or there would be another version for it.
The article describes existence of two versions.

There are two versions of MSIZAP.EXE:
MsiZapA.exe (for use in Windows 95, Windows 98 and Windows ME), and
MsiZapU.exe (for use in Windows NT, Windows 2000, Windows XP, and Windows Server 2003). The appropriate executable should be renamed MsiZap.exe.

Download references -- in case that link goes dead.

Msizap can be downloaded as a part of the Microsoft Windows Server 2003 Support Tools or the Windows Installer CleanUp Utility (EXE). I was unable to find the Windows Installer CleanUp Utility by searching Microsoft’s download site, so note that as of today the file’s name is msicuu2.exe if you the above link goes dead in the future.

If you don’t want to install the Windows Installer CleanUp Utility, use a program such as Universal Extractor (aka UniExtract) to extract the individual files. Once you extract the files, you’ll notice msizap.exe does not exist, but you will find MsiZapA.exe and MsiZapU.exe.

  • 3
    MsiZap is something I have run already. It only removes ORPHANED ones. I would like to know which MSP files are related to which patch to manually delete those. And I mean the ones that are not orphaned. And about Cleanup utility. I don't want to unsinstall patches and programs. I just want to remove their uninstall files (in XP you could just delete a bunch of compressed folders within Windows folder) Aug 13, 2009 at 12:17
  • @Robert, I get your point.
    – nik
    Aug 13, 2009 at 12:23
  • @nik: GUID folders usually contain smaller files. Ok. I'm able to determine those... What about .MSP files in Installer folder? Aug 13, 2009 at 20:32
  • 2
    Your solution about MSP files (with relation to registry) is correct that's why I awarded you with bounty points. Thanks nik. I was able to delete the big ones (ie. Office SP2 and others) and release a huge amount of disk space because I know I won't uninstall them. Aug 20, 2009 at 9:43
  • 1
    if you delete them then you will have trouble applying subsequent patches to those apps
    – JamesRyan
    Nov 24, 2010 at 12:39

For Q1, you mean just the normal Windows Updates files that get installed through Automatic Updates? You can free up that space by deleting the content INSIDE C:\windows\SoftwareDistribution\Download

The $NtUninstallKB folder in previous OS' doesn't exist in Windows 2008 so you can't just delete the uninstall files anymore.


16 GB is pushing it for a system volume for Win2008 - a fresh install with updates has taken up 15 GB on my 2008 VM. I am not sure about freeing up space within the system volume by deleting "unnecessary" files and folders, but the good news is it is a VM, it is Win2008, and you can actually make the system disk bigger quite easily because of these 2 things.

I am running a Win2008 VM on a standalone ESXi 3.5 box. To increase the size of the system disk:

1) Edit the VM properties and change the hard disk size to something larger (I'd recommend at least 40 GB or more to ensure you don't have to do this again)

2) Reboot the VM (you may not actually have to do this step, but I did on mine - seemed too crazy to be able to resize the system volume without rebooting since it is Windows after all...)

3) Go to Disk Management and you should see the extra space as X amount of unallocated space.

4) Right click your system volume and select "Extend Volume...". Go through the wizard to add the additional space to your system volume and you now have a larger one than you did before.

Goes without saying that you could also do this to your Data disk as well. Even if this wasn't a VM you could still add another physical disk and extend onto that although you may be creating a less fault-tolerant configuration unless you are extending onto a RAID volume. Because this is a VM, all ESX does is make the vmdk file larger.

  • thans, but that's not what I'm after. I'm using VMWare Workstation and there's "vmware-vdiskmanager" tool for this stuff. But I want to get rid of all garbage I don't need. My fresh install was around 11GB I think... or 12. But not more. It depends which features you installed. Aug 5, 2009 at 16:43
  • 2
    Not sure how this deserves a down-vote as it DOES provide a valid alternative to deleting Windows system files. Robert edited his question to say "No other possible solutions to free-up disk space will be considered." AFTER I already provided this answer...
    – August
    Aug 18, 2009 at 13:03

There are a number of things you can look at:

  • Run disk cleanup, this will clear out some space.
  • Next you can look at removing things like service pack and update uninstall files, if you are happy that these updates have worked and you won't need to remove them - see this article
  • If your page file is on the smaller disk you could look at moving it to the larger disk.
  • Disable system restore, if you are not using it

These are just a few I could think of, there are a number of good articles on the internet describing a variety of techniques for freeing space, some safe, some likely to destroy your windows install if you get it wrong, so beware!

  • I did run disk cleanup utility that freed up about 50MB... :( I was hoping to find some info on the link you provided, but it refers to Windows Server 2000 and not 2008... Aug 5, 2009 at 11:29
  • If you move away pagefile from the Install partition, Windbg symbol association ability will be lost. Matters if you want to track stray BSoD conditions better.
    – nik
    Aug 5, 2009 at 12:09
  • The process is the same for 2000, 2003 or 2008. As for the page file, you do want some page file on the C: drive for debug, but it can be minimal size
    – Sam Cogan
    Aug 5, 2009 at 14:10
  • @Sam: No, Server 2008 obviously uses a different folder location for update uninstall files. Aug 5, 2009 at 22:23

They changed the Servcing stack in Vista and 2008 so you no longer get the $NTUninstall files in your system dir like with previous Windows versions. It wedges everything in to the WinSxS directory to give more robust rollback and use-the-latest-version-of-a-file abilities.

Have a look at the Windows Component Clean Tool (compcln.exe) that comes with SP2 for 2008 or Vista, it'll ditch some files, but only frees up around 900MB for me. Still, better then nothing.


I would make a disk image of the system using Clonezilla and then go ahead and experiment. If things dont work out just restore the image and try again until you get it.


Files in C:\Windows\Installer are not related to patches or updates; they come with programs you install, and are needed for change/repair/uninstall oeprations (and sometimes for installing later updates to these programs, too).

You should definitely not delete them.

  • the installers for updates go in there too
    – JamesRyan
    Aug 18, 2009 at 14:46
  • APPLICATIONS updates, not O.S. ones; and they're anyway needed for change/repair/uninstall/upgrade of said applications.
    – Massimo
    Aug 18, 2009 at 16:19
  • although they may technically be applications, patches to things like .net framework and silverlight are downloaded by windows update and bunged in this folder automatically
    – JamesRyan
    Aug 19, 2009 at 12:05
  • Yes, and I keep suggesting not removing them, as they will be needed for every subsequent update to the same component.
    – Massimo
    Aug 19, 2009 at 13:00

Be very careful about deleting anything from the Windows and installer folder because these MSI files are required to install later updates. You can see what each one is by going into properties and looking at the version information. The biggest one will most probably be Visual Studio.

I am having the same headache on a bunch of Windows 2003 Server installations that were originally given 10 GB drives. It's a real pain that Microsoft have introduced this tactic of keeping every installer without giving us any heads-up on it.

The best thing I have found is to take a backup of the installer folder so that you can delete and replace them later as required by setup. But yeah, then you still have to waste time around working out which is which.

  • 1
    Interesting. Or at least compressing Installer folder. Thanks for the idea (still not a direct answer though) Aug 13, 2009 at 12:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .