I've experienced the fairly common slow open and save dialog box issue that seemed to come about with Mavericks and stick right through Yosemite.

The following solution has worked temporarily for me:

1) In Terminal: rm ~/Library/Caches/CloudKit/CloudKitMetadata*;killall cloudd

2) In Activity Monitor: Force Quit cloudd

But the problem always returns. I wanted to share the above temporary solution, but also to see if anyone has come upon a permanent solution yet.

  • unfortunately this does nothing to me. NO effect-
    – Duck
    Commented May 28, 2020 at 19:31

1 Answer 1


I do not believe there is a permanent solution, since this problem has been out for far too long with little interest to fix it. I would recommend having that terminal script save as a .command stored in your dock that you would click every time you need it. To create a document that can do this for you:

  1. Open TextEdit.app
  2. Enter the following code into the document:

    rm ~/Library/Caches/CloudKit/CloudKitMetadata*;killall cloudd

  3. Save to a directory with the name "[a name that you would like].command"

  4. Open Terminal
  5. Type in chmod a+x BUT DO NOT HIT ENTER
  6. Drag in the .command
  7. Hit enter

Now you can drag in the command to your dock and click it whenever you need


Another idea is to use Automator.

  1. Open up Automator
  2. Go to the toolbar on the left and drag a execute she'll script
  3. Paste the code from above into the action
  4. Record a "Watch me Do" (by pressing the red record button in the top right) of:
    • Opening activity monitor
    • Seraching for cloudd
    • Clicking cloudd
    • Clicking quit
    • Selecting quit or force quit
      1. Set that to 1000x and save as an app
  • The file “KillCloudd.command” could not be executed because you do not have appropriate access privileges. (Permissions show me as Read + Write)
    – Octavian
    Commented Jul 14, 2015 at 22:39
  • Did you chmod a+x? Commented Jul 14, 2015 at 22:39
  • Yup. I'll try again.
    – Octavian
    Commented Jul 14, 2015 at 22:40
  • Because that error only happens for me when I forget Commented Jul 14, 2015 at 22:41
  • If it makes it any easier, move the .command to your ~(home) directory and run: chmod a+x KillCloudd.command Commented Jul 14, 2015 at 22:42

You must log in to answer this question.

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