You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Kel Solaar Author

Level 1

5 points

The application Finder.app can't be opened.

I upgraded to Snow Leopard yesterday, and I'm having a lot of troubles, Finde, Time Machine and Disk Utility being the most annoying of them. I don't really know which one of them is making the others unstable / crash but well that's starting to be very irritating, now when I try to start the Finder I get this :

*The application Finder.app can't be opened.*
-10810

Restarting the Computer ( Mac Book Pro Uni ) usually fix that, but it's the second time that it's crashing a 220 go files package copy. I ended up doing it with rsync, the copy is still going on ( it will take a long time ) but I'm left with a Zombie Computer where I can't open a finder, and every Application that use it to open some file is crashing itself.

Is there a way to manually relaunch it ( I don't want to reboot, my computer is stuck backing up a lot of files ) ? I tried Sudo Launch the Finder from /System/Library/CoreServices/Finder.app/Contents/MacOS with no luck, any help would be appreciated.

KS

Message was edited by: Kel Solaar

Mac OS X (10.6)

Posted on Aug 30, 2009 12:35 PM

696 replies

Sp0k

Level 1

18 points

Oct 2, 2009 4:48 PM in response to Kel Solaar

Well, I had 0 (zero) issues once I downgraded to 10.6 from 10.6.1

Osmo

Level 1

0 points

Oct 2, 2009 6:35 PM in response to Sp0k

Macfixit have some solutions for us. Clearly this is VERY widespread for them to be reporting: http://reviews.cnet.com/8301-13727_7-10365239-263.html?tag=mncol;title

Oct 2, 2009 7:15 PM in response to Osmo

Very interesting. I didn't do a clean installation of Snow Leopard [this time] so this makes me wonder if that is related to the Finder problem.

Oct 3, 2009 1:34 AM in response to Rafael Figueroa

I have now tried two other things - I have rebuilt launch services - In Terminal copy and paste the following /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/Support/lsregister -kill -seed -rfv -all user, system, local

Secondly I have excluded my FW external hard disc from Spotlight searches. It is still not perfect but I am getting fewer lockups on wake from sleep with an external HD attached and 10810 less as well. I don't think this issue will be totally cured until we get an update - see here in Macfixit http://tinyurl.com/ybzvvr9

Wilson

Oct 4, 2009 2:30 PM in response to WilsonLaidlaw

I found a very simple solution. If anyone who got this error "The application Finder.app can't be opened. -10810" all you have to do is open terminal and type "killall Finder" and hit the enter key. Finder should restart and be back to normal. 🙂

I am not sure if this is a permanent solution but it worked for the time being.

Message was edited by: Brandon Kurtz

Calpa

Level 1

0 points

Oct 4, 2009 2:34 PM in response to Brandon Kurtz

Yeah dude; I really wish it was that simple 😉. Since the Finder wasn't running, there really wasn't anything for me to kill, ergo:"No matching processes belonging to you were found".

After deleting every related system pref file, rebooting a bunch of times, resetting some stuff, reinstalling 10.6.1.. creating a different user (even the guest account had no working Finder) the only thing that eventually worked for me was going back to Leopard (since I won't risk installing SL again and finding out the problem reappers after a couple of days untill Apple sorts out the problem).

There's only so much time one can work on a mac without a working Finder; for me it was three days untill I grabbed my OS 10.5 install dvd.

Message was edited by: Calpa

Oct 4, 2009 2:34 PM in response to Kel Solaar

Oct 4, 2009 2:35 PM in response to Kel Solaar

Oct 4, 2009 3:10 PM in response to Brandon Kurtz

The Killall solution is fine if you have a route into Terminal but sometimes with 10810 error is that you cannot open terminal, even through the usual backdoors like cmd-shift-U or via Spotlight.

Wilson

Calpa

Level 1

0 points

Oct 4, 2009 3:12 PM in response to WilsonLaidlaw

..I don't understand why this should work; the Finder wasn't running, that was the whole problem.. there was nothing to kill so the 'killall' command wouldn't do anything usefull.

Oct 4, 2009 11:30 PM in response to Calpa

If you get the 10810 error Finder is running but locked up, useless and may not be accessible. It may also be invisible and normally you also cannot open Force Quit either (Cmd-opt-esc). The killall solution will work but ONLY IF you can get into Terminal to run it. Spotlight will work some of the time to access Terminal - just type Terminal into it and click on Terminal in applications. If you are getting 10810 error locked Finder a lot, it may be worth setting Terminal to open at login and always be in dock.

Wilson

aladdin

Level 1

148 points

Oct 6, 2009 3:57 AM in response to Kel Solaar

I can confirm that the Finder problem is certainly related to an external drive in my case!

I'm using an external LaCie Rugged (selfpowered) FW drive which apparently causes the problem. While my Finder crashed several minutes ago, I tried all the Terminal (which luckily was still open) commands listed here, from killall over umount to reboot without any result. So I tried disconnecting the LaCie drive brutally and immediately the Finder was back, with multiple windows popping up (all the clicks I did before...) and, unfortunately, also all the Terminal commands being executed... including the reboot 😟

At least now I know... 😉

Calpa

Level 1

0 points

Oct 6, 2009 4:03 AM in response to WilsonLaidlaw

Well, that may be the case for some.. But when I got the error there was no Finder running, no active processes relating to it and therefore nothing to kill using the terminal (which I was able to run just fine using spotlight).

So perhaps there are 'mild' cases where the Finder is still running and locked-up; and the 'hard' ones where there just ain't anything there..

Message was edited by: Calpa

Oct 6, 2009 5:30 AM in response to Calpa

I see 10.6.2 beta was seeded to developers today. I sincerely hope that this horrible issue is tackled. Here is the Macrumors article on the beta http://tinyurl.com/y9ey75b . If it is not, I think I am going to have to revert to Leopard on my iMac, which has all sorts of external hard drives usually attached.

Wilson

Oct 7, 2009 7:57 AM in response to Kel Solaar

I've tried all of these work arounds but Finder still crashes a lot while using external drives. I've done a fresh install 3 times, added the drives to Spotlight's exclude list, upgraded and downgraded from 10.6.1 but still no relief. It seems to affect some drives more than others though. The Lacie and Iomga drives seem fine but a Gtech drive that I'm using seems to cause more crashes.

The application Finder.app can't be opened.