Back to Apple Security Update page
Apple Security Update free download for Mac

Apple Security Update Reviews

2020-002
26 March 2020

For macOS High Sierra.

PLAYER_ONE
12 September 2019

Most helpful

I've got serious problem with latest security update on my 13' MacBook Pro Retina (Early 2015). After update my Mac heats up and throttle as hell. I reinstalled Mac OS Sierra from scratch, changed thermal paste on CPU twice, nothing helped. I can have ~80 celsius on my CPU, when I'm only browsing the net on Safari. It's hard to use any powerful applications, because it can heat up to even ~100 celsius and above. Please help, what can I do? Did anyone had the same problem? Thank you in advance P.S. I can't upgrade my OS to newest version due to my health problems. So I have to stay with Mac OS Sierra.
Like (2)
Version 2019-004

Read 59 Apple Security Update User Reviews

Rate this app:

Ward
05 February 2020
Security Update 2020-001 was released on 28 Jan 20. More info: https://support.apple.com/en-us/HT210919
Like
Version 2019-004
PLAYER_ONE
12 September 2019
I've got serious problem with latest security update on my 13' MacBook Pro Retina (Early 2015). After update my Mac heats up and throttle as hell. I reinstalled Mac OS Sierra from scratch, changed thermal paste on CPU twice, nothing helped. I can have ~80 celsius on my CPU, when I'm only browsing the net on Safari. It's hard to use any powerful applications, because it can heat up to even ~100 celsius and above. Please help, what can I do? Did anyone had the same problem? Thank you in advance P.S. I can't upgrade my OS to newest version due to my health problems. So I have to stay with Mac OS Sierra.
Like (2)
Version 2019-004
Derekcurrie
01 August 2019
Untangling Confusion:

The original "Security Update 2019-004 (High Sierra & Sierra)" contained a bug that affected Sleep mode on a few recent Mac models. Without explanation, Apple pulled the update for several days. Then, without explanation, Apple made the update available again with modifications that removed the Sleep bug.

If you have questions about whether you have the correct version installed, simply download and install this latest version. For details, please read:
"Apple has released High Sierra and Sierra Security Updates 2019-004 again"
https://eclecticlight.co/2019/07/29/apple-has-released-high-sierra-and-sierra-security-updates-2019-004-again/
Like (1)
Version 2019-004
mason746
04 June 2019
If you have an older Mac, you are stuck on macOS 10.13.6. A number of people have had problems installing Security Update 2019-003 10.13.6, where on shutdown the Mac hangs at a black screen with just the cursor visible, requiring a hard reset that doesn't complete the installation. Rinse and repeat, but no success.

Quick solution to enable successful shutdown, but does not install the Update:
Delete the files that trigger the patch installation on shutdown
https://apple.stackexchange.com/questions/188842/black-screen-with-cursor-on-logout-in-yosemite

Solution to clear and reset a whole load of "stuff", and get the update installed:
https://davidsimpson.me/2018/11/14/fixing-failed-macox-10.13.6-security-update-2018-002/
The above works for update 2019-003 as well.
Like (1)
Version 2019-003
Markus-Winter
14 May 2019
Works fine as usual
Like
Version 2019-003
stu241
02 April 2019
I have High Sierra 10.13.6. When I try to update with this download, it comes up with "ALERT. This update requires macOS version 10.12". Yet this download is supposed to be for my OS as well? I had previously tried to update in the App Store, but every time I restart my screen goes black apart from my mouse pointer which works perfectly, but nothing happens, it stalls. The only way to do anything is to power off and on again and it loads fine. But as soon as you do a restart, the same thing happens. Help!
Like
Version 2019-002
MichaelFrankel
26 March 2019
This is a seriously buggy POS (for reference, this was on High Sierra). Installed it, seemed to go fine, restarted after the updated, seemed to go fine, shut down my laptop and went to another location, restarted my comuter and it would NOT boot up (said there was something wrong with the Mac OS installation). I had to start without system extensions, open the App Store, and install it AGAIN. There was NO warning about problems with the initial install. Can't you do better, Apple??
Like
Version 2019-002
2 answer(s)
Scion777
Scion777
27 March 2019
I updated three machines - two High Sierra, one Sierra - no problems whatsover ...
Like
domains-3
domains-3
29 March 2019
You might want to look at my replies to Scion777 below. That could have something to do with your experience. Although I didn't have any trouble after downloading/applying a few days ago, I am being prompted to re-install the update as of today.
Like
Scion777
26 March 2019
https://support.apple.com/kb/DL1995?viewlocale=en_IN&locale=en_IN - 2019-002 Sierra https://support.apple.com/kb/DL1997?viewlocale=en_IN&locale=en_IN - 2019-002 High Sierra -- ignore the Dec 5, 2018 date on the page, this is the March 19th correct installer
Like (1)
Version 2019-002
3 answer(s)
Mcr
Mcr
27 March 2019
All, the SHA-256 Hash for the 2019-002 HIGH Sierra update is
de523feb8f01d528bdbf0f52b54775bb19fd73a86de82f14b6e54ef3612fa2c5
Like (1)
domains-3
domains-3
29 March 2019
I'm on High Sierra 10.13.6

I download and applied this DMG a couple of days ago from the URL mentioned here. The checksum matches the one shown here. Machine rebooted itself as is typical for this kind of update. Today, however, App Store indicates the update needs to be applied, despite the fact that the update shows under Updates Installed In The Last 30 days. However, for that entry, there's a lot of missing information:

Security Update 2019-002
Version
Installed March 27, 2019

The version field is empty, as is the detailed description that's typically shown in the column to the right. I've don't recall seeing an update entry with that information missing before.

Anyone else have this experience?

My guess, based upon the fact that Apple had a December date on the download page, and the fact that this update was not immediately available through the App Store for High Sierra until today is that the download mentioned here may not have been the same as the actual release version that's showing up today.

It appears that App Store has already finished downloading the update, and is ready to apply and restart. I would love to find that download to compare the checksums. I've already looked in $TMPDIR../C/com.apple.appstore/, and it's not there.

Does anyone know where the download might be?
Like
domains-3
domains-3
29 March 2019
Well, it appears I was correct in my assessment. The file at the URL for High Sierra is NOT the same file as that was there on 3/27 . I just downloaded it again and compared the two files. Same name. Different size.
The SHA-256 hash for the current file is 27765011d7028a643516e5ac106033b6340ee00f261f8e85ae444653d5a17211
For those of us who installed the earlier file, the missing meta data is probably the reason this happened - considering the file size is minimally different. That explains everything including the update re-appearing in the App Store Updates.
Like (1)
samnangie
28 January 2019
This is great, thanks! Does anyone know where the 2019-001 update from Jan 22 is?
Like
Version 2018-006
1 answer(s)
samnangie
samnangie
28 January 2019
I found it! https://support.apple.com/downloads

http://updates-http.cdn-apple.com/2019/macos/041-31494-20190122-BBE902D6-D788-11E8-B555-8E91F34A5CAA/SecUpd2019-001Sierra.dmg

http://updates-http.cdn-apple.com/2019/macos/041-31491-20190122-BBE902D6-D788-11E8-B555-8E91F34A5CAA/SecUpd2019-001HighSierra.dmg

And Mojave doesn’t get a security update, instead they get 10.14.3
Like
Aargl
12 December 2018
No trace of an Apple Security Update 2018-006 for OS X 10.11.6 anywhere — and I bet the 004 will be the last forever — so why keep on calling this page "For macOS 10.12.6 and OS X 10.11.6"? I've just lost time trying to find it... :-/
Like
Version 2018-006
Flavum
10 August 2018
"Will Apple Security Update work good <sic> on macOS 10.13.4?" I'm guessing it won't. Nice work, MacUpdate.
Like
Version 2018-004
3 answer(s)
Derekcurrie
Derekcurrie
10 August 2018
Each version of macOS has its own version of Apple Security Update. Updates will refused to install on the wrong version of macOS. IOW: Yes, the version for 10.13.4 will work good on 10.13.4. If you haven't installed it by now, get to it ASAP.
Like
Flavum
Flavum
11 August 2018
My comment concerns MacUpdate's description of this entry - "For macOS 10.12.6 and OS X 10.11.6". So no, it won't work "good" for macOS 10.13.4.
Like
B-Jefferson-Le-Blanc
B-Jefferson-Le-Blanc
11 August 2018
If you are using High Sierra, available updates will show in the App Store. As they will, for that matter, for other versions of the macOS. I download these because I like to archive them for use on client's computers.

Of course, why MacUpdate hasn't updated their links, well that's anybody's guess. MacUpdate Desktop hasn't worked for some time now. I get a connection error when I look for updates. Maybe everybody is on vacation and their skeleton staff can't handle the workload.
Like
Derekcurrie
10 August 2018
Yes, Apple Security Update Version 2018-004 is from a month ago, July 9, 2018. You are not hallucinating. You most likely already have it installed.
Like (3)
Version 2018-004
1 answer(s)
rardin
rardin
10 August 2018
I've been leaning on the MacUpdate crew to update this entry for weeks. I let them know early yesterday morning that they still need to update the download link at the top of the page and add a link for the El Cap version in the Related Links section, but so far have received no love. In the meantime, the updates can be downloaded from the Apple pages I referenced in my comment below dated Jul 13, 2018.
Like (1)
Mcr
09 August 2018
When applying SecUpdate2018-004 to previous SecUpdate2018-003 installation on El Capitan, HEADS UP. There were TWO SecUpdate2018-003 updates for El Cap, an initial and a slip stream version that Apple very quietly slipped in to replace the initial one a few days later. If you installed the initial SecUpdate2018-003 download, the build number shows 15G21012, if you waited and downloaded it after Apple replaced it with the new one, the build is 15G21013 when completed..

NOW, if you try manually try to run SecUpdate2018-004 over SecUpdate2018-003 build 15G21012, it will refuse and say the SecUpdate2018-004 update can not be installed. Run it over SecUpdate2018-003 build 15G21013 and no issues. I had to first RE-APPLY SecUpdate2018-003 (the newer one and the one you get currently if you download a fresh copy from Apple) to get the build number from 15G21012 to 15G21013. Then I was able to apply SecUpdate2018-004 (which results in build number 15G22010 btw).

I don't know if it would have worked had I gone through MAS ; I always apply my updates by manually running the installer BECAUSE I always boot from another drive to run update. That's a tip everyone should follow, i.e. never boot from and install an update to/from the same boot partition. In my experience, this virtually eliminates the reports you hear about the update taking forever, and or the system taking forever to reboot, or runs slow after the update. This is because by booting from a different drive, the one you are updating is completely accessible and files can be updated quickly without delay. If you try to update the same drive you boot from, not all files can be updated first time around because the system is still running, its like trying to replace a rug while you are still walking on it. it takes a few reboots and a lot more time before everything is updated. With disk drives so inexpensive and HUGE these days, there is no excuse not to have an external boot drive or to divide your existing internal drive into multiple partitions, plus macOS is SO easy to clone and excellent cloning software is readily available (Chronosync, SuperDuper, CarbonCopyCloner to name just a few). In any case, for emergencies, you should ALWAYS have another boot option available to regain access to your working partition in case of trouble.
Peace.
Like
Version 2018-004
rardin
13 July 2018
SecUpdate2018-004 has been out since July 9, but the MacUpdate crew hasn't gotten around to adding it yet, so I thought it would be worth posting links to SecUpd2018-004ElCapitan: https://support.apple.com/kb/DL1972 and SecUpd2018-004Sierra: https://support.apple.com/kb/DL1971
Like (2)
Version 2018-003
MichaelHaeusler
14 June 2018
Weirdest security update ever (2018-003): the installation (onto an HDD) was very fast, faster than usual, but login into my main account—and I'm not kidding—took 6 (six!) hours for even my Desktop to show up, two more hours for all the startup items and scripts to load/run, and the machine was sluggish for many more hours. Now it's all good again, snappy & stable. But if you get the spinning beach ball for seemingly forever, don't force-shutdown, just wait it out, go to work, go party, read a book.
Like
Version 2018-003
Mcr
04 June 2018
As of June 4, 2018, this MU listing is incorrect. It is actually Security Update 2018-003 for Sierra and El Capitan is the most current. For High Sierra, the fixes are included in 10.13.5 update.

2018-03 for Sierra here:
https://support.apple.com/kb/DL1968?viewlocale=en_US&locale=en_US

2018-03 for El Cap here:
https://support.apple.com/kb/DL1967?viewlocale=en_US&locale=en_US

10.13.5 combo for High Sierra here:
https://support.apple.com/kb/DL1965?viewlocale=en_US&locale=en_US

I ALWAYS recommend using the combo updater, even if updating from the immediate prior release, for example, even if updating from 10.13.4 to 10.13.5, I would still using the combo, not the incremental. I've experienced several instances were the incremental is missing necessary files or misses files from previous updates that for whatever reason didn't get updated. The combo by design will check all files back to the 10.x.0 release to confirm all needed files are current. And I always recommend booting from another partition or drive to run updates, i.e. don't boot from the same partition drive you also plan to update; this ensures the partition to be updated is offline and files are all accessible; dramatically reduces the time to run the update, in my experience.
Like (1)
Version 2018-002
2 answer(s)
rardin
rardin
05 June 2018
I contacted Joel about this yesterday and we're working on getting it sorted out.
Like
Jlock
Jlock
05 June 2018
Thank you rardin and MCR and for the assistance. These Security Updates can sometimes be hard to get right!
Like
Jcraig
04 June 2018
Be patient with this one. My early-2011 MBP made a buzzing noise (firmware update?) and rebooted twice. After the second reboot, it seemingly sat dormant with the Apple/gray screen for some time before finally bringing up the login screen. Grab a snack and let the update do its thing, all will be well.
Like (1)
Version 2018-002
3 answer(s)
Cowicide
Cowicide
13 June 2018
How did you update? And, which version OS are you running? It's showing up but I can't download it through the store. Doesn't do anything when I click update.
Like
Jcraig
Jcraig
14 June 2018
Hey Cow, I'm still running Sierra - I've got some stuff that won't run on High Sierra. I was able to update through the App Store.
Like
Cowicide
Cowicide
15 June 2018
Thanks for the info Jcraig, must be something with my particular setup causing the App Store issue then.
Like
Scion777
30 November 2017
This does not point to the 2017-001 High Sierra update - which right now is only available via the App Store. This is pointing to the supplemental update released several weeks ago..
Like
Version 2017-001
Thinking-Differently
03 November 2017
If you wish to directly download the update from Apple, try the following URL for the US english version: https://support.apple.com/kb/DL1940?viewlocale=en_US&locale=en_US
Like
Version 2017-001
Yorh Ekin
22 June 2017
My MacBook Pro test machine on El Capitan got VERY hot, ***right after*** restarting and the fans were blowing like totally crazy for minutes and minutes until the whole MacBook broke down. I don't know what Apple is doing ... it's a mess. Even the installation process is a little glitchy. It doesn't run smooth for Apple at the present time. Too many under constructions and Sierra won't solve it. I recommend everyone, make a TC backup BEFORE installing OS related updates Even the migrations from a TM backup didn't work as expected after installing a clean El Capitan. Apple ... it's a total mess.
Like
Version 2017-002
1 answer(s)
Yorh Ekin
Yorh Ekin
22 June 2017
One more thing ... I am VERY sceptical in using my iCloud account as my login to startup a Mac. I did this once. It broke, I was no longer able to access my own user account on my machine and Apple phone Support did not now what to do after talking with them for a long time. VERY VERY VERY critical security issue using your iCloud account to login and boot your system to gain access to your data and user account.
Like (1)
For those who wish to download it directly from an Apple web page, the correct URL for El Capitan (OS-X 10.11) is: https://support.apple.com/kb/DL1920 And the correct URL for Yosemite (OSX- 10.10) is: https://support.apple.com/kb/DL1919
Like
Version 2017-002
Helmo-Hass
30 October 2016
Well finally i got it Since 10.10 every security update strangely coincided with the release of new system. and funny thing is each and everyone ended up f******-up the actual os. IS this the new apol strategy to brute-force people moving on the newest one? (mac fans pls do not reply to this, its rhetorical)
Like (2)
Version 2016-002
3 answer(s)
Scion777
Scion777
17 December 2016
Nope - each release ran just fine on all three of my Macs. Seems the problem is with you ?
Like (2)
Helmo-Hass
Helmo-Hass
17 December 2016
OMG you'r so blessed... Scion.
Like
Jsabini
Jsabini
18 December 2016
Hey Scion, read my post below, I had the "lsd quit unexpectedly" error with 2016-001 update also. The new update worked OK for me. But to say it's Helmo-Hass' issue id BS. Do your homework and a bit of research... This problem is well documented in Apple's community support. Don't blame the victim. Anytime there is a kernel patch all kinds of things can happen.
Like
marketing-3
30 October 2016
Great that we get security updates for El Capitan.
Like (1)
Version 2016-002
Adonsa
17 September 2016
The secupd2016-001 update was performed on System 10.11.6 and resulted in a persistent "lsd quit unexpectedly" errors which rendered everything unusable. There are message threads on Apple website containing complaints about the "lsd quit unexpectedly" error, but no definitive solution except to reformat and restore from backup. Recommendation, do what you want, but you might want to have a good backup ready to restore from. Recommendation for Apple Computer - fix the problem.
Like
Version 2016-001
1 answer(s)
Jsabini
Jsabini
26 October 2016
I got exactly this same issue, from a fucking "security update"! I'm so pissed, wasted hours trying to fix it and finally am wiping my internal drive and restoring from a working backup with SuperDuper. Apple, test your shit! This is why I held off on upgrading to Sierra, but problems came anyway. Not sure how long I'll wait now before installing future updates...
Like
outer
02 September 2016
It took me a further full Restart to get things back to expected (for example, ntpq was timing out waiting for localhost to deliver data). Apart from that, no problems. sw_vers now reports 10.11.6 (15G1004).
Like
Version 2016-001
Fred-Dalzell
02 September 2016
Security Update 2016-001 for El Capitan Something weird - when I updated using this download, Safari was still 9.1.2. App Store still showed it wasn't installed, so updated through store and now Safari is 9.1.3.
Like
Version 2016-001
Mac-Freak
16 May 2016
Security Update 2016-003 Mavericks http://support.apple.com/downloads/DL1878/en_US/secupd2016-003mavericks.dmg Security Update 2016-003 Yosemite http://support.apple.com/downloads/DL1879/en_US/secupd2016-003yosemite.dmg
Like (3)
Version 2016-002
1 answer(s)
Solutionscts
Solutionscts
17 May 2016
Thank you!
Like
slobjones11
24 March 2016
Allowed my MacBook Pro running Yosemite 10.10.5 to install Security Update 2016-002 today. Tonight I find I'm only getting audio from the left channel of my headphone port. Deleting audio plists provides no relief. Anyone else experiencing this problem?
Like
Version 2016-002
1 answer(s)
Big Johnson
Big Johnson
17 December 2016
What? You’re still using an actual computer?
Are those still a thing?
Those were so 2000’s!

Don’t you know that Crapple is leading the push to force everyone onto mobile devices?

They disabled your port as part of their nefarious plan to rid the world of headphone jacks, thus stimulating sales of wireless Beats and AirPods.

RESISTANCE IS FUTILE!
You WILL be assimilated into the Apple collective.
Like
Low-Flyer
22 January 2016
Security Update 2016-001 for Yosemite was posted by Apple on Jan 19, 2016 (https://support.apple.com/kb/DL1856?locale=en_US), but three days later still not available for update by App Store.
Like
Version 2016-001
Aarrd
21 January 2016
Be aware this could break your nvidia drivers for unflashed graphics cards on 10.10.5. After spending 5 days trying to get my system working the way I want between 2 computers and 3 OS they release this "wonderful" security update 2016 001 and I'm back where I started. Now after looking on the net I found this is a regular occurrence. I wish Apple and Nvidia could just talk to each other to give us some native drivers in the OS.
Like
Version 2016-001
1 answer(s)
Aarrd
Aarrd
21 January 2016
New Drivers here:
http://www.nvidia.com/download/driverResults.aspx/97606/en-us
Like
Bigboysdad
15 December 2015
Well, I'm having to come here to download it because it's impossible to do so from the App Store. Jeez, I sometimes hate that App Store.
Like
Version 2015-006
Mcr
13 December 2015
interesting. 2015-005 is released on Dec 8. 2015-006 is released on Dec 12, FOUR DAYS LATER. Really Apple? What did you not know on Dec 8 that you suddenly know on Dec 12? Or was there an error in 2015-005 that you had quickly correct? If there was an error what does that say about the QA testing for critical things like security updates?
Like
Version 2015-006
Kobalt
09 December 2015
The latest Security Update for Yosemite is 2015-005 1.0 https://support.apple.com/kb/DL1852?viewlocale=en_US&locale=en_US Post Date: Dec 8, 2015 File Size: 369 MB
Like (1)
Version 2015-004
Derekcurrie
14 August 2015
Apple Security Update 2015-006 is for BOTH OS X 10.8 Mountain Lion AND 10.9 Mavericks. It is NOT just for 10.9. And: WHY does MacUpdate have the Mountain Lion logo on this page when it (wrongly) says this update is only for Mavericks??? Cognitive dissonance storm!
Like (1)
Version 2015-006
ianrid
01 July 2015
Two Restarts on this one. But why does it have to make that alarmingly loud tone when the machine first shuts down?
Like
Version 2015-005
Albabe
30 June 2015
It see,s, Today's Security Update kills SIMBL and EasySIMBL.
Like
Version 2015-004
4 answer(s)
sjk
sjk
30 June 2015
EasySIMBL 1.7.1 and plugins (e.g. SafariStand) still work for me on 10.9.5 after installing this update. Their failure is on 10.10.4.
Like
Aargl
Aargl
30 June 2015
I confirm that Security Update 2015-005 breaks cDock on 10.9.5: no more colored sidebar, no more transparent dock. :-(
I've installed EasySIMBL 1.7.1 afterwards but it doesn't seem to cure anything...
Like
sjk
sjk
01 July 2015
Thanks, Aargl. I don't use cDock but noticed there's discussion happening with the developer here, where you've also commented: http://www.macupdate.com/app/mac/51149/cdock
Like
Albabe
Albabe
01 July 2015
I'm in the same boat as Aargl. No more Colored Sidebar or TheLostFinderNewWindow.
Like
Lvdoc
11 April 2015
This might be worth noting, particularly the comment, "Macs running versions 10.9 or earlier remain vulnerable." http://arstechnica.com/security/2015/04/latest-version-of-os-x-closes-backdoor-like-bug-that-gives-attackers-root/?utm_source=feedburner&utm_med
Like
Version 2015-004
MtnManEd
09 April 2015
Downloaded from here and directly from Apple and get the same error during installation: "...can't be installed on this disk. An error occurred while evaluating JavaScript for the package." So, it seems there's an issue with the code in the pkg.
Like
Version 2015-004
wintermute
21 March 2015
**For users of old Mac Pro desktop machines running non-Apple EFI Nvidia cards-- if this is not you, you can probably ignore this.** Apple Security Update 2015-003 will likely break your video drivers. Without the video drivers loading, you will likely reboot to a black screen after installing the Apple Security Update 2015-003. Okay... not sure why this finally worked... I tried installing this "b4" Nvidia Web driver previously and it refused to install stating that I didn't have the correct build of OS X. I tried installing it with Pacifist, and it installed but still no video. I followed the outlined instructions I posted earlier for the "fix" which apparently worked for many others, but still no joy. The system kept reporting that the NVDAstartup.kext was unsigned and refused to load it. After repairing permission and trying a bunch of things, I simply ran the installer for the following "b4" version again... and it suddenly let me install it with no complaints. Odd. And then on reboot, all is working again. Go figure. Here's the link. Make a cloned bootable back-up first and then try installing this driver. If it will let you install it, you are probably good to go. Good luck. http://us.download.nvidia.com/dZAS8cBUHaT1cUk4pr4NBgqTMH8PbHXC/WebDriver-343.02.02b04.pkg
Like
Version 2015-003
2 answer(s)
wintermute
wintermute
21 March 2015
Aha... there are two "...b4" drivers... one for 10.10.3 and the one I posted above for 10.10.2. I had tried using the version for 10.10.3 since that was the only newer driver posted in the reference list I originally found. I found the above link at an alternate site but didn't realize it was different at first.
Like
jack-delay
jack-delay
01 May 2015
I have macvidcards 780ti on aMacPro 5,1 (mid 2012) and I had to replace it with Apple card to get 10.0.3 to boot. When I install the latest NVIDIA Web Driver (Apr 22 date) the system crashes on startup. Is the WebDriver-343.02.02b04.pkg you reference above a solution to that problem. I have wasted several days of my times trying about 3 different "solutions" for this problem and then restoring my system from Time Machine in orderto be able to use it. Interestingly (or should I say discouragingly) with 10.0.3 and running without the NVIDIA driver even placing the macvidcards 780ti into the machine crashes OSX on startup. Bummer.
Like
wintermute
20 March 2015
So here's my personal rating since this update killed my Nvidia drivers. Boo to Apple on this one. I understand that the security fixes needed to be made, but the fixes that were made should not have affected the graphics drivers... they dealt with Keychain security, not graphics drivers.
Like (1)
Version 2015-003
wintermute
20 March 2015
If you have an old Mac Pro with a non-Apple EFI Nvidia card, first create a cloned, bootable back up of your system to be sure you can boot back up as you are now. Second, either install an Apple EFI Video card or turn on Remote Access and have another mac available to remote in if needed. Third, install the Nvidia web driver from here:
http://us.download.nvidia.com/Mac/Quadro_Certified/343.02.02f03/WebDriver-343.02.02f03.pkg

Fourth, install the security update.

Finally, follow these instructions to enable the Web driver with the new build number of OS X which changes after the Security Update:

http://www.tonymacx86.com/graphics/159885-security-update-2013-003-breaks-nvidia-web-driver-again.html

Good Luck!
Like
Version 2015-003
1 answer(s)
wintermute
wintermute
20 March 2015
**UPDATE** So, while some have said this method works for them, unfortunately, it did not in my case. This method does seem to allow the web driver to load, as I can see that when I use Remote Access. However, while the driver is allowed to load, Apple changed something else so that the Nvidia Web drivers and Apple's default Nvidia drivers both will no longer work with my Nvidia Geforce GTX 660 graphics card. Is Apple trying to force us to buy a new Mac Pro? Almost seems like it. I wouldn't mind upgrading if the new Mac Pro had multiple internal drive bays like the old model... I don't want to spend an extra $500 on an external Thunderbolt 2 quad bay enclosure, another $$ on extra RAM, in addition to the cost of a new MacPro, especially when the old Mac Pro hardware is still working fine.

Glad I have the bootable back-up. Hopefully, Nvidia will release an updated Web Driver to resolve this issue soon.
Like
JBX
20 March 2015
Kills Nvidia drivers!
Like (1)
Version 2015-003
1 answer(s)
wintermute
wintermute
20 March 2015
Yep. I can confirm that with my non-Apple Nvidia card, the supplied Apple drivers do not work and the previous Web drivers are disabled. Be sure to clone your boot disk and have a way to access your Mac Pro in the event that you reboot to a black screen. (Either install an Apple EFI graphics card or at least turn on Remote Access.) You can also try loading Nvidia Web Drivers for OS X 10.10.2 Build 14C1514, if they are out yet, before you attempt the update.
Like
Despite what it says at the top of this page, this update is for Yosemite only.
Like
Version 2015-003
Solutionscts
20 March 2015
The Mavericks update still exposes the mach.kernel which has to be re-hidden through terminal. That's a real pain when you have 50 plus Macs to update!
Like (1)
Version 2015-003
2 answer(s)
rardin
rardin
20 March 2015
The Mountain Lion and Mavericks updates are still SecUpd2015-002, unchanged from March 3, as far as I can tell. It appears that SecUpd2015-003 is Yosemite-only.
Like
Albabe
Albabe
20 March 2015
Rardin:

It doesn't update thru "Software Update" in Mavericks, so you are likely right!
Like
wintermute
19 March 2015
Another Security Update is out... 2015-003 1.0 Anyone know if this breaks the non-Apple Nvidia drivers again?
Like
Version 2015-002
1 answer(s)
wintermute
wintermute
20 March 2015
So I tried it after cloning my boot disk... Yep, the 2015-003 1.0 security update does indeed break the Nvidia drivers once again. PITA!
Like
wintermute
12 March 2015
I can confirm that this latest security update, 2015-002, does indeed break the graphics drivers for users using non-Apple EFI Nvidia graphics cards. Users on old Mac Pros with non-Apple EFI Nvidia cards will likely reboot to a black screen after the update. Be sure you have a cloned, bootable back-up on hand before attempting this update or have an Apple EFI videocard installed.
Like (1)
Version 2015-002
DigiMonk
11 March 2015
Update installed successfully on a MBP 17'', Mid 2010 - it downloaded the update, rebooted to install it and rebooted again after and showed the configuration setup where you can put in your Apple-ID password to auto-configure everything related.
Like
Version 2015-002
Lounge-Deluxe
11 March 2015
Just a warning about this security update, it bricked my MBP mid 2014. My system restarted after the security update installed through the App store, then it showed a progress bar for a few seconds and then it just shows a black screen with a white prohibitory sign. Booting into recovery mode and repairing disk does not help, it won't even boot into single user mode. Of course my backup disk is in a storage unit as I'm in the middle of moving to a new house... Dagnabit! So back up first (as always) :-)
Like
Version 2015-002
4 answer(s)
Tony-Cellini
Tony-Cellini
11 March 2015
Hello.
Surely you have modified Kext signing in some way. For example you could have activated Trim for a non-Apple internal SSD and this is what you got....
You can find online some solution (you have to manage it with Terminal, of course) or you can reinstall the OS from Zero.....
Like
Lounge-Deluxe
Lounge-Deluxe
11 March 2015
Thanks for the suggestion, in the end I decided to reinstall as it's quicker than a trip to the storage unit. I don't think I've had trim enabler installed though, trim on the factory installed ssd worked natively.
Like
Tony-Cellini
Tony-Cellini
12 March 2015
Maybe some hacks/cracks that have something to do with Kext signing then....
Like
Lounge-Deluxe
Lounge-Deluxe
20 March 2015
I only have legitimate software installed if that's what you mean.
Like
Lounge-Deluxe
11 March 2015
Just a warning about this security update, it bricked my MBP mid 2014. My system restarted after the security update installed through the App store, then it showed a progress bar for a few seconds and then it just shows a black screen with a white prohibitory sign. Booting into recovery mode and repairing disk does not help, it won't even boot into single user mode. Of course my backup disk is in a storage unit as I'm in the middle of moving to a new house... Dagnabit! So back up first (as always) :-)
Like
Version 2015-002
1 answer(s)
Tony-Cellini
Tony-Cellini
11 March 2015
Hello.
Surely you have modified Kext signing in some way. For example you could have activated Trim for a non-Apple internal SSD and this is what you got....
You can find online some solution (you have to manage it with Terminal, of course) or you can reinstall the OS from Zero.....
Like
kabdog
10 March 2015
iTunes no longer sees my iPhone. Thanks, Apple.
Like
Version 2015-002