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.

User profile for user: Kel Solaar
Kel Solaar Author
User level: 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

Reply
696 replies
User profile for user: jackoverfull
jackoverfull
User level: Level 1
0 points

Mar 22, 2011 4:28 PM in response to jackoverfull

Happened again, this time in a slightly different way.
I was doing…ehr…"heavy" operations…that is, encoding videos with handbrake and moving several gbs to a local AFP share while practicing on a musical keyboard connected via midi, using garageband (and the VB3 hammond simulator).

after a while I tried to switch to the finder to see if the copy was finished, but at the pression of command-tab I heard the system alert sound. exposé still worked and the finder was still open, unresponsive, but in mulixfinder's menu no application was listed anymore and in the dock no light was lighted up.

I tried clicking on finder's icon in the dock and got 10810. Actually I got the same error from mail (already open) as well:
http://b4.s3.quickshareit.com/schermata20110322a1822png50084.png

I could use most of the functions of the applications already opened but not launch new application, i could interact with the windows by clicking on them to make them active, but could not access to menu bar functions different then the one of garageband (which was in the foreground when the thing happened…). I could not click dismiss the 10810 errors, but i was able to use almost every other menu or button on screen. Not the finder's ones, tough. I used ssh on another computer to connect to my mac and killed the finder, it restarted, but still i could not use it.

At the end i just waited for handbrake to finish (the copy seemed to be already complete) and rebooted via ssh.

I still have to update to 10.6.7, will do soon.

Message was edited by: Jack_Overfull
Reply
User profile for user: Angsty
Angsty
User level: Level 1
9 points

Apr 2, 2011 2:51 AM in response to Kel Solaar

Just had this happen to me this evening! I actually updated to 10.6.7 earlier today so this bug is STILL happening.

Actions: I was connected to my NAS and transferring files. I clicked on the Eject button for the NAS from the sidebar but the device would not disconnect. I tried the Relaunch Finder option, like everyone else has done, and same error: "The application Finder can't be opened. -10810"

No access to desktop, no finder, nothing, so looks like a reboot is the next step.
sigh

Surely obscure errors messages like "-10810" were an 1980's computer thing and our software has gotten smarter and friendlier when reporting error messages to us users since then, right?? ???

Ang
Reply
User profile for user: ajmacipad
ajmacipad
User level: Level 1
0 points

Apr 9, 2011 6:13 AM in response to Kel Solaar

I hit finder cannot open while trying to use time machine with an NAS box. Time machine never completed and the finder put out The application Finder.app can't be opened.
-10810.
I recovered the finder by disabling time machine and disconnecting the NAS. I remember this was a limitation of tm when it first was released. You could only use it with USB attached drives. It looks as if it still is.
Reply
User profile for user: ajmacipad
ajmacipad
User level: Level 1
0 points

Apr 12, 2011 4:49 AM in response to ajmacipad

My issue seems to be with the NDAS driver from Ximeta. If I plug into the USB port on my drive, the problem goes away. I verified the disk through the USB port with no problems found.
Uninstalling and reinstalling the driver does not fix the issue. Most likely this is a problem with Ximeta locking up the finder with a kernel call. I may try reseting the NDAS box back to the beginning and start over. I would most likely lose my data or i might just use the USB port.

If I turn off the drive when connected to the ethernet port it causes a panic, which I sent to Apple:

Interval Since Last Panic Report: 34361 sec
Panics Since Last Report: 4
Anonymous UUID: 2EB269BB-ED8A-400C-846F-45982756C6C0

Tue Apr 12 06:12:58 2011
panic(cpu 1 caller 0x4b9646): "sbflush: sb 0x8e608f8 so 0x8e60854 cc 0 mbcnt 2109541457 mb 0 mbtail 0 " "lastrecord 0\n"@/SourceCache/xnu/xnu-1504.9.37/bsd/kern/uipc_socket2.c:1241
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x5b5c3548 : 0x21b510 (0x5d9514 0x5b5c357c 0x223978 0x0)
0x5b5c3598 : 0x4b9646 (0x5d226c 0x5d2a51 0x8e608f8 0x8e60854)
0x5b5c35d8 : 0x4b9687 (0x8e608f8 0x0 0x5b5c3618 0x5b5c36bf)
0x5b5c35f8 : 0x4b3d27 (0x8e608f8 0x0 0x0 0x0)
0x5b5c3628 : 0x4b3da9 (0x8e60854 0x0 0x0 0x0)
0x5b5c3648 : 0x4b59f4 (0x8e60854 0x9 0x0 0x0)
0x5b5c36a8 : 0x4b5a40 (0x8e60854 0x1 0x5b5c36e8 0x5c830433)
0x5b5c36c8 : 0x5c82fd44 (0x8e60854 0x747e000 0x5b5c3718 0x131d9600)
0x5b5c36e8 : 0x5c83a5b4 (0x131d9600 0x1 0x9630d58 0x538cfe)
0x5b5c3718 : 0x5c83cea4 (0x747e000 0x9630800 0x1 0x5c85f780)
0x5b5c3748 : 0x5c841ddf (0x747e000 0x9630800 0x7c0 0x224fc5)
0x5b5c3f68 : 0x5c842a89 (0x8a47200 0x8cc24c0 0x0 0x0)
0x5b5c3fc8 : 0x2a06dc (0x8a47200 0x0 0x10 0x6bbadc4)
Kernel Extensions in backtrace (with dependencies):
com.ximeta.driver.NDASFamily(233)@0x5c824000->0x5c86cfff
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(2.6.5)@0x5b65e000
Reply
User profile for user: JaxxLatraishe
JaxxLatraishe
User level: Level 1
0 points

May 17, 2011 7:44 PM in response to Kel Solaar

HI Everyone,


ok first of all, I really cant believe that this tread is 40 pages long, and each page has an average of 8 posts ' whats that, like 600 posts? and still no answer.


as of right now and after 24 hours of diagnosing, troubleshooting and just plain getting frustrated i am re installing the whole system again.


im on a macbook pro late 2009 15" 2.8 2g ram ' anyhow just over day ago i got the misterious message (10810)

from reading previous post both on the net and here on the apple site i think it might have started due to a malfuncition with a usb key and accesing my iphone via "conect to..." instance...


but my situation got much worse than anything ive read so far.

i could not open anything, thus not being able to back up my important stuff for a clean reintall.

no apps were able to run, my computer was taking a very long time launching.


i tryed everything, deleting all the launch files and finder prefs. Also, creating and writing terminal shortcuts and little apps, updating to the lastet os version (10.6.7) and nothing. very very frustrating.


well, im now waiting for the installation to finish. will write as soon as it does.

but one thing is still bothering me, will everytime an external unit or something corrupts the system and we find this error, are we going to have to reinstal and start over?


im really hoping for Apple to get back to us, with some help


thank you for your time.


Best regards


Jack Alalu

Reply
User profile for user: mopppish
mopppish
User level: Level 1
10 points

May 23, 2011 6:36 AM in response to Kel Solaar

I'm on 10.6.7 and this problem with Finder is killing me.

In my case, it is very clearly tied to the use of an external Lacie Rugged drive that I use over firewire.

Unfortunately, 99% of the time that I'm using this drive, it's with Logic Pro. This made it difficult to pin the problem down at first as I assumed it was an issue with Logic, but further investigation confirmed the drive was the problem.

NONE of the terminal fixes work for me. Last night, after trying everything I could think of, I logged out, at which my computer hung. Desperate to avoid another forced shutdown, I unplugged the Lacie and my computer IMMEDIATELY became responsive again, giving me the "disk was improperly ejected" notice.

I'm fairly confident that the drive is not faulty as I've run verifications on it and can use it for long stretches of time without a problem. MOST of the time when the dreaded freeze occurs, it's when I've walked away from the computer for a while and let the drive spin down, but occasionally it has actually happened in the middle of a recording.

I'm willing to do an archive an install at this point and, if it becomes necessary, a complete erase and install.

Can anyone confirm that this will or will not work?

Reply

The application Finder.app can't be opened.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up