El Capitan 10.11.1 Install Problems

Nice detective work! Any idea what these extensions do or are for?

For what it is worth. Updated my iMac late 2011 last night. Installation hung fairly soon in the update procedure. First a lot of hard disk activity, then a grey screen and nothing more. Rang Apple Germany and got (free) and good support. Two telephone calls and a test upgrade on my MBP later (this last went without a hitch), I was told to delete all 3 cache folders in the various libraries on the iMac, which I did, and after a reboot the installation finished normally. A few hours lost due to a routine update, but at least everything works again.

Have been dealing with this same problem ever since the update came out. I managed to get my MacMini operational . but was advised to not turn it off until an Apple fix was available. My 2012 MBP is bricked solid and nothing I have tried has worked.

Am interested in knowing where the three cache folders were located (i can only locate two only machine) and whether you lost any data or application access by removing thrash folders? Was there any negative impact to your machine in doing this?

Thanks

Old Marine

I can only remember the location of two caches (the Apple guy talked me through it), one in the user library and the other in the general library, the third, I think, was in the/a system folder somewhere.

No, I lost nothing, at least so far I have not noticed anything.

My iMac was totally stuck too, restarts were useless and even recovery mode did not help.

I found all three caches:

1. user library > caches

2. Macintosh HD > library > caches

3. Macintosh HD > system > library > caches

I finally tried 10.11.1 as the new functions are something I'd like.

As with many here, I got to the install stage and it just stalled.

Haven't tried the fix suggested as, with more reading of the good folk here, there seems to be a 50/50 chance of succeeding;

and those odds just aren't good enough.

I had to reinstall my backup, and it's all okay for now.

It is so obvious that the company has decided to rush through some exciting changes with a lack of deference to the very loyal owner/operators of

their products. They don't have absolute power but the corruption is there in a healthy dose with this product.

Will I have to wait until 10.12 is available? Even then I will be very very cautious.

Brand new iMac 27 Retina -out of the box. Pre-installed with 10.11

used time machine to migrate a 10.6.8 user to the new iMac. No user password.

Restart. Everything ok. Migrated data 100% functioning

Did NOT sign into iCloud. Skipped it.

App Store Software update Notification: "There are updates for your mac" (10.11.1, etc) Like a lemming I say yes and proceed with install.

Mac restarts to BLACK Screen with cursor.

I cannot see the desktop - screen is BLACK-except for cursor) The mac is working. I can connect via another mac (original user had file sharing activated)

Internet sharing works (I set it up fo old old iMac because there is only one ethernet cable in the office)

Safe boot allows me to restart and see desktop. video severely impaired due to safe boot limiting video to bare bones video.

I am dismayed and really ******!

I went to recovery mode and reinstalled OS X (over existing install

Still no joy after the 1 hour+ ordeal of reinstalling!

On Monday I will use a USB installer and install 10.11 (not 10.11.1) over the existing 10.11.1 (if it lets me!)

I will assiduously check back with this post to see if any fixes are out there. From what I have experienced something (an extension) that worked in 10.11 has broken after the 10.11.1 update. What a nightmare!

There’s a lesson to be learned from all this. We all tend to be lemmings on occasion, especially when we have reason to trust popular opinion. And we have had good reason to trust Apple’s track record as far as Mac software, updates, and upgrades are concerned: things usually got better in some way, we have rarely been let down, and there have almost never been really serious problems. But s*** happens, and when it does, it will be unexpected. So: short of expecting it, prepare for it.

The lesson? BACKUP, BACKUP, BACKUP!!!

After losing all my data TWICE decades ago (actually, that had nothing to do with Apple, but my own carelessness, but I, too, have a tendency to be a lazy lemming), I began to take back-ups seriously. I discovered bootable clones (SuperDuper! is my choice), and have been making them regularly since (the price per megabyte of external ** drives has gone way down since I began, and now it’s downright cheap, and they're better). Time Machine and Time Capsule have been valuable additions (but not always 100% reliable), but I never stopped making clones. I used to do it daily, but weekly is now usually enough, EXCEPT I always make one right before any update/upgrade, or when I take my Mac on long trips. It’s like fire insurance, or those oxygen drop-downs in planes: you hope you never need it, but if you do, you REALLY do. To be sure, I’ve only rarely needed the clone, but when I have, it’s been a life-saver, and this 10.11.1 UpdateGate (I think it has legitimate claim on that name) has been a great example. I knew my Mac and all my data was safe, and except for the time I spent trying to get the d*** update to function (unsuccessfully), I was back at work thanks to my clone in half an hour. No stress, no sweat.

Meanwhile, as far as this update is concerned, I’ve decided I won’t even try to fix it. For me, at least, it’s not really necessary. There are too many elements in play, and regardless how good the fixes which have been proposed seem to be, I think the whole toxic thing has to be re-worked by Apple, and hopefully corrected with 10.11.2.

EXTRA! EXTRA! READ ALL ABOUT IT!

I know this sounds alarmist, but according to this post by slimchance, on Oct 31, 2015 6:13 AM, on another forum <Re: The update to 10.11.1 is hanging after about 3/4 of the installation - what can I do???>, who claims to have got this from Apple, we should do nothing (not removing .kexts, and all the rest) to try to fix our update problems, but wait until Apple corrects it.

Unfortunately the poster has (in spite of requests) failed to provide any supporting links, it is not possible to verify that Apple actually said that. So for now it's just another unsupported internet opinion.

Your advice to backup is the most sensible advice in the thread.

Hi all.

Yesterday I downloaded the El Capitan 10.11.1 update file in here Apple - Support - Downloads, execute the file and the update installed successfully.

Previously, my update via App Store failed.

Hope this helps.

Hi,

My macbook air updated to 10.11.1 without issue, but my iMac hung at about 60% through the process after the reboot. Disk check/recovery didn't help (no errors).

Re-installing OSX from the recovery utility had it boot and seemingly all data is available, though a painful and costly process.

First time for me that there's been an issue with an OSX update, which is exemplary of why I switched to Apple.

Don't drop the ball folks; MS update bollocks should be a huge warning about what not to do. Presumably these public errors are a one-off and will not turn in to a trend.

You are so right. The problem is widespread. Here in Cape Town, South Africa today I had exactly the same issue with the doomed OS X 10.11.1 on my 2010 iMac. Only fix or me was to take it in to my nearest Apple dealer and do a OS X restore (WITHOUT THE UPGRADE). Other Apple stores here are reporting similar issues.

I would therefore suggest that users of older units resist the temptation to upgrade although the basic EL Capitan seems to function fine. Fortunately, a return to the original OS X did not result in any loss of data.

AVOID OS X 10.11.1 until you (and the forums) suggest a further update works.

The quickest fix for any such problem is take it back to Apple and get them to restore the OS to an earlier version - or your best last OS that worked.

Thanks , This worked to me . thanks a lot . I really was tired

Follow up to my original posted comment:

I was gearing up to doing a combo update again and then a full blown complete reinstall. But first I tried deleting cache files as someone mentioned in this thread. No luck. after a restart a black screen. Booting in safe mode allowed me to see my screen, BTW
I tried some horizontal thinking:

I realized I had 'migrated' a user account without a password (I migrated from a 10.6.8 User without a password). I decided to to put in a password and deactivate Automatic login. Guess what: This worked for me, I was able to shutdown and restart to a visible sign-in screen instead of a cursor on a pitch black screen.