Previous 1 2 3 4 5 6 Next 89 Replies Latest reply: Jan 25, 2013 11:56 PM by patH72 Go to original post
  • Luis Rendon Level 1 Level 1

    Wow thank God I didn't install this thing. I've worked in the past on firmware and I know that one single typo on the code can make a mess of it, so decided to wait. Today my machine alerted me of a new update and I thought it had been the same update I neglected (the one that affected everybody) but I went to the app store and nothing showed up. Hopefully apple is going to take note on this one and don't release such updates lightly. Now I assume that that patch, had it worked alright it was meant to address issues; I hope they release a working one later. I know that the one they released afther the original fiasco was only meant to address the problems that the first one caused.

  • patH72 Level 1 Level 1

    The "Supplemental Update" which was released yesterday did not fix the "lid closing wakes hard disks and displays" problem which the MacBook Pro Update 2.0 introduced. It's very disappointing that Apple would relase an update which does not fix all the problems, quite a number of which have been described here). Just take us back to the way it was before.

  • mpcnz Level 1 Level 1

    A new version of this update has just come out.  Has anyone tried it out?

  • Luis Rendon Level 1 Level 1

    Not yet, I have not installed anything in the firmware realm. Curious to see if anyone has anything to report.

  • mizzer-d Level 1 Level 1

    Has anyone tried it?  Bwahahaha.  That might be the funniest thing I've read in a while.


    Seriously, though, ever since being burned by the last update, I think I'll wait several months before considering this one.

  • RickyB. Level 1 Level 1

    I installed it almost immediately, and it fixed all of the major issues on my Retina MBP (including keychain, etc.).

  • eltsac Level 1 Level 1

    After the original update which caused the problem, I did a fresh install of 10.8.2 over my existing system, and it got back to normal. When the "OS X 10.8.2 Supplemental Update 2.0" came out, I again installed the MacBook Air/MacBook Pro 2012 Update 2.0 (the wonky one), then immediately restarted and installed the Supplemental Update 2.0. Smooth sailing, and it's been working fine for well over a week now.

  • ampdeck Level 1 Level 1

    seriously up until now Apple has'nt fixed the HDMI display output issue. I'm still not able to use my external display via HDMI.. its almost two months now boooooooo very very disppointing!!!!

  • Adel Sabry Level 1 Level 1

    I bought a Core i7 Macbook pro 15" mid 2012 non retina model, with 8 GB RAM,


    It has Intel HD 4000 512 MB VRAM and Nvidia GT-650M 1 GB VRAM


    Apple released ( MacBook Air & MacBook Pro Update 2.0 ) for mid 2012 model


    It is not a firmware update...


    The results after the update ... Intel HD 4000 384 MB VRAM instead of 512 MB


    I reinstalled the OS 10.8, 10.8.2 combo update again, and did hide the MacBook pro update 2.0


    The VRAM of the Intel HD 4000 came to 512 MB


    so in my case


    8GB RAM -> 384 VRAM After update

    8GB RAM -> 512 VRAM Before update


    which is better ??

  • patH72 Level 1 Level 1

    I see that I have 384 MB of VRAM as well, having installed the update some time ago.

  • Luis Rendon Level 1 Level 1

    Anyone else that has a rMBP and has applied this patch successfully ?

  • mpcnz Level 1 Level 1

    Yes, I risked the new version of this update a couple of weeks ago.  No problems since then.

  • Luis Rendon Level 1 Level 1

    Thanks a bunch mpcnz, going to give it a try.

  • SwankPeRFection Level 4 Level 4

    This update also causes another Power Mangement issue that people are finally starting to notice.  Below are the details...  And no, the new version of the update doesn't fix this problem.  The rereleased version only fixes the keychain issue mainly that was introduced in the first release of this update.





    This is a problem with all 2012 MacBook Pros that have applied the update DL1609 via Software Update.  This update is called MacBook Air and MacBook Pro Update 2.0.  The only fix that exists for this is to reinstall OSX and just not install this update when it shows in the available updates list in the AppStore.  Just hide it until this issue is fixed by Apple.


    If your OSX 10.8.2 version is anything after version (12C60) then you will have this problem.  The problem is as follows.  With the system asleep with clamshell closed, plugging and unplugging the power cable causes the system to wake up and go back to sleep.  Additionally, leaving the system plugged into power for over 4 hours will cause the system to go into hibernation, but only when plugged in.  If it's not connected to AC power while sleeping for that long, it will not enter hibernation.


    Please call Apple and complain about this problem.  I have been working with them for over a month and a half trying to get them to fix this and it's a major hand-holding process because they didn't initially understand the issue.  Add to that the fact that they insisted that this problem doesn't exist and it just made it that much harder to get them to see the issue.


    You need to call them AppleCare and let them know you're having this problem.  Along with that, email the rep you're working with links to every Apple Support Forum thread you can find on this.  Trust me, there are several with this same exact problem.

  • patH72 Level 1 Level 1

    Yes, I have a problem. Closing the lid of a sleeping MacBook Pro wakes it up as well as attached hard disks, causing unnecessary wear and tear on the drives, after which it immediately goes to sleep. I've filed a bug report with Apple but there's been no response.


    I can't see why they need "proof"of this. Any MacBook Pro with the so-called Update 2.0 applied will have these problems.

Previous 1 2 3 4 5 6 Next