The application Finder.app can't be opened.

wafflelad wrote:
Yeah, it definitely seems related to external drives.

I experienced the same problem a few days ago, I don't have any external drive.

I'll throw my tuppence worth in.

Had the same issue with my time Machine Drive, WD My Book 500 GB F/W 800.
Time Machine stopped backing up, also at the same time,
Developed issues with GoogleUpdateInstaller asking for a system password every hour and;
EyeConnect crashing every 5 seconds according to Console.

UnInstalled everything google and updated EyeTV to latest version and those 2 problems went away.

Restarting left me with no finder until i unplugged the Time Machine Drive.
Re-Partitioned with GUID and many reformats of the drive - Not nice having no Time Machine - Still had the same issues.

Could sometimes get Time Machine to run about 100GB of backup's before Finder would crash again. Tried relaunching finder and the whole system would hang. Pulled the power on the HD and the system would jump straight back into life as though nothing was wrong apart from the -10810 error hiding in the background.

Thought it was the drive but looking at these messages there's something else going on, also can't help but think that it's not a coincidence that all three problems manifested themselves all at the same time????

Message was edited by: matt_film

Matt,

I too had suspicions about eyeTV. As I am still at my French house, I don't need eyeTV until I go back to the UK next week, so I disabled the eyeTV helper from my log in items. Did not make any difference. I will, like you, upgrade to the latest eyeTV V3 next week.

I have never liked Time Machine and had far too many problems with things like Sparse Image corruption etc. The Time Capsule connected via Ethernet to my iMac is working OK on Snow Leopard but I use Chronosync for scheduled back up, which also uses a lot less hard disc than Time Machine. This is important for me as my iMac is modified with a 1TB HD, with around 10,000 59MB TIFF images on it, so Time Machine would fill up a 1TB Time Capsule too quickly. The situation is only going to get more critical when I change from a Leica M8 to M9 next week where the Tiff's are 109 MB each.

I have now got Freecom working on this issue and they say they will liaise with Apple.

Wilson

I just had this problem hit me this evening. First the machine seemed to freeze (one app after another not responding, till nothing worked). I rebooted, went back to work, and within minutes found the same thing happening. Oddly, this time I noticed Spotlight busy reindexing my whole internal drive. I shut down (put iMac to sleep with the button, then pulled the plug). I then booted to Snow Leopard install disk and used Disk Utility to do a repair (it found one file and one directory missing). After the repair, I booted back to the internal drive and logged into my normal account.

This is when I first got hit with the "Finder.app can't be opened. -10810" message. Since finder would not open I launched TextEdit and then Terminal from my dock. I then noticed that Spotlight was again trying to index the whole disk. I launched System Preferences from the dock and turned off Spotlight altogether. I fast-user-switched to my admin account and found Finder working fine in that account. I fast-user-switched back to my usual account, still no dice.

After reading a number of messages in this thread I began to wonder if an FSEvents problem might be a common thread (Spotlight and Time Machine both use FSEvents heavily). I decided that although killing Spotlight had not solved the problem, maybe now that it was turned off Finder would work if I logged off and back on.

I logged out of my usual account, then logged back in. Finder was working. Spotlight is still off (I'm afraid to turn it on, even though I really appreciate the searching). I'm not sure if Spotlight is the "cause," to me this feels like a deeper 10.6.1 problem. But I thought I'd share this experience in case it helps anyone else.

I got the same -10810 error message.
There was crash of coreservicesd
It reports
------
Process: coreservicesd [103]
Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/Support/coreservicesd
Identifier: coreservicesd
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1]

Date/Time: 2009-10-01 13:49:04.371 +0200
OS Version: Mac OS X 10.6.1 (10B504)
Report Version: 6

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x90659eec CFBasicHashFindBucket + 108
1 com.apple.CoreFoundation 0x90659e43 CFDictionaryGetValue + 131
2 ...ple.CoreServices.CarbonCore 0x99121da8 SCSession::noteTaskGone(__CFMachPort*) + 56
3 ...ple.CoreServices.CarbonCore 0x99121d33 SCSession:: taskPortInvalidationMainThread(_CFRunLoopTimer*, void*) + 41
4 com.apple.CoreFoundation 0x9067deee __CFRunLoopRun + 6846
5 com.apple.CoreFoundation 0x9067bd34 CFRunLoopRunSpecific + 452
6 com.apple.CoreFoundation 0x906817a4 CFRunLoopRun + 84
7 ...ple.CoreServices.CarbonCore 0x990db53b _CoreServicesServerMain + 630
8 coreservicesd 0x00001f09 0x1000 + 3849
-------

Any hints?

Frank

I am afraid this is looking way beyond any user fixing. My guess is that a nasty bug has been introduced when Finder was rewritten to 64 bit. I am surprised to see all those Carbon errors, as I thought the coreservice was now Cocoa in Snow Leopard but then I am not in any way an expert in Apple API's.

Wilson

It seems to appear at very random intervals on mine. I've had entire days when it doesn't happen and then I'm plagued by it for hours.

I don't connect up any external HDs, I have very few 3rd party apps on and most of my crashes are in Mail and Finder .It's also happened in other user accounts on the same Macbook. I've deleted prefs. I've fixed disk permissions.
I've also reinstalled (and 6.1) and this hasn't fixed it. I've gone further than a mac user should be expected to go.

Judging by the number of times this thread has been viewed (and others relating the same error) I expect it has be appearing on Apple's radar as a major bug. Let's just hope they eventually acknowledge this and a fix is imminent.

exactly same thing happened to me just now when i plugged in my USB thumb drive.

I also had this exact same message occur under my new snow leopard install on a new Macbook pro 13. I was unable to do anything about it but manually shut the machine off. Thankfully it has not yet reappeared but it does seem from so many postings that this is a significant issue.

Same thing happened to me as I was trying to access my external hard drive. Not good. Can anyone at Apple confirm that you guys are trying to fix this?

Yesterday I made an "official" message to Apple via http://www.apple.com/feedback/

I have been leaving feedback on this for about 10 days, setting out the various things I have tried and looked at in an effort to resolve this problem. I have this awful suspicion that feedback may be routed straight into the floor level cylindrical filing system.

Wilson

I'm feeling like going back in time; the SL Finder crashes more often than the one in Mac OS 8... 😉

System 8? Uhhmmm... Am trying to remember just how stable System 6.0.7 was. Did the MultiFinder ever crash?

10 print "Tongue-in-cheek mode off"
30 goto 10
40 end

🙂

It has been some time since my initial trouble with the Finder. I use a couple of USB drives as backup and have not had a recurring problem with the "-10810" error. I am starting to think that the problem with the Finder does not have a link to external USB devices.

My internal drive did show directory damage after the incident BUT I am not certain that Snow Leopard (or the subsequent update) had anything to do with it.

Things are very stable now.