The application Finder.app can't be opened.

Same here -- i.e. problem not solved yet for me either.
That is, using Terminal and entering:
"/System/Library/CoreServices/Finder.app/Contents/MacOS/Finder &"
(without quotes)
is still NOT working for me, either. Or, to be more specific, it does bring the Finder back to the list of "Running" applications (listed in the "Force Quit Applications" window) but Finder is still showing as (not responding) and no finder windows will open. Plus I still get the 10810 error message (if I get anything at all) when trying to open a finder window.
I've had to manually shut my MacPro off by holding the power button for ten seconds and then waiting and turning it back on every single day for a couple of weeks when I come into the office.
The strangest thing to me is that EVERYTHING else works except the Finder.
Any other suggestions?
Thanks Sincerely,
KG

I'm having issues every other day, but not just with Finder. My iMac (bought in October 2009) hangs about every other day.

I'm running in 64-bit mode and am wondering if this is why I have all these problems.

I'm wondering how many people here are running in 64-bit mode?

Go to Applications / Utilities / highlight "software" and look for this line in the right pane:
64-bit Kernel and Extensions: Yes

If it says "No", you're running the 32-bit Kernel and Extensions. When I bought my mac, it came set up with 32-bit... I had to manually make it run in 64-bit, even though it has 64-bit hardware.

-Brian

I'm running 10.6.2 in 64-bit mode and didn't have a problem until I started using a HD attached to my Airport Base Station Extreme (ABSE) for TM backups and file sharing. I have a wired ethernet connection to the ABSE but left my wireless on as well. At first it worked very well, then I went on a trip with my Macbook and when I came back TM couldn't open the attached drive. I manually connected and it would work for a while, then the backup would fail, finder would freeze, and I'd get error after trying to restart Finder.

I've found that if I restart my network services I'm able to restart finder with no problems, but I still get this every now and then. The frustrating thing is I cannot duplicate the situation at will.

Hello,
It may be that running your iMac in 64-bit mode is causing unrelated problems - or it may not be. If your Mac "hangs" (aka, "freezes"), then I don't see the connection with Finder crashing and failing to relaunch (Error -10810).

So the question I'd ask myself is whether I need to run an iMac in 64-bit mode. As you say, the factory default setting is 32-bit mode. The reason is that few applications are adapted to 64-bit mode and those that are usually operate properly only if "huge" amounts of RAM are available. By "huge" I mean a lot more than the usual 2-3 GB (up to 32 GB can be used with 64-bit mode).

You may like to look at this thread for a simple explanation of the reasons for wanting/needing 64-bit mode.

http://discussions.apple.com/thread.jspa?messageID=10897018&#10897018


As for the hangs you mention: it could be that some apps which are not written for 64-bit are "behaving badly" in that mode. Or - it could be some other problem which you'd need to start tracing. If you continue to have that problem (as distinct from Error 10810), then you might want ot start your own thread on Apple Discussion, giving the details.

Regards

Message was edited by: macnoel

++Go to Applications / Utilities / highlight "software" and look for this line in the right pane:++
++64-bit Kernel and Extensions: Yes++

No at all sure what you mean by this. There is no application called "software" in utilities - can you explain what you mean?

Wilson

sorry about that Wilson - I left out "System Profiler"

Apps / Utilities / System Profiler /

Once in system profiler, highlight the "Software" group heading in the left pane, and look at the right pane for 64-bit Kernel and Extensions: Yes

The machine on which I am getting the 10810, is not 64 bit capable (it is a 5,1 iMac), so this issue is not resolvable for me with this "cure". I do wonder however if there is something in it, as the syslogs do seem to show a 32/64 bit conflict within the Carbon Coreservices area. I am not getting the issue on my 2009 2.53gHz 13" Macbook Pro, which I am guessing is 64 bit capable. I cannot check at the moment, as it is away having a new keyboard under warranty, after two thirds of the lighting failed.

I do still wonder if Apple made an error moving away from Power PC processors. Our G5 machines (PowerMac server and iMacs) just churn away day in, day out with never any problems, glitches, crashes, connection time outs, spinning beach-balls etc. They are 99.99% stable. The Intel machines are a very different story.

Wilson

For those that are still having problems, I have achieved a level of stability by simply turning off spotlight indexing entirely:

sudo mdutil -i off -a

You will lose spotlight abilities until the actual problem gets fixed. I have been running many, many traces since I have a very repeatable case of this problem. The spotlight indexer (mds) launches a bunch of processes (mdworker, mdworker32) to index the drives. At some point, one of these workers encounters a file that causes it to go catatonic and coreservicesd to crash. As was pointed out before, coreservicesd currently has a bug that doesn't set the version correctly and it doesn't allow anything to talk to it (like Finder) - this causes the system to essentially hang. If you are lucky enough to have a Terminal window open (and in the foreground), you can reboot, or kill the Finder.

I would be greatly interested to know if running the above fixes anyone else's problem as well.

I have also tried rebuilding the services database and removing any unnecessary mdimporters from /Library/Spotlight. I am trying to track down if it is a specific corrupt file that is killing coreservicesd or something else. I keep running out of scrollback in my Terminal for my dtruss processes 🙂

Many thanks Jitterysquid. I think that is the best temporary "cure" so far. I had tried excluding various HD's in the Spotlight Privacy and whereas this improved things, I was still getting the infamous 10810 error from time to time. I assume to reverse the Spotlight, when Apple sort the issue with 10.6.3 (cough, cough) I enter "sudo mdutil -i on -a" in Terminal.

Wilson

Yes, "sudo mdutil -i on -a" will re-enable spotlight indexing and immediately fire off an index run. My coreservicesd will crash within 5 minutes of the indexer starting.

I'm guessing this was triggered the first time mds tried to do a full rebuild of the index after my 10.6.2 upgrade. It took a while for the problem to show up - I upgraded to 10.6.2 within 3 days of release and I just encountered the problem 01/30/2010.

But that turned on indexing for my yime machine backups! How do I turn it off there? System preferences fails to add this.
jarmac:~ jar$ sudo mdutil -i off -a
Password:
/Volumes/MacHD4:
Indexing and searching disabled.
/:
Indexing disabled.
/private/tmp/523/C:
Indexing disabled.
/Volumes/jarfx_c:
Indexing disabled.
/Volumes/Mac HD3:
Indexing and searching disabled.
/Volumes/Mac HD3/Backups.backupdb:
Indexing enabled.
/Volumes/tc:
Indexing disabled.
/Volumes/MacHD2:
Indexing and searching disabled.
jarmac:~ jar$

jrome - I would try telling mdutil to just look at /Volumes/Mac HD3/Backups.backupdb and see what it thinks it is set to right now:

sudo mdutil -s "/Volumes/Mac HD3/Backups.backupdb"

Then try:

sudo mdutil -i off "/Volumes/Mac HD3/Backups.backupdb"

and see if it gives a specific error.

I'm not sure why it chose to do the opposite of what you told it to do. I also find it interesting that the Backups.backupdb TM folder is mounted separately. Someone who actually uses TM might need to weigh in here.

jarmac:~ jar$ sudo mdutil -s "/Volumes/Mac HD3/Backups.backupdb"
Password:
/Volumes/Mac HD3/Backups.backupdb:
Indexing enabled.
jarmac:~ jar$ sudo mdutil -i off "/Volumes/Mac HD3/Backups.backupdb"
/Volumes/Mac HD3/Backups.backupdb:
Indexing enabled.
jarmac:~ jar$

Alfred Abraham wrote:
what was particularly helpful was the comments by wraggi :

http://reviews.cnet.com/8618-13727_7-10365239.html?communityId=2123&targetCommun ityId=2123&blogId=263&messageId=8461367&tag=mncol;tback

+where he wrote :+

The Fix - In many cases one of the following:

go to into your user library and delete:

~/Library/Preferences/com.apple.LaunchServices.plist
~/Library/Preferences/com.apple.LaunchServices.QuarantineEvents

Then delete these files from the root level of your boot drive ...

/Library/Caches/com.apple.LaunchServices* (the * means anything)

Then reboot.

I have not tested this long enough to comment, hopefully this will be of some help to someone

Alf

I agree with Alfred Abraham. The issue occurs on (some?) external volumes/drives (I have some USB with Fat32, and some with Mac OS X Extended (Journaled) and a FireWire drive. But this happens for example with an encrypted .dmg container that I put in the iDisc, too.

When this happens to me, I go to Library/Caches in my user directory (home) and delete "com.apple.finder" and the LaunchServices.plist if it is there. Then restart.
I think it is save to delete something in "Caches", as the name implies. However

You may have to use the Terminal and type
cd ~/Library/Caches
rm -rf com.apple.finder
rm om.apple.LaunchServices.plist

I am not sure which file/folder exactly is the problem. However this is no solution but just a temporary fix. Apple, please do something !

Message was edited by: SamuelJohn

And in case this problem happens to anyone, (It just happens to me), what is a kind of a work-around to get the Finder starting again, is to delete

~/Library/Caches/com.apple.finder
and/or perhaps the
~/Library/Caches/ LaunchService
files. (I am not sure with the latter but basically it's save to delete everything under Caches.)
Perhaps someone can figure out which file/folder is exactly causing the problem.

Then restart.
But this does not prevent the problem to reoccur at some (random) point in the future.