CNET también está disponible en español.

Ir a español

Don't show this again

Computers

Ongoing Snow Leopard issue: Finder Application cannot be opened (-10810)

As reported on MacFixIt over a month ago, a growing number of users are still experiencing an issue with Finder freezing when attempting to connect to shared volumes or external hard drives and work with files from those drives.

As reported over a month ago here on MacFixIt, a growing number of users are still experiencing an issue with Finder freezing when attempting to connect to shared volumes or external hard drives and work with files from those drives. Users report the issue happening with SMB Shares, connecting to servers via Finder's "Connect to Server" function, and external storage devices such as Drobo drives.

Users experience a freeze in Finder when attempting to search or work with files on their shared drives. When they Force Quit (relaunch) Finder, they receive the (-10810) error with the message that the Finder application cannot be opened. Users are forced to then reboot their machines to continue use. Apple Support Discussions forum user "fitzyjoe" reports:

I'm having the same problem - When I try to "Connect to Server" from the Finder. I select afp:///. Then, I'm prompted to authenticate. Authentication seems to complete successfully and an entry is created in /Volumes. If I try to expand the volume or do an "ls -al" in Terminal, the Finder freezes. I right-click on Finder and choose to restart it. Then, I'm hosed... Can't start a new Finder with "The Application Finder can't be opened -10810" message. If I wait long enough, the Finder restarts. The shared drive on my server is a Drobo.

Solutions?
At this point, it still looks like people are having this issue and no official fix has been released from Apple. That being said, Mac OS X 10.6.2 has seen several beta releases to developers and should be available for download soon. To further the hopes of users that have been faced with this issue, ASD user "alleksu" posted this response from Apple about a filed bug for this problem:

"This is a follow up to Bug ID# 7256664. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 7152276. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#."


Be sure to check us out on Twitter and the CNET Mac forums.
Do you have questions, issues, or stories you would like to see on MacFixIt? Email Us.