Installed Mavericks and shortly thereafter Finder crashed. Error message keeps appearing, click OK to send to Apple and message returns. Tried restart to no avail. Any suggestions?
iMac, OS X Mavericks (10.9)
No, you shouldn't lose anything, it will only replace system files. That said you should always have a backup, but you said you had Time Machine?
Unfortunately, I don't. Should I try to borrow an external hard drive and do a TM backup first?
Yes, or buy one so you always have it. If you run without a backup sooner or later you'll be sorry about that decision.
I think I'll wait a couple of days before I try anything too drastic in the hope Apple will correct this Finder mess, which is akin to it distributing a car without a steering wheel.
You can wait but since it's not an issue everyone is experiencing it may be a long wait.
I hope not. I plan to go into my local Apple Store tomorrow morning to see if technical staff are aware of the issue and if they have a heads up on at least a temporary solution.
Please, report back if solved.
For sure. Solved or not, I hope I can gain a better sense for the scope of the problem. Will certainly pass on what I learn.
How did you back up from Time Machine? I made a TM back-up just prior to running the Mavericks install. When I plugged it into to restore to Mountain Lion, Mavericks didn't recognize the TM.
I also ran 'carbon copy' cloner, just as a fail-safe, but feel that Apple should figure out a way to support its own integrated software. What's the point of using TimeMachine if the failed new OS doesn't recognize it?
Thanks...
I have the same issue, that Finder crashes repeatedly after I installed Mavericks.
Just started using my previously installed Path Finder which seems to function just fine under Mavericks; provides the Finder function showing all attached devices and more. Not the solution to the Finder issue, but does provide a temporary bridge.
Form my part, I believe I have resolved the freezing after installing issue for my MBP, mid-late 2007 model. After ensuring that the latest backup of the Mac was captured by TimeMachine, I booted from an external drive and erased the hard drive in the MBP. I then launced the App Store and obtained Mavericks. When presened with select disk, I selected the freshly erased MBP disk. The install took about 40 minutes and it has now booted nicely into Mavericks. Instead of going through the usual setup options I selected to restore from a TimeMachine backup. In doing so, I selected to copy everything over, Apps and documents, but not computer and network settings. The old OS/Finder must have had some sort of corruption that was not being detected by the various utilities I was running to resolve the issue previously. The data from the TM backup is now being transferred. I should kow if the issue is actually resolved once that is recovered and I have booted fully into Mavericks.
For the TM . command - R when you start or restart to access Mac osx utilities. that'll let you evert back with TM and not let Maverick interfere.
its also in the owners manual, all the steps.
instructions.
Just back from an Apple Store where I spoke to technical staff concerning Mavericks Finder crashes. Unfortunately, at this point the store staff are unaware of the issue. Recommendation was made to reinstall Mavericks. Other than doing the reinstall, it looks like the issue will have to perk a while tbefore the root cause(s) is identified.
This problem is causing data corruption. I have a second hdd in my 2011 17inch in place of the superdrive. While saving a large photoshop file, finder would stop responding and my second hdd just got unmounted without any reason.
Disk utility was unable to mount or repair the drive, I had to restart in repairmode, and repair the disk there so that OSX can mount it again. Of course the files I was saving when this happened were corrupted.
This happened twice already since I installed Mavericks yesterday.
I've reset the PRAM and give it another try. If this happens again, I'll revert back to MtLion until there's a fix.
finder crashes with maverick
