Hello, You cannot be able to move $PatchCache$ to other drive. You can delete files under this directory if you want, and your applications will continue to run normally. DO NOT delete%WINDIR% Installer no matter how large it might be. Leave%WINDIR% Installer severely alone. I have found a work around for you: Click Start button, input “cmd” right-click command prompt and click run as Administrator. Type the following command to remove the Windows Installer baseline cache: rmdir /q /s%WINDIR% Installer $PatchCache$ You must stop the Windows Installer service for the change to take effect. You can set the MaxPatchCacheSize system policy to 0, so that the patch cache will not be created for this or any other products when patched.
To see “Freeing additional space” of the article: Hope it will help you! Hello, You cannot be able to move $PatchCache$ to other drive.
You can delete files under this directory if you want, and your applications will continue to run normally. DO NOT delete%WINDIR% Installer no matter how large it might be. Leave%WINDIR% Installer severely alone.
![]()
I have found a work around for you: Click Start button, input “cmd” right-click command prompt and click run as Administrator. Type the following command to remove the Windows Installer baseline cache: rmdir /q /s%WINDIR% Installer $PatchCache$ You must stop the Windows Installer service for the change to take effect. You can set the MaxPatchCacheSize system policy to 0, so that the patch cache will not be created for this or any other products when patched. To see “Freeing additional space” of the article: Hope it will help you! Hello, You cannot be able to move $PatchCache$ to other drive. You can delete files under this directory if you want, and your applications will continue to run normally. DO NOT delete%WINDIR% Installer no matter how large it might be.
Leave%WINDIR% Installer severely alone. I have found a work around for you: Click Start button, input “cmd” right-click command prompt and click run as Administrator. Type the following command to remove the Windows Installer baseline cache: rmdir /q /s%WINDIR% Installer $PatchCache$ You must stop the Windows Installer service for the change to take effect. You can set the MaxPatchCacheSize system policy to 0, so that the patch cache will not be created for this or any other products when patched. To see “Freeing additional space” of the article: Hope it will help you!
How to clean C Drive and reclaim more disk space in C: Windows directory or C: partition One of the ways to find out what files are taking up how much space is to run a free and program called which is available from Open Source Download site. More information about this program is available at When I ran WinDirStat program on my Windows 7 64 bit and Windows XP SP3 computers, I found a file called $PatchCache$ under the following directory to occupy large amount of space 2 to 3 GB (depending on the computer). C: Windows Installer $PatchCache$.
In one my machines, the C: drive (actually a partition on a larger drive) where Windows directory was located had only 10 GB total allocation (since it was a Windows XP SP3 machine and 8 years old), I needed to recover some space in the c: partition. This was made more important since I had less than 10% free space, making even defragmenting using “” not optimal. So I Googled the search-term “can i remove $PatchCache$”. The two following links came up as promising ones.
![]()
So I followed the instructions in the posts and I am repeating them here. Start AccessoriesCommand Prompt Don’t run it but right click it and Select Run as Administrator and say “yes” to the prompt and run it; if you simply run it and issue the next command, see below, you will get an error “Access is denied”. You need to be an Administrator to run it. In the command window type exactly the following command rmdir /q /s%WINDIR% Installer $PatchCache$ and hit return. After few seconds you will get the empty prompt again.
This means the $PatchCache$ directory has been cleaned. Subsequently, the space occupied by that directory should be free and you have now reclaimed some wanted space.
Morning All, I've been wrestling with a problem with our installer for a couple of days. It is a Basic MSI project, and for every build we change the Package Code, leaving the product code and version untouched (thus making this a 'Small Update' in installer parlance, I believe).
I noticed the other day that, following an upgrade using the latest installer, the binaries in my bin folder were not up to date. The were all showing a version number that was some 2 months old. On closer inspection of the MSI log I realised that it was getting the source files from a '$PatchCache$ folder, i.e.: C: Windows Installer $PatchCache$ Managed I've done much searching of these forums and other places and am no clearer on: 1. Why did the version from a couple of months ago get cached in the first place?
Trusted Installer Delete Windows 10
Download ezmix 2.1.1 full crack. Why is the installer now deciding that it should use this cache? The answer to #2 may be that the mere presence of the cache is enough to ensure it is always used. I'd like to think I'd have noticed before now, but the reality is that I may not have done. So, question 1 is possibly the most pertinent. I was hoping to not have to delve too deeply into the reasons for this, I wrote an installscript function to delete these files, but it failed to do so with an ACCESS DENIED (0x80070005) error (if I try to do it in windows explorer then I'm asked to provide admin privileges - I run the installer as administrator, but that doesn't seem to help). So, looks like I'm back to trying to figure out why the stuff got cached in the first place. I have only seen this behaviour once before (and only on one machine) so I don't think that my installer is always cacheing it's binaries.
Is anyone able to shed any light on this situation? In case anyone's reading this looking for an answer, I don't have one:-( I ended up writing a custom action to look for the patch cache folder and rename all the binaries in there to prevent them being used by InstallShield.
Was unable to delete them - did not have permission. Not nice, feels like I'm fighting InstallShield, but in the absence of any kind of indication from IS as to exactly what it was doing, I didn't have a lot of choice.
Next time I need any kind of installer I'm going to write a powershell script.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |