Archive. This is an archive of the Apple Support Community. Discussions are being restored and soon you will be able to read and post here again.

M4 Mac: Cannot empty Bin because com.apple.siriactionsd is in use

M4 Mac: cannot empty Bin—com.apple.siriactionsd “is in use”


Three Apple folders are stuck in my Bin, including com.apple.siriactionsd, which contains ShortcutsSandboxCache.


Emptying the Bin reports that com.apple.siriactionsd “is in use.”


I have already tried:

- Safe Mode, confirmed by “Boot Mode: Safe” in System Information.

- Force-quitting siriactionsd in Activity Monitor.

- Giving Terminal Full Disk Access, then quitting and reopening Terminal.


Inspecting ShortcutsSandboxCache with ls -ldeO@ fails with “Operation not permitted,” including when using sudo. Finder shows Locked unchecked and “You have unknown access.”


How can I safely remove these folders? What additional information would help diagnose this?

2 replies

com.apple.siriactionsd


It part of the Sealed and Read-Only Boot Volume


Yes, the primary siriactionsd binary and its launch agent plists are strictly part of the signed and sealed system volume.


  • The Sealed System Volume: Since macOS Big Sur (and fully maintained through macOS 27 Golden Gate), the core operating system files reside on a cryptographically Signed System Volume (SSV). This volume is completely read-only and sealed with a hash tree (Merkle tree) that the Mac validates at boot. Because siriactionsd is an official system daemon responsible for coordinating and syncing background tasks for the Shortcuts app and Siri AI, its executable code cannot be modified, deleted, or tampered with

com.apple.siriactionsd


So as my colleague @den.thed has suggested put it back


Why and how did you move those files to the trash...?

Put those folders/files back in there original location, startup in Safe Mode, then restart normally.


If you can not put those folders/files back or are having other issues...?

Make sure that you have a solid backup or two in place and then completely reinstall the macOS.


To reinstall the macOS, see > https://support.apple.com/en-us/102655