The application Finder.app can't be opened.

10.6.2 due out any day soon. The level 2 techie I spoke to claimed that this would solve this problem, make my hair grow back again and provide free beer.

Wilson

You have spoken to a level 2...impressed, like the free beer..how does it get poured from the machine? a USB plug in extension to put the glass under?

Oh really? What so dpeial about level 2 technie? He graruntee 10.6.2 can solve this problem or just entertain you ?

I think you can probably gauge my confidence in the techie's assurances that 10.6.2 would solve the problem from the "free beer" comment. Just think how long it has taken Apple to half solve the wireless network time out issue (2+ years and yawn - counting).

Wilson

Hey! I solved the problem for my Finder - 10810 problem!
Yesterday I tried whole full day to figure out what causing the Finder to crash. Finally I found out it's the Time Machine, when TM start to backing up, it will crash, and I look into my Console, it's listed "coreservicesd_date-time-localhost.crash", I thought it's something related to coreserivices but I was wrong, it's the TM.
So I just do as other website suggested, EXCLUDE the TM being index/search by Spotlight.
Just add TM drive into the EXCLUDE list of Spotlight, wolah! Work like a charm and no more crash!

For anyone who having the same problem with TM caused the Finder/Dock crash and can't operate the OSX need to make a hard reset, my solutions 100% work to you! If you don't have Time Machine running, just make sure Spotlight EXCLUDE all your external drive index/search.

My setup is WD My Passport Studio as my Primary boot disk via Firewire 800.
My iMac internal HDD as Time Machine.
It's because my iMac's internal HDD having lag problem stated as this website: http://www.mac-forums.com/forums/os-x-operating-system/106153-leopard-lag-imac-h ow-do-i-troubleshoot.html since Leopard, tried Snow Leopard and any solution still no luck.. 😟

This problem happened strangely after I tried out VMWare Fusion 3 BETA 2... after the installation, I got Little Snitch installed, it will ask to allow the Internet Connection for VMware, after I allow it, the system start crashing. I think it may related something about VMware & Snow Leopard itself, maybe it's still in Beta though.. Anyway, now my Snow Leopard no more crash, wish help anybody who having same issue with Time Machine & Snow Leopard.

Cheers,
Chris from Hong Kong

Message was edited by: chrischua

Chris,

It may be Time-Machine for you but i suspect it is more to do with the attached external drive. I have not used Time Machine since I got a corrupt sparse image last year and lost my whole back up. I use Chronosync. Like many others, almost from day one of SL, I have excluded the external drives from Spotlight but I still get 10810 and other finder lock ups, if I leave any FW external HD attached when my iMac goes to sleep. My MBP with an apparently identical set up and software suite works much better with only rare 10810's on the little Iomega eGo FW800 external drive and on the big FW400/800 2TB Datatank that normally sits on my iMac. I tried using the Datatank with USB2on the iMac instead of FW but no joy.

Wilson

Just got the same error - was copying files from a CD-R that i had burned on another machine to my Macbook - lagged for over 10 minutes - Force Quit the Finder to stop it from trying to copy ( from a bad cd i'm guessing ) - cannot get Finder to come back without restarting ( which if I am uploading files thru Dreamweaver, or another ftp app, or downloading/streaming anything, etc - I have to start over on any work I'm doing because of a faulty Finder. Maybe time to rename the Finder to Loser 😟 )

Also - it affects other apps as well - can't open Adobe Bridge for example - since it needs to communicate with the Finder - also if I try to Apple-O a file from within Photoshop it also will crash/lag PS.

Another note - also the menubar seems to be bugged when this error happens - just tired to go to "About this Mac" and nothing happened.

Waiting for my free beer and 10.6.2 i suppose...

I got tired of waiting for a fix and did a clean erase and install. I reinstalled all my ilife apps from the dvd that came with my ibook and copied only my apps and docs from a TM back up I did. Then I downloaded all the upgrades. I've set up my accounts from scratch as well and reinstalled a couple of plug ins I had. I've had some cs3 problems, but finder seems to be fixed and working.. so far!

I just did a software update and restarted my computer to get the Finder.app can't be opened. I have no idea what to do and I'm not a techie so any help would be appreciated. I've had Snow Leopard since it's release.

For a start, insert your Snow Leopard disc, restart holding the C key down and when you reach the install page go to the utilities menu on the top bar. Click on "Disk Utility" and once this opens, click on repair hard disc. After that has finished, click on repair file permissions (both these will take some time to run). This is First Aid cure #1 for all OSX macs. Then exit from installer via select start up disc and choose your hard disc. I hope this will at least recover finder for you. If you are a Mac newbie, this is as far as I would go yourself without finder and if it does not work, I am afraid it is a trip to the genius bar at your nearest mac store. I would not suggest that you delve into Terminal and Console commands as you may do more harm than good. If you have a copy of techtools or can download it on another machine, you could run that to make sure there is not a hardware fault.

Wilson

Having the same Problem with SMB-Shares here. Since Yestereday, the Finder crashes or I get a kernel panic when working with SMB-Shares. Very frustrating, to say the least.

Of course I have gone through every recipe that is mentioned in this thread for stailizing my system.

Has anyone had luck with this problem? The problem occurs when Time Machine begins to back up to my WD My Book Studio. The Terminal line works, but only if I keep Terminal running, which I'd rather not do as it takes up space in my Dock. Does anyone know if 10.6.2 will actually do anything to alleviate this?

Some folks have had luck with a clean install but this is a bit sledgehammer/nut-ish. I have been following the progress of 10.6.2 and what it is stated it contains plus bugs on beta releases. I am very much afraid to say I don't see much evidence of a serious effort by Apple to tackle this issue in this update. I have a feeling they may be in denial over it just like the "Connection Timeout" issue, dating from the release of Leopard, which they still have barely acknowledged. I am not optimistic. The liaison between Apple and the various software/hardware providers seems much poorer that we have been used to on previous OS updates. I was speaking to Epson yesterday to check which film scanners had Snow Leopard drivers and which Epson scanner software worked either in 32 or 64 bit. Confusion reigned.

Wilson

I'm experiencing this issue as well. C'mon Apple, this is fairly serious!

This problem happened again today. It was triggered by a USB flash drive - same as last time. Here's a timeline of what happened:

I plugged in a standard USB flash drive. I copied a couple of files across to it, but the copying stalled. I tried to stop the copying, which didn't work. I then tried to eject the USB drive, which also didn't work. By this time, Finder was beachballing and unresponsive. I right-clicked on the Finder dock icon and re-launched it. This is when the "The application Finder.app can't be opened" error message appeared. I then tried to shut down the computer, which also stalled. I had to hold the power button to turn it off.

This Console log roughly correlates to the time when Finder started acting up:
http://img88.imageshack.us/img88/1218/screenshot20091027at938.png

I can't remember the timing exactly though. That console entry may have appeared after I forcibly rebooted the computer, I really can't remember. But the interesting thing is this: the file referenced in that log (/Volumes/SOPHIE1/Design/5 Print - Milk.psd) is one of the files that failed to copy to the USB flash drive.

A hint at solving the problem, perhaps?

Message was edited by: Fizwidget