Bottom Line: It is **safe to clean up `$PatchCache
Bottom Line: It is **safe to clean up ** using official Windows Installer-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder) commands. Deleting the patch cache saves gigabytes on SSDs without corrupting installed software.
What is the $PatchCache$ Folder?
Located at `C:\Windows[Installer](/files/windows-installer-folder)$PatchCache
Bottom Line: It is safe to clean up PROTECTED_CODE_0 using official Windows Installer-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder) commands. Deleting the patch cache saves gigabytes on SSDs without corrupting installed software.
What is the $PatchCache$ Folder?
Located at , this hidden system folder is created by Windows Installer (MSI).
When you install service packs or software updates for applications like Microsoft Office or SQL Server, Windows Installer caches baseline copies of updated binary files in `$PatchCache
Bottom Line: It is safe to clean up PROTECTED_CODE_0 using official Windows Installer-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder) commands. Deleting the patch cache saves gigabytes on SSDs without corrupting installed software.
What is the $PatchCache$ Folder?
Located at PROTECTED_CODE_1, this hidden system folder is created by Windows Installer (MSI).
When you install service packs or software updates for applications like Microsoft Office or SQL Server, Windows Installer caches baseline copies of updated binary files in . This allows future patches to install faster without asking for original installation media.
Over time, `$PatchCache
Bottom Line: It is safe to clean up PROTECTED_CODE_0 using official Windows Installer-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder) commands. Deleting the patch cache saves gigabytes on SSDs without corrupting installed software.
What is the $PatchCache$ Folder?
Located at PROTECTED_CODE_1, this hidden system folder is created by Windows Installer (MSI).
When you install service packs or software updates for applications like Microsoft Office or SQL Server, Windows Installer caches baseline copies of updated binary files in C:\Windows\Installer. This allows future patches to install faster without asking for original installation media.
Over time, hoards 3 GB to 15 GB+ of duplicate installation files.
Can You Delete $PatchCache$?
✅ Yes, it is safe to disable and clear.
- No software uninstall: Installed applications continue to function normally.
- Safety rule: Do not delete files inside PROTECTED_CODE_2 directly, but clearing `$PatchCache
Bottom Line: It is safe to clean up PROTECTED_CODE_0 using official Windows Installer-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder) commands. Deleting the patch cache saves gigabytes on SSDs without corrupting installed software.
What is the $PatchCache$ Folder?
Located at PROTECTED_CODE_1, this hidden system folder is created by Windows Installer (MSI).
When you install service packs or software updates for applications like Microsoft Office or SQL Server, Windows Installer caches baseline copies of updated binary files in PROTECTED_CODE_2. This allows future patches to install faster without asking for original installation media.
Over time, PROTECTED_CODE_3 hoards 3 GB to 15 GB+ of duplicate installation files.
Can You Delete $PatchCache$?
✅ Yes, it is safe to disable and clear.
- No software uninstall: Installed applications continue to function normally.
- Safety rule: Do not delete files inside PROTECTED_CODE_4 directly, but clearing via
rmdiror command flags is completely safe.
How to Safely Clean Up $PatchCache$
Method 1: Disable and Clear PatchCache via Command Prompt (Admin)
- Open Command Prompt as Administrator.
- Run the command to disable $PatchCache$ creation:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v DisablePatchCache /t REG_DWORD /d 1 /f - Purge the `$PatchCache
Bottom Line: It is safe to clean up PROTECTED_CODE_0 using official Windows Installer-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder)-folder) commands. Deleting the patch cache saves gigabytes on SSDs without corrupting installed software.
What is the $PatchCache$ Folder?
Located at PROTECTED_CODE_1, this hidden system folder is created by Windows Installer (MSI).
When you install service packs or software updates for applications like Microsoft Office or SQL Server, Windows Installer caches baseline copies of updated binary files in PROTECTED_CODE_2. This allows future patches to install faster without asking for original installation media.
Over time, PROTECTED_CODE_3 hoards 3 GB to 15 GB+ of duplicate installation files.
Can You Delete $PatchCache$?
✅ Yes, it is safe to disable and clear.
- No software uninstall: Installed applications continue to function normally.
- Safety rule: Do not delete files inside PROTECTED_CODE_4 directly, but clearing PROTECTED_CODE_5 via PROTECTED_CODE_6 or command flags is completely safe.
How to Safely Clean Up $PatchCache$
Method 1: Disable and Clear PatchCache via Command Prompt (Admin)
- Open Command Prompt as Administrator.
- Run the command to disable $PatchCache$ creation:
rmdir /s /q %WinDir%\Installer\$PatchCache$ - Purge the folder: PROTECTED_CODE_7
Related Guides
- Learn about deleting Windows Installer folder.
- How to clean up MSOCache folder.
- Check if you can clean WinSxS folder.
Discussion
Loading authentication...