MBP Mid 2012 on El Cap. Thanks for not throwing us under the bus.
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 Addresses Meltdown and Spectre in macOS Sierra and OS X El Capitan With New Security Update
- Thread starter MacRumors
- Start date
- Sort by reaction score
So, no fixes for Yosemite...
Is it possible to just get El Capitan or Sierra instead of the useless High Sierra...?
Is it possible to just get El Capitan or Sierra instead of the useless High Sierra...?
Not sure if it works on all versions but if you go into 'About this Mac' and hit the software version number it will then show the build number.
Yes, fortunately you can still get those installers:
https://support.apple.com/en-us/HT208202 (Sierra)
https://support.apple.com/en-us/HT206886 (El Capitan)
Why not complain?. It is at best a half-hearted security measure?. They are having folks walk around with equipment they think is secure but isn't? Equipment that can more easily be hijacked and used to attack others and digital infrastructure. At a certain point it is more dangerous to and just leave these systems out their and apple should be faulted for enabling this false sense of security.
Apple needs to get off their butt and tell people to recycle systems they hand left behind,
I shouldn't really reply to someone that joined in October 2017 only to post criticism (not a single positive post).
However, I will point out that one could say all security measures are "half-hearted" in that they address an issue (or a group of them) when many others are either in the pipeline or about to be discovered.
If you cannot get to terms with this fact of computing life then perhaps you should give up computers altogether.
I hate to point out the obvious, but when I am not happy with a service provider I usually move to one that I perceive to be a better one. Have you considered this as an option?
Same here. Black Screen of Death every 3 minutes.
Thank you so much, Apple, for rendering a 5000$ mac pro system useless.
Starting time machine now.
[doublepost=1516792188][/doublepost]
Please let us know. I've reinstalled my old system after kernel panicks.
So I put ESET back on this morning and it was working fine up until I plugged my iPad Air 2 in to charge and within about 60 seconds it started with the rebooting again. Strange thing is it would still do it even after a restart with the iPad removed. So I restarted to safe mode which I had to activate via Terminal as Shift during boot is being ignored and removed ESET yet again and its been fine for a few hours since then.
I've had a peruse of the ESET forums and see no mention there yet of the Black Reboot Screen, so I'll leave it uninstalled for now, I don't have the time to research it any further at the moment. Glad I didn't have to resort to a reinstall and restore of my Carbon Copy Clone, that would have pissed me off.
Thanks for your reply!
I was startled by your ESET comment, as I use it too, seems to be that you hit a good spot. I'll postpone the update for now. I just need to be able to work.
Maybe I'll install it later and I'll watch the ESET forums too. Thanks! Alex.[doublepost=1516793647][/doublepost]
Found something:
https://support.eset.com/alert6654/
Thanks, I'll wait for them to fix ESET then, I'm not updating to High Sierra, I might as well throw the laptop off the roof it would be more reliableThanks for your reply!
I was startled by your ESET comment, as I use it too, seems to be that you hit a good spot. I'll postpone the update for now. I just need to be able to work.
[doublepost=1516793647][/doublepost]
Found something:
https://support.eset.com/alert6654/
I'm good with the El Capitan update, but will add that I've only been running for about an hour now.
Help! my MB Pro mid 2010 does not start OS after installing patch. This happened for the first time after 7 years of use. Reboot does not help
UPDATE: this is how I fixed it: I had to enable safe mode from bootable install disk (using Terminal and nvram command). Then after starting in safe mode installation process resumed and finished. Then again I had to turn off safe mode with nvram.
UPDATE: this is how I fixed it: I had to enable safe mode from bootable install disk (using Terminal and nvram command). Then after starting in safe mode installation process resumed and finished. Then again I had to turn off safe mode with nvram.
Last edited:
Open System Information (hold option/Alt + click the apple menu), scroll down to Software>Installations, then view by install date - everything appears there, inc security updates, gatekeeper updates etc.
I will not be updating any of my Apple computers for a while as I know this patch was rushed out. I'll take my chances getting hacked in the meantime.
To be fair its a problem I had with my Anti Virus software, ESET Cyber Security Pro was causing the reboots, ESET have admitted the problem. I think if you don't use ESET then you may be OK. They have said they are working on an update to fix the problem. My Macbook has been running all day now without issue.
Since when does being a forum member for a short period of time exclude my opinion? I've been in IT for 28 years. I started with Linux and I've been a Mac user for 7 years now. I'm heavily invested in them. Switching isn't A) cheap nor B) is my opinion not the source of the problem.
I am asking for Apple to just be more transparent. As an example, pick the last year of the OS release your running that isn't the current OS, then add up all of the discovered vulnerabilities in the following years and those are the holes you are running with. e.g. a 2015 OS has 540+ holes Apple will -never- fix. So patching spectre and meltdown isn't throwing anyone a bone.
https://www.cvedetails.com/product/15556/Apple-Iphone-Os.html?vendor_id=49
Cisco is not a perfect company but their EOL policy is transparent and certainly works better than Apples. They could learn something from them.
https://www.cisco.com/c/en/us/products/eos-eol-policy.html
Asking Apple to do better is not picking on them, I'm a very concerned customer. I had to dump a fully functional Mac mini because Apple stopped producing patches. That latest iMessage crash bug, not fixed in Sierra. I now have a new mac.
---
One last thing, I joined in October because of precisely this issue. I want to raise awareness so that Apple improves their response, not continue with it's current fog of a policy.
Last edited:
Same here.Thanks, I'll wait for them to fix ESET then, I'm not updating to High Sierra, I might as well throw the laptop off the roof it would be more reliable
I don't think Apple has ever made any secret of not supporting older versions of iOS.
In iOS' case, vulnerabilities are addressed by newer versions.
As for OSX/MacOS, I thought it was their policy that only the last three versions (including current) are supported, however I cannot find any official information about this. So I agree with you that better clarity would be useful.
In the meantime though, as far as I am aware, El Capitan released in 2015 is still very much supported and patched accordingly.
By the way, I do appreciate the spirit of your concerns.
Whilst it is good to discuss issues with fellow users, it is probably more productive to complain directly with Apple as this is not their website.
Yep, and I'm still waiting for a version of MacOS 7.6 that will run on my SE/30 and other Macs with 32-bit processors but without 32-bit clean ROMS.
They should be out in a few hours, maybe tomorrow, at worst friday. They already issued the latest version of their drivers for High Sierra 10.13.3.