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

Jefe317

Level 1

0 points

Oct 12, 2010 1:49 PM in response to Kel Solaar

For me the solution was disconnecting my Firewire cable going to my external hard drive and leaving it unplugged for a few minutes. This fixed the problem and I was able to relaunch the Finder.

Oct 19, 2010 12:36 PM in response to Kel Solaar

I have found that this happens to me when I try to access my iDisk and (for whatever reason) the Finder cannot access it. It just spins and spins, but never makes contact. Then my Finder will not restart, no matter how many kills/restarts/reboots etc.

I REALLY can't believe that no one at Apple has responded to this issue (that I can find, and there are LOTS of threads about it!!!!). I am extremely disappointed, after having been an Apple/Mac user for 34 years (yes, I had an Apple II+)... this is not what I like to see from Apple, Inc.

Maybe the 10.7 release will address this issue, but I'd rather not have to pay AGAIN to get BUGS fixed that are so prevalent. It is getting too Microsoft-like around here... and I don't like it one bit. (Pun intended.)

-Scott

Message was edited by: Scott Thompson11

glenn_uk

Level 1

8 points

Oct 24, 2010 5:18 PM in response to Scott Thompson11

I too find it hard to believe that Apple just can't be bothered to respond to this, less still fix it. Far too busy trying to shove that ghastly iTunes-10.0 down our throats, probably.

Nov 2, 2010 4:20 AM in response to Kel Solaar

Hi there, i just got this error after unmounting time capsule after getting to school. This caused the beach ball to start spinning in finder so i went to the dock and made it "relaunch", which gave me the error.

I repaired the permissions and now i have finder working again.

Cheers.

iGuy83

Level 1

0 points

Nov 3, 2010 9:43 PM in response to Kel Solaar

Hi all, I have the same problem, only with Networked drives.
Until Apple fix this bug i use this work around

Close the error message
Open up the Terminal application (use Spotlight if you dont have it on your dock)
Type: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder &
Press enter and... Ta-da.. Finder is playing nice again.
You can then close the terminal.

Here's hoping Apple figure out a fix soon.

Nov 5, 2010 11:09 AM in response to iGuy83

^ That works, until I close terminal and the Finder quits and desktop icons disappear instantly. I can do it again, same result when I close terminal. Hmmm....

Nov 5, 2010 12:10 PM in response to adrockmk2

see my post here to keep it open:

http://discussions.apple.com/message.jspa?messageID=12331981#12331981

Basically:

screen /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder

hasitha

Level 1

0 points

Nov 5, 2010 10:53 PM in response to jackoverfull

That worked like a charm! Cheers mate!

avhk

Level 1

8 points

Nov 8, 2010 7:47 PM in response to Kel Solaar

I'm and old time pc user. Just bought my first Mac today. Tonight it crashes with Finder error 10810.
Can't get a break. Anyone have any answers

Nov 8, 2010 8:01 PM in response to avhk

Do you have an external firewire hard drive attached? If so, try connecting it via USB2 instead. That was the issue for me.

Nov 11, 2010 1:05 PM in response to Max Correia

Mac OS X 10.6.5 update was released yesterday. This may help the issue, but no specifics are mentioned in the release notes. Check Software Update to download.

Nov 11, 2010 2:08 PM in response to umparrothead

I've been through 4 OSX updates since I started seeing this bug. Each time hoping that THIS one would be the one to fix it.

I'm not saying that 10.6.5 won't fix this bug, but I'm not holding my breath.

Nov 11, 2010 5:19 PM in response to Kel Solaar

I just started getting this after updating to 10.6.5. Always with network storage.

Nov 13, 2010 7:45 AM in response to RadioSnow

It hasn't fixed it. If anything it seems worse. I've got a feeling it'll never get fixed. They've got away with ignoring it for this long. Shocking.

kain2396

Level 1

0 points

Nov 13, 2010 2:41 PM in response to jackoverfull

So, while this isn't a fundamental fix, you don't need a screen session. Finder is launched under launchd, so in order to keep it alive, you need launchd to have control of it. This was actually simpler than I thought it would be. From the command line:

+launchctl submit -l Finder -p /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder+

If you check the Activity Monitor, it should show up (hierarchically) under launchd rather than one of your terminal sessions.

The -l is a label, and it seems to be arbitrary (I named it something obvious), so I don't know if this has an effect on Finder's behavior. Of course, Apple probably has other switches and arguments to Finder by default, but this should, at least, get you Finder back. Hope this helps.

The application Finder.app can't be opened.