Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases OS X 10.11.1 El Capitan With New Emoji, Mail Improvements and Office 2016 Bug Fix
- Thread starter MacRumors
- Start date
- Sort by reaction score
I don't want to be the Apple guy with a reverse end, but when an update that affects millions of users is broken, the process is broken. Apple, have a three tier release process where the mindless user is in the third tier.
Just Rocketman
Apple drones, I know you are reading this. Forward it. It's a UI issue.
If you are going to be a late adopter of tech, let your users be a late adopter of updates. Please?
Just Rocketman
Apple drones, I know you are reading this. Forward it. It's a UI issue.
If you are going to be a late adopter of tech, let your users be a late adopter of updates. Please?
Last edited:
Anyone ever try Thunderbird? I switched from Apple Mail a LONG time ago when I realized that not upgrading my OS meant no upgrades to Mail (e.g. I skipped Yosemite). Mail has had problems since at least Mavericks, if not earlier (used to not check mail when you told it to and would often take a day or more to do it on its own unless you quit and restarted). Thunderbird by comparison has been rock solid for me and they update it long after support for a given OS version has been abandoned by Apple.
OTOH, Mail does work here and worked in 10.11.0 too. I just prefer Thunderbird.
Hmm.. they are general Intel & Nvidia drivers, so I don't know which GPUs will benefit. I have Iris Pro 5200 and 750M. Both got newer driver version. Also openCL was updated.
Found a nasty and frustrating (new!) bug in 10.11.1 which has borked Mission Control for me.
When using a non-fullscreen app and you use Cmd+Tab or the dock to click on another app (that is not on the same desktop), it does not switch straight away - it simply seems to pass window focus to the Dock and then if you then do the same action AGAIN with Cmd+Tab or clicking on the Dock, it then actually changes app focus to the other desktop.
When you Cmd+Tab already with a full-screen app focused, this behaves as expected and switches app focus straight away, even to something non-full screened. Anyone else got this one?
It's a actually a bad regression of a system I thought was working perfectly before.
When using a non-fullscreen app and you use Cmd+Tab or the dock to click on another app (that is not on the same desktop), it does not switch straight away - it simply seems to pass window focus to the Dock and then if you then do the same action AGAIN with Cmd+Tab or clicking on the Dock, it then actually changes app focus to the other desktop.
When you Cmd+Tab already with a full-screen app focused, this behaves as expected and switches app focus straight away, even to something non-full screened. Anyone else got this one?
It's a actually a bad regression of a system I thought was working perfectly before.
I wish Apple wold simply stop doing "major updates" to the OS and focus on bug repair and smaller incremental changes. Why do we need all new UI and codebase every single year? The answer is we don't. Apple marketing seems to think they do. Bring back classic for example and if that means a thunderbolt dongle to make it work, okay.
Serious bug in 10.11: cannot connect iTunes to Apple servers, reported in discussions.apple.com by a number of users: Get pop-up windows with errors of form "iTunes cannot verify the identity of the server...", where that server is any of a long list, e.g., itunes.apple.com, search.itunes.apple.com, init.itunes.apple.com, play.itunes.apple.com.
I'm suffering from this too.
I'm suffering from this too.
This isn't a "major" update and the UI is almost the same as Yosemite. I simply wish the performance without a Metal supported GPU was better, more akin to Mountain Lion and older hard drives didn't run slower for that matter (I went from 240-270MB/sec in Mavericks and Mountain Lion to 140-180MB/sec in El Capitan with the same RAID 0 setup). My GPU for my Mac Mini is supported so it's super smooth on that Mac, but I'm afraid it won't do as well on my 2008 MBP (probably try it anyway just to see, though, but the XBench results for the UI using the old calls is pretty slow in testing. I don't have a newer test for such things if XBench is the problem). Each OS release since Snow Leopard (save possibly Lion to Mountain Lion; I didn't use Lion but I've read it was horrible which is why I didn't switch) has given steadily slower results for Quartz, Hard Drives and User Interface test (most everything else has been about the same). "Metal" is a bit of a nice "cheat" to make things smoother on supported GPUs, but it's no excuse to get lazy elsewhere and it would have been nice if they had finished updating OpenGL to its final pre-Vulkan version first.
I have this with App Store.
Not sure if it's the same error or not, but it definitely wasn't around before 10.11.1. (As evidenced by the fact I managed to update to 10.11.1.)
SIP is even worse than I ever imagined. All I want to do is disable it. I can't. Period. The problem is that I already have RAID drives in use on my Mac Mini server and you NEED a recovery partition in order to disable SIP with "csrutil". You cannot have a recovery partition on a RAID drive. Someone told me just get a USB stick and create a recovery partition on it and use it as the recovery drive and all will be good. There's a MAJOR PROBLEM with that suggestion. There is NO WAY TO CREATE A RECOVERY PARTITION without already having a recovery partition! (Makes logical sense, right?)
Recovery Disk Assistant REQUIRES you ALREADY HAVE a recovery partition on the drive you booted from! It won't magically create one from scratch (same is true of Carbon Copy Cloner). Recovery Partition Creator (V3.8) can supposedly create one from the installation file (6+ GB), but when you try to run it under 10.11.1 it craps out and says it's not supported in this version of OS X. So I tried creating a recovery partition from my Macbook Pro running Mavericks using Recovery Disk Assistant. It's annoying because you have to partition it yourself ahead of time or it will use your entire USB stick for a tiny (760MB) recovery partition. This will might come back later to haunt you again. So I created a 3 Partition setup on a 16GB drive thinking I will create a USB stick that has Boot Installers for Mavericks and El Capitan plus a Recovery Partition. OK, I use Recovery Disk Assistant and it puts a recovery partition on the 1GB partition and that partition disappears. I then booted into my backup drive that still has Mavericks on it for my Mac Mini and downloaded the Mavericks install files (despite a 30Mbps connection, it took almost 3 hours due to slow Apple servers). I then used Diskmaker 5 to create a bootable install partition on one of the two remaining partitions on the USB stick and once I download El Capitan I would do the same for the other partition. Here comes the next problem.
I reboot into the Recovery Partition I created earlier. Can you guess why it isn't helpful? If you guessed that a Mavericks Recovery Partition CANNOT run CSRUTIL you win a prize! I can easily get to the Csrutil file on my El Capitan drive from the recovery shell, but it says "Operation not supported" when I try to run it. Apparently, you have to be running an El Capitan Recovery drive in order to run that file. Well, I don't have an El Capitan recovery drive ANYWHERE because I upgraded from Mavericks to El Capitan on a system using RAID 0. This never used to be an issue because you don't NEED a "Recovery Drive" in years past as long as you have a bootable backup! (I can also restore off the Internet if I really got in a mess). But along comes El CRAPitan and creates a need for a recovery drive OTHER than actually recovering something! They could have just had a reboot switch with a separate password or something to do it automatically with a recovery partition intervention, but no no no. Apple has to make life fracking miserable. They could have made Recovery Disk Assistant create a recovery drive from scratch for you. No no no. They want you to already have a recovery partiition in order to create a new one! Well, if I ALREADY HAD one, I wouldn't need to create one!!!!!!!!@@$@#@@$!!!!
So this leaves me with a couple of lousy options. One is wait for Recovery Partition Creator to update (if it updates) to handle El Capitan 10.11.1 and try to create a recovery partition from the install files. Two, ONLY BECAUSE I also own a Macbook Pro that can be updated to El Capitan, I can go ahead and update it (even if I don't want it) and since it DOES have a recovery partition, that partition will get updated to an El Capitan version and then I can use Recovery Disk Assistant all over again on that USB stick to create an El Capitan recovery partition that I can then take over to use with my Mac Mini! I will have to wipe the USB stick and make the Mavericks boot partition all over again because that's the only way that program works (i.e. once it disappears, it doesn't come back to update). Then, if I want Mavericks back on the Macbook Pro, I then have to restore from its backup drive using Carbon Copy Cloner. WOW! That's a LOT of work to create a stinking recovery partition on a freaking USB stick so I can turn off SIP and use my software that El Capitan disabled that needed it (e.g. XtraFinder and NFS with the -N option).
It's utterly ridiculous is what it is. They should have given you the option of disabling SIP during the update install at the very least or better yet put the damn switch to disable it somewhere that doesn't require a damn recovery partition to run it, knowing full well that RAID users will be screwed by it!
Just try again. My Mavericks Macbook Pro gave the same error. It means too damn many people are trying to access the App Store at once. I clicked on it again and it came up fine.
Recovery Disk Assistant REQUIRES you ALREADY HAVE a recovery partition on the drive you booted from! It won't magically create one from scratch (same is true of Carbon Copy Cloner). Recovery Partition Creator (V3.8) can supposedly create one from the installation file (6+ GB), but when you try to run it under 10.11.1 it craps out and says it's not supported in this version of OS X. So I tried creating a recovery partition from my Macbook Pro running Mavericks using Recovery Disk Assistant. It's annoying because you have to partition it yourself ahead of time or it will use your entire USB stick for a tiny (760MB) recovery partition. This will might come back later to haunt you again. So I created a 3 Partition setup on a 16GB drive thinking I will create a USB stick that has Boot Installers for Mavericks and El Capitan plus a Recovery Partition. OK, I use Recovery Disk Assistant and it puts a recovery partition on the 1GB partition and that partition disappears. I then booted into my backup drive that still has Mavericks on it for my Mac Mini and downloaded the Mavericks install files (despite a 30Mbps connection, it took almost 3 hours due to slow Apple servers). I then used Diskmaker 5 to create a bootable install partition on one of the two remaining partitions on the USB stick and once I download El Capitan I would do the same for the other partition. Here comes the next problem.
I reboot into the Recovery Partition I created earlier. Can you guess why it isn't helpful? If you guessed that a Mavericks Recovery Partition CANNOT run CSRUTIL you win a prize! I can easily get to the Csrutil file on my El Capitan drive from the recovery shell, but it says "Operation not supported" when I try to run it. Apparently, you have to be running an El Capitan Recovery drive in order to run that file. Well, I don't have an El Capitan recovery drive ANYWHERE because I upgraded from Mavericks to El Capitan on a system using RAID 0. This never used to be an issue because you don't NEED a "Recovery Drive" in years past as long as you have a bootable backup! (I can also restore off the Internet if I really got in a mess). But along comes El CRAPitan and creates a need for a recovery drive OTHER than actually recovering something! They could have just had a reboot switch with a separate password or something to do it automatically with a recovery partition intervention, but no no no. Apple has to make life fracking miserable. They could have made Recovery Disk Assistant create a recovery drive from scratch for you. No no no. They want you to already have a recovery partiition in order to create a new one! Well, if I ALREADY HAD one, I wouldn't need to create one!!!!!!!!@@$@#@@$!!!!
So this leaves me with a couple of lousy options. One is wait for Recovery Partition Creator to update (if it updates) to handle El Capitan 10.11.1 and try to create a recovery partition from the install files. Two, ONLY BECAUSE I also own a Macbook Pro that can be updated to El Capitan, I can go ahead and update it (even if I don't want it) and since it DOES have a recovery partition, that partition will get updated to an El Capitan version and then I can use Recovery Disk Assistant all over again on that USB stick to create an El Capitan recovery partition that I can then take over to use with my Mac Mini! I will have to wipe the USB stick and make the Mavericks boot partition all over again because that's the only way that program works (i.e. once it disappears, it doesn't come back to update). Then, if I want Mavericks back on the Macbook Pro, I then have to restore from its backup drive using Carbon Copy Cloner. WOW! That's a LOT of work to create a stinking recovery partition on a freaking USB stick so I can turn off SIP and use my software that El Capitan disabled that needed it (e.g. XtraFinder and NFS with the -N option).
It's utterly ridiculous is what it is. They should have given you the option of disabling SIP during the update install at the very least or better yet put the damn switch to disable it somewhere that doesn't require a damn recovery partition to run it, knowing full well that RAID users will be screwed by it!
Just try again. My Mavericks Macbook Pro gave the same error. It means too damn many people are trying to access the App Store at once. I clicked on it again and it came up fine.
It's not a bug with OS X; Apple has been having software update accessibility issues for more than a day now, affecting all versions of OS X.
Just for the heck of it, I tried copying over the Mavericks version of Disk Utility (renamed it) and tried to run it. It started to run just fine in the background, but then a pop-up came up that said I was not ALLOWED to run the old awesome version of Disk Utility in El Capitan that I MUST exit and run the crap version. It seems to me this is just a stupid version check somewhere that if one could find a way to defeat, you could have the old version of Disk Utility back. It appears they went to great lengths to make sure you CANNOT use it, though. You have to figure the old version probably wouldn't have had a check in mind for such a thing because it didn't really change over multiple OS versions since like Jaguar or whenever. They must have something in OS X itself looking for old versions when run and then intercepting them (would explain why it was working in the background until the pop-up appeared scolding me for trying to use a better version of Disk Utility). Someone needs to find this check in the OS and find a way to terminate it with extreme prejudice (as in the new Disk Utility sucks).
Edit: Made some progress; force quitting "software updated" process while the warning window is up got it to "gathering disk information" in the background on the old Disk Utility but the "close" pop-up window is still there. I think it's just a matter of closing the right process to get it to work.
Edit: Made some progress; force quitting "software updated" process while the warning window is up got it to "gathering disk information" in the background on the old Disk Utility but the "close" pop-up window is still there. I think it's just a matter of closing the right process to get it to work.
Last edited:
I saw the exact same error today while running Yosemite 10.10.5 when I used App Store to check for updates for Yosemite. I quit the App Store. Waited about 30 minutes and tried the App Store again with no error. The problem does not seem to be tied to 10.11, but instead Apple servers.
Last edited:
I'm really tired of Apple releasing a new OS every year. It's just ridiculous. It's too fast and it almost always takes a good 6-9 months just to iron out the new bugs. I wish they would at least move to a 2-year cycle so we could quit chasing down all of these problems for awhile.
Yeah, I mentioned that program already above. It's the only version there is.
I did not. I've been downloading it for hours (i.e. installer automatically is deleted normally after an install). I'm making a copy of this one so I can make an install thumb drive when all this is done that will have an El Capitan Recovery partition plus El Capitan Install partition and Mavericks Install partition.
What's that supposed to do? I have RAID here. AFAIK you can't install a recovery partition on RAID and I don't see any commands to indicate I can specify what partition. I'm installing El Capitan on my Macbook Pro next (wanted to see how a 2008 MBP performs with it anyway since I just backed it all up two days ago) and from there I can just run that Recovery Disk Assistant (what you call Lion Recovery Update) from it and put it directly on the USB stick (followed by the boot installers from my Mini using Disk Maker X 5.
Recovery Disk Assistant is not the same as Lion Recovery Update. They do 2 different things.
Recovery Disk Assistant just copies an existing recovery partition to an external drive.
Lion Recovery Update on the other hand updates the Lion recovery partition from version 10.7 or 10.7.1 to a 10.7.2 version. However it was soon discovered that together with my instructions it can CONTINUE to update it to 10.7.3, all the way up to 10.11.1 (and counting). Furthermore it can even create a new recovery partition where one doesn't previously exist. Given that delta and combo updates don't update the recovery partitions, it has proven to be a very useful little remnant from Lion days. I keep it permanently in my Downloads folder together with the script file ready for the next update.
If you use my method, you have to download Lion Recovery Update which is 431.91MB. But to be honest about it, there is really only a tiny little part of it that my script uses called dmtest. This is proprietary software owned by apple and it would be illegal to extract it from Lion Recovery Update and insert it into a much smaller app however more convenient that may be.
So the only legal way to access dmtest is through Lion Recovery Update. That's why we still have to download that to get my method to work ( - and keep it all legal).
If this stuff is giving you so much trouble, why don't you just make a bootable usb instead using these instructions from apple: https://support.apple.com/en-au/HT201372
That's actually better than a recovery partition because it contains the full installer (which a recovery partition doesn't).
Last edited: