Open With reads "Fetching..." for over a minute in Yosemite

rswift's solution from StackExchange worked for me, thanks!

i.e. this command line in a terminal window:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -seed -r -f -v -domain local-domain user -domain system

I also see numerous errors in the terminal window as the command runs, but the results back in the Finder for Open With.... are super. The menu now immediately pops up fully populated, as expected.

Well that was like magic. The command lsregister resets the Launch Services database.

I ran it a second time for research purposes. It ran faster, but there are redundant errors and other items re-registered.

Thank you.

I use this command on Terminal and everything is working again!!!

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -seed -r -f -v -domain local-domain user -domain system

It works for a while then after a day or so it reverts back to a list with the same problems... or if you restart the computer.

Right click hangs in iPhoto as well.

Sadly this still occurs in 10.10.2...Apple?

Yes, like I said, it does work for a while, but if you restart your computer it reverts back, so you have to run it every time you restart. Also, it actually creeps up usually after about 5 day to a week with me. I think finder resets or something. Not sure.

I'm having the same issue on a 12 core 64gb Mac Pro. This should not be happening. I feel like the whole computer is lagging when this thing should be screaming fast.

Same problem here with the annoying, greyed out, take forever "fetching" since installing Yosemite. I unmounted my 500GB external drive (used for Time Machine) and now my program selection is instant, like it used to be. Interesting. As artemistravel said, it's "not a fix", just a workaround.

It has to do with spinning up sleeping hard drives to look for addition applications to "open with". Is there a way to tell Yosemite to only open things with apps on the hard drive you are using? I don't have any apps on the other hard drives but it still insists on spinning them up.

Upgraded my MacBook 2009 hd to ssd, then it appeared.

Use this command helps, thanks.

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister-kill -seed -r -f -v -domain local-domain user -domain system

OSX 10.10.3

I have been watching this thread for several months and nothing works permanently b/c Apple is either NOT paying attention or perhaps is too busy developing new items. For me, since this is all live fetched, it is a problem with some other aspect of "fetching" i.e.; does this process use Spotlight or the Spotlight underpinnings? I have a new Mac Pro (late 13) and have had this happening immediately (first day) after purchasing the computer. Anyone who reads this and has this problem "CALL APPLE" have it escalated, go through the process of Capture Data and this is what will work. EVERYTHING else is temporary.

I've made an app using automator that executes this command, hides & quits every time my mac starts.

This is perhaps the closest thing to a permanent solution to the "slow open with fetching time" that I've found! If anyone can improve on this program, please let us know!

OPEN AUTOMATOR:

<HIDE ALL APPLICATIONS>

<RUN APPLE SCRIPT>

tell application "Terminal"

do script with command "/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Launch Services.framework/Versions/A/Support/lsregister -kill -seed -r -f -v -domain local -domain user -domain system"

end tell

tell application "Finder" to set visible of process "Terminal" to false

tell application "Terminal"

delay 90

quit

end tell

THEN... System Pref > Users Group > Login Items > + > Select your automator app.

This should automatically run, hide, quit every time you turn on your mac!

So this always happened on my old macbook air. Now it's 2016 with a brand new iMac running the brand new Sierra and this still happens. Usually I need to click away and then try again. This is clearly an OSX issue that nobody seems to think is important enough to fix.

thank you this worked for me