I scanned my Mac SSD with DaisyDisk. And in this folder -/Library/InstallerSandboxes/.PKInstallSandboxManager I found this file - 13C0DF80-42F3-4228-B301-C0913855E2FA.activeSandbox with 8GB size. I open this file and see 2 folders - root and boms. In root -> Applications I found Xcode.app . After searching on web, I found out that the PKInstallSandboxManage folder is responsible for updating applications. It turns out that in my “updates” folder there is an Xcode package that takes up 8GB and is not used? Can I remove it?

3 Answers 3


The answer to this is both NO and YES, NO you should never clear those temporary cache items yourself, but YES you can have Mac OS clear out the temporary files itself.

You should not modify or delete any of these folders:

.Spotlight-V100: Spotlight metadata for each mounted volume. The mdworker processes use this metadata to update Spotlight search.

.fseventsd: A log file of FSEvents logged by the fseventsd launchdaemon process. It monitors file system events, such as file creation, modification, deletion, and more. Time Machine uses this data to process backup in the background.

.DocumentRevisions-V100: macOS versioning database used by apps to save and retrieve different versions of a document.

.PKInstallSandboxManager: Used for software updates and sandboxing.

.PKInstallSandboxManager-SystemSoftware: Used for system software updates.

.Trashes: Trash folder in each mounted volume.

If for some reason you reboot the Mac and the temporary files and temp folders are still bloated with who knows what, you can reboot into Safe Mode by rebooting the Mac and holding down the Shift key, this performs additional measurements to get rid of temporary files and caches, when the Mac has finished booting into Safe Mode, rebooting back, as usual, should get things in check as expected.

And if you came across these folders because you’re running out of storage, check out some tips to free up disk space on the Mac, or do a file size based search, you’ll likely find something appropriate for recovering some space for your situation.

  • 1
    Yes, I came across these folders because I'm running out of storage. This problem appeared some time after the update on mac OS Catalina. And the subsequent Xcode Update. The fact is that my Xcode was not updated with using the App Store, so I had to download it from the developer's site. Maybe that's why I have problems with this now? Also I reboot my Mac into Safe Mode. But it is not help me. How to fix it?
    – User
    Dec 4, 2019 at 17:35
  • Hey @User did you deleted the files? If so the there was any problem doing so?
    – ooredroxoo
    Mar 10, 2021 at 18:12

I ran
sudo rm -rf /Library/InstallerSandboxes/.PKInstallSandboxManager
on my machine (macOS 11.4) since it gotten completely out of control with 200+ GB, which was mostly xcode app data.

No problems so far.


For an Apple Silicon M1 mini macOS Ventura 13.4 computer, the following steps worked for removing some multi-year-out-of-date ".PKInstallSandboxManager/UUID.activeSandbox" folders:

  1. Verify that the .PKInstallSandboxManager subfolders in question are truly obsolete and as such abandoned. In my case, these were years old and major revisions out-of-date.
### check dates
sudo ls -l /Library/InstallerSandboxes/.PKInstallSandboxManager
### check Boms
sudo ls -l /Library/InstallerSandboxes/.PKInstallSandboxManager/*/Boms
  1. Try the "reboot into Safe Mode" approach. Because, well, its a safe approach.

  2. Try sudo rm -rf … approach because this apparently worked in some prior use cases.

sudo rm -rf /Library/InstallerSandboxes/.PKInstallSandboxManager
# … operation not allowed.
  1. Try the max effort approach:

    sudo cd /Volumes//Library/InstallerSandboxes/.PKInstallSandboxManager
    sudo rm -rf UUID.activeSandbox
    ### repeat `rm -rf …` as needed.
    • Restore the mac to its original boot disk and security settings.

For me, only step 4 was successful in this Apple Silicon M1 mini macOS Ventura 13.4 computer scenario.

† Listed below is my experience with some SSD devices which did|didn't provide for a bootable macOS Ventura SSD drive. Your results may be different.

  • Created Ventura Bootable Drive OK
    • Crucial X8 External USB 3.2 Gen 2 Type-C Solid-State Drive
    • Oyen Digital "U32 Shadow" USB 3.2 Gen 2 Type-C Solid-State Drive
  • Not Successfully Ventura Bootable
    • Samsung T7 Shield Portable USB 3.2 Gen 2 Type-C Port Solid-State Drive
    • SD Cards
    • USB Stick

Test Update

macOS Ventura 13.4

  • Apple M1 arm: did install OK to external drive
  • Apple Intel x86_64: did install OK to external drive

macOS Ventura 13.5.1

  • Apple M1 arm: did not successfully install to external drive
  • Apple Intel x86_64: did install OK to external drive
  • I tried these steps, but could not get a bootable macOS installation on an external hard drive to work with my M2 MacBook Pro. However, that appears to have been overkill anyway: I had no trouble just deleting the files using the macOS Recovery Terminal.app. I disabled secure boot but did not explicitly disable SIP. Reenabled boot security with csrutil enable and everything appears to be working.
    – Jonathan
    Aug 24, 2023 at 2:36

You must log in to answer this question.

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