My body is preparing for OS X 10.12 betas.
Your body can wait 6 months.
My body is preparing for OS X 10.12 betas.
er, you might want to try to find out what keeps doing that, because OSX won't be; and if you don't know what it is, is may be something that shouldn't be there.
[doublepost=1453228106][/doublepost]
without Flash, browsing is a lot faster, yes, and safer, and gives longer battery life. I've not had it installed on a Mac now for over a year.
I have a JDK installed because it's my job *and* my hobby, but even I don't have it enabled in the *browser*. As long as you ensure that too then it too won't be slowing down your browsing. (You can enable or disable java in the browser in the java control panel, in the security tab.)
Safari and iTunes can no longer be opened as they are corrupted everything is running at a snails pace. Reinstalling El Capitan now and not going past 10.11.2 it's s disgrace..
I clocked Safari before and after the update. About 30% faster now.Its out, less than a minute to finish the download. Hopefully the performance of my 5k iMac improves. The sleep function has been broken since the last update.
Am I the only one who CAN'T get the external displays to work with this 10.11.3 update? It was working fine before installing it, and after it no matter what I do the computer does not see the displays. I have rebooted, cold booted, and connected/disconnected everything but nothing.
I'm on a MBPr late 2013, with 2 Dell U2410 connected via DisplayPort (each on separate ports, no chaining).
I've seen a few posts complaining about this issue. I definitely plan to wait before updating.
Go to About This Mac and see if it lost your serial number. If it doesn't know your serial number, you will not be able to log into the App Store or iCloud, or iTunes.
Certainly seems that way. Restarting my Late 2013 15" rMBP takes significantly longer on 10.11.3 than it did on 10.11.2."Apple Releases OS X 10.11.3 El Capitan With Multiple Bugs"
Precisely why I have held off from installing the 10.11.4 beta till now.
The last 10.11.3 beta was build 15D13b. And the 10.11.4 beta was 15E27e. So despite apple being early with releasing the 10.11.4 beta I haven't installed it because then I couldn't test the new build 15D21, which although historically newer than build 15E27e, going by build numbers is between the 2 betas.
So I'll install this 15D21 build over 15D13b, AND THEN (maybe a few days later) install build 15E27e.
That makes more sense to me. (And perhaps more importantly, I'll have time machine backups of all 3 builds).
Thanks tywebb13, appreciate your timely posts.Don't forget to update your recovery partition. Updating through the mac app store or with the delta or combo update will NOT update the recovery parttion.
To make the 10.11.3 recovery partition:
1. Download the Lion Recovery Update from https://support.apple.com/kb/dl1464?locale=en_US . Make sure it is in your downloads folder. Download the full installer for el capitan 10.11.3 from the mac app store, right click on it and click Show Package Contents. Go to Contents/SharedSupport/. Copy the InstallESD.dmg file into your Downloads folder.
2. Download and decompress the file recovery.sh.zip from http://4unitmaths.com/recovery.sh.zip and move recovery.sh into your Downloads folder if it's not there already.
3. Open Terminal and type the following commands:
chmod +x ~/Downloads/recovery.sh
sudo ~/Downloads/recovery.sh
4. Wait a few minutes for it to finish and return back to a prompt. Reboot with holding down the option key to test your 10.11.3 recovery partition.
To add to what @dogslobber mentioned, the build numbers across versions don't inherently indicate the age of a given build and are not directly comparable.Precisely why I have held off from installing the 10.11.4 beta till now.
The last 10.11.3 beta was build 15D13b. And the 10.11.4 beta was 15E27e. So despite apple being early with releasing the 10.11.4 beta I haven't installed it because then I couldn't test the new build 15D21, which although historically newer than build 15E27e, going by build numbers is between the 2 betas.
So I'll install this 15D21 build over 15D13b, AND THEN (maybe a few days later) install build 15E27e.
That makes more sense to me. (And perhaps more importantly, I'll have time machine backups of all 3 builds).
I haven't used flash in two years and everything has seemed fine or the same. For a few months some web pages wouldn't run, but everyone seems to have clued in now and i haven't seen anything that required it in over a year.I agree completely with you! I do not have Java or Flash installed on my MacBook Air and it is A LOT faster and obviously more secure. Sure, do some websites look weird because of having no Flash? Obviously yes. However, webpages load A LOT faster! Also, as you said you gain battery life. More and more websites are going to H.264/5 so soon most people won't even need Flash for the most part.
![]()
To add to what @dogslobber mentioned, the build numbers across versions don't inherently indicate the age of a given build and are not directly comparable.
For instance, the first publicly available beta of 10.11.3 was 15D9c. We can't assume that's older than build 15C50 of 10.11.2.
Thanks tywebb13, appreciate your timely posts.
I have an older MBP, 2011 15" with a Plextor SSD installed, and on that machine, updated with the combo updater, the Recovery procedure you posted resulted in a recovery partition named "EFI boot", which seemed a little strange! I connected a Firewire disk (Intel SSD 335) and rebooted to that external disk. Ran the procedure again, and it worked correctly resulting in a recovery partition named "10.11.3". So I ran CCC and used its recovery partition cloning function on the MBP internal SSD, which correctly cloned the 10.11.3 partition to the internal SSD in the MBP.
In addition to that little "glitch," I have noticed some strange errors when trying to delete files, with a "can't delete these items because they can't be found" error, which will sometimes be resolved by quitting other running apps, sometimes not until a restart. I can always delete the target files after a restart.
This may be spotlight related, so I will do a reindex via Onyx and see what happens.
I have also encountered this finder "bug" on my older Mac Pro '2009' .
Any iseas as to the cause of this?
This "fix" was part of 10.11.1. Apple hasn't changed it in 10.11.3, and it's still broken. Now that it's fully public, maybe we'll see a fix in 10.11.4.The OSX10.11.3 update seems to include a slapdash, incomplete attempt at putting a finger in CVE-2015-7024. Patrick Girdle confidentially revealed his discovery of the hole in Gatekeeper to Apple and he took less than 5 minutes to break through the "fix." Same problem, unauthorized applications can be installed through the hole. see Kaspersky's threat post.
OBTW 9.2.1 OK
Hope they add Night Shift to the Mac in the next betas of 10.11.4![]()