my aunt had a similar issue with 10.10.3 - reinstalling the combo update fixed it
Define awful. I am on 10.10.4 on my Late 2010 MBA for the past 10 minutes or so. No obvious degradation in performance. Still pretty zippy.
my MacBook Pro 8,2 also performed a firmware update now show version MBP81.0047.B2A formerly MBP81.0047.B27 also has a new smc version now showing 1.69f4 formerly 1.69f3 i wonder what these updates containMy iMac 2011 21.5" seems to have performed a firmware upgrade during the 10.10.4 update.
It made the very low-pitched beep noise instead of the normal chime, did something for a while, then rebooted. Anyone else see this?
And now System Information now shows "Boot ROM Version: IM121.0047.B21" - newwer than the IM121.0047.B1F which is the latest version shown on Apple's firmware updates page. Anyone know anything about this?
They are full of zip files which will self-unzip in the middle of the night to release Overpriced & sub-standard Beats Headphones, They will then creep over your ears & convince you that a combination of the most expensive Beats Headphones & a Subscription to Apple Music for you, your Family, & everyone you ever saw on Facebook, is the ideal plan for you.my MacBook Pro 8,2 also performed a firmware update now show version MBP81.0047.B2A formerly MBP81.0047.B27 also has a new smc version now showing 1.69f4 formerly 1.69f3 i wonder what these updates contain
A combo updater is an updater that updates 10.10.0 to 10.10.4 (in contrast to the 'normal', differential updater that updates only from 10.10.3 to 10.10.4). Essentially you are re-installing the parts of the OS that got changed with earlier updates as well as adding the changes from the latest differential update.What is the combo update? I did the update through the App Store on my rMBP, I don't know anything about a combo update. Thanks
To those of us with Samsung 8xx SSD's, I just found some disturbing comments about enabling TRIM (see the comments on the linked ARS article). It may not be "healthy" for those drives afterall?
http://arstechnica.com/apple/2015/0...lows-you-to-enable-trim-for-third-party-ssds/
Yeah, funny, under audiobooks if you choose "authors" it just gives the list but no books to the right. Go to Playlists and all the books are there.iTunes 12.2 is out.
To those of us with Samsung 8xx SSD's, I just found some disturbing comments about enabling TRIM (see the comments on the linked ARS article). It may not be "healthy" for those drives afterall?
http://arstechnica.com/apple/2015/0...lows-you-to-enable-trim-for-third-party-ssds/
My iMac 2011 21.5" seems to have performed a firmware upgrade during the 10.10.4 update.
It made the very low-pitched beep noise instead of the normal chime, did something for a while, then rebooted. Anyone else see this?
And now System Information now shows "Boot ROM Version: IM121.0047.B21" - newwer than the IM121.0047.B1F which is the latest version shown on Apple's firmware updates page. Anyone know anything about this?
my MacBook Pro 8,2 also performed a firmware update now show version MBP81.0047.B2A formerly MBP81.0047.B27 also has a new smc version now showing 1.69f4 formerly 1.69f3 i wonder what these updates contain
Thanks. I wasn't sure what doing this entailed.This has nothing to do with kext signing. It's an official, though unsupported, means of enabling Trim by Apple.
Try a SMC and/or PRAM/NVRAM reset.
If you tested 10.10.3 "clean" (meaning you didn't install anything until you tested that the battery would last as it is supposed to) and your battery was still being drained fast, I'd say that is a defective battery not an update problem.
If you did a clean install, then installed everything you had on it before, you put yourself right back in the same boat you were in before the clean install and it isn't an update problem either.
Right article, wrong vulnerability. Thunderstrike was an older issue that was partly fixed by 10.10.2 (CVE-2014-4498), but there was another related issue around boot.efi which may not have been fixed yet (see the earlier Ars Technica article and linked blog post).The EFI updates fix the Thunderstrike vulnerability: http://arstechnica.com/security/201...ost-macs-vulnerable-to-permanent-backdooring/
After some more tinkering with the Terminal, I finally got the system to boot up, and TRIM is enabled. I guess something must have went wrong after I disabled Chameleon TRIM Enabler, and then ran the trimforce command.
Is there a way to check if kext signing is enabled on my system? When I type "nvram boot-args" it says data was not found
my apple store doesn't work![]()
My Mac App Store app seems to be frozen also.
Same here
i did 2 restarts and still the same problem. i press update-restart-show details and we are back again
So stable, an elephant can balance on it!
Is that this?Does this fix the XARA vulnerability? https://www.macrumors.com/2015/06/18/what-you-need-to-know-about-xara-exploits/