Q: Slow loading Finder in Mavericks?

I tried this and unfortunetly, nothing has changed.  I too am contemplating a return to ML although I am sure they will eventually work this out.

I too am having the same problem. I am running mavericks on my late 2009 imac with a 3.06ghz intel core 2 duo. Whenever I try to save any of my files or documents from any program the finder takes at least a few minutes to populate so I can navigate to where I want my files saved.

I have yet to try the fix rubyreddevon has suggested but when I do I'll repost the results.

I too have this issue, it has cause a few Finder crashes as well. While most annoying during "Open file" within an app, it's also done this just browsing through folders and even when I opened the trash to empty it.

Upon upgrade from 10.8, I thought perhaps somethings possibly got corrupted so I installed 10.9 fresh from USB drive after a couple days, but the issue is identical.

15" MBP 2012 w/256GB SSD, 8GB RAM i7-2.6Ghz Quad.

I am having the same issue. FInder will always load, but sometimes the delay can be 20 seconds long.

Also having this problem - finder windows can be very slow opening or updating.

11' MacBook Air 2013, 8 Gb RAM

Happens to me too. Brand new 27" iMac 3.5GHz i7, GTX780 GPU, 16GB RAM, 3TB Fusion drive.

When I try to open files in any app I get the spinning gear and it takes up to 20 seconds for the files to show.

I tried disabling app nap on indvidual apps via "get info" with no luck.

Can't even boot in safe mood. When I release the shift key I get the progress bar, screen turns black for a second, then it boots normally.

Someone mentioned clearing the kext cache and that didn't work either.

Hope they fix this soon.

Very aggravating...

Upgraded the day it came out, Love it! Battery has dramatically improved! Only has one issue....when I would load finder it would take sometimes 15-30 seconds to load the few files in my documents folder.

I tried

sudo defaults write com.apple.Finder NSAppSleepDisabled -bool YES

in terminal and it is fixed! Thanks rubyreddevon

Give this a try if you are having issues. It worked for me.

Spces:      Mid 2013 Macbook Air i5 w/4 GB RAM

                 Did not upgrade, btut clean Mavericks install from USB drive

                 No other issues (so far)

Hopefully they will send out an update and fix the other problems you guys are having.

I have the same problem on my machine too. 2012 MacBook Air, 13", 512GB, 8GB RAM. I actually had a chance to test the Mavericks beta in its early stages on my machine and this issue was present in the seed as well. I made Apple aware of it and I'm waiting for a response from their engineers to see what could be done about this issue. I find it rather annoying for when I'm using Photoshop or when I'm uploading a file in Safari. It happens all the time!

I have the same problem. Sometimes finder will take ~30ish seconds to load a folder that mountain lion had no trouble with

Same here. Since installing Mavericks, it takes 10-20 seconds to load finder contents, whether in desktop or from within an app. It really slows work down. Very irritating at the least, and also creates (hopefully) unfounded concerns about the integrity of my HD. As others have said it drags down the good stuff about Mavericks. I tried trashing the finder prefs - no change whatsoever.

My 2010 Mac Pro suffers from this as well.  When loading the contents of folders on an esata G-Speed Q.  It will take upwards of 10 to 20 seconds to display the files that used to display immediatly. 

Hopefully there will be a fix soon.

Pretty inconvenient.

Same here for me and my co-worker.  Finder loads slowly, but only certain folders with large amounts of contents in them, like the Downloads folder, for me, for example.

It migth be a reach, but check out Activity Monitor (in Applications/Utilities).  If you see a process called kernel_task using up huge amounts of memory, it might be the culprit for any slowing down of anything under the OS.  Mine seems to hit a wall at around 1 GB.  Before that it is slow but tolerable.  The only fix is to restart the Mac.  Apple has been aware of the problem for some time, but hasn't addressed it yet.