Windows XP $PatchCache$ folder

[Frank D. Nicodem, Jr.]

I'm noticing a number of folders in my C:\Windows subdirectory structure
that are growing quite large, and I'm wondering which -- if any -- can be
deleted. I try, whenever possible, to NOT install any software on my C:
drive, but prefer to keep it for "system" files, and install all
applications in other partitions. Yet my C: drive continues to grow -- it's
not around 7GB of files.

I know there are several "installer" folders -- i.e., where various kinds of
files are kept after an application is installed (frequently by
InstallShield). And, from my experience, many of those need to stay,
because they are used for uninstalling the application, or other purposes.
But there's one folder I cannot find an explanation for.

Under my C:\Windows folder, there's a subfolder called "Installer". And in
that folder alone there are over 100 files, comprising 200MB of space.
Then, under that folder, there is a subfolder named "$PatchCache$". There's
almost another 200MB in that folder, as well. And when I look at the files
there (i.e., in $PatchCache$), there is not a single file that isn't at
least 2 years old! What are these files, what put them there, and do I need
to keep them?

On a related note, are there other folders in the C:\Windows hierarchy that
just keep unnecessary installation information, and can be deleted? (E.g.,
what about all of those dozens and dozens of "$NtUninstallKBnnnnn$" folders
that result from running Windows Update?)

Any help appreciated.
-------------------------------------------
Frank D. Nicodem, Jr.
[email protected]

[Ramesh, MS-MVP]

Hi Frank,

Not sure about the $PatchCache$ and which application creates those folders.
Is there a text based file present in that folder (.INF files or similar)?
If so they may give you a clue.

Regarding $NtUninstallKBnnnnn$ folders:

The $NtUninstallKBnnnnn$ folders contain the uninstall information and the
backup files needed to undo a Hotfix. If your system is stable, and you no
longer plan to uninstall an update, then the $NtUninstallKBnnnnn$ folders
can be deleted. If you're concerned, you can burn the folders to a CD and
delete them from the hard drive.

$NTUninstall folders - Description:
http://windowsxp.mvps.org/hotfix_backup.htm

Tidying up after installing SP2
http://aumha.org/win5/a/sp2faq.php#after

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows XP Shell/User]
Windows® XP Troubleshooting http://www.winhelponline.com


"Frank D. Nicodem, Jr." <[email protected]> wrote in message
news:%23GXp%[email protected]...
I'm noticing a number of folders in my C:\Windows subdirectory structure
that are growing quite large, and I'm wondering which -- if any -- can be
deleted. I try, whenever possible, to NOT install any software on my C:
drive, but prefer to keep it for "system" files, and install all
applications in other partitions. Yet my C: drive continues to grow -- it's
not around 7GB of files.

I know there are several "installer" folders -- i.e., where various kinds of
files are kept after an application is installed (frequently by
InstallShield). And, from my experience, many of those need to stay,
because they are used for uninstalling the application, or other purposes.
But there's one folder I cannot find an explanation for.

Under my C:\Windows folder, there's a subfolder called "Installer". And in
that folder alone there are over 100 files, comprising 200MB of space.
Then, under that folder, there is a subfolder named "$PatchCache$". There's
almost another 200MB in that folder, as well. And when I look at the files
there (i.e., in $PatchCache$), there is not a single file that isn't at
least 2 years old! What are these files, what put them there, and do I need
to keep them?

On a related note, are there other folders in the C:\Windows hierarchy that
just keep unnecessary installation information, and can be deleted? (E.g.,
what about all of those dozens and dozens of "$NtUninstallKBnnnnn$" folders
that result from running Windows Update?)

Any help appreciated.
-------------------------------------------
Frank D. Nicodem, Jr.
[email protected]