Thunderbolt Display firmware update 1.2 failed

Thunderbolt Display firmware update 1.2 fails to complete.  I have made four attempts to load this software update.  The odd thing is that the software list shows that the update has been installed.  But every time I check for updates, Thunderbolt Display firmware 1.2 is listed as a needed update. 

Strange. The downloaded dmg file package said that the upgrade was successfully installed, but the App Store still says I need to update. I haven't tried it with my MBP cover open but I'll give that a shot.
Thanks,
Clinton
MacBook Pro (15” Late 2011), OS X Yosemite 10.10.1, 16GB Crucial RAM, 960GB M500 Crucial SSD, 27” Apple Thunderbolt Display

Similar Messages

  • Thunderbolt display firmware update 1.2 won't install correctly

    On Friday 11/13/2014, I received a Software Update notification in OS X Yosemite 10.10.1 that there was an update available for "Thunderbolt Display Firmware Update 1.2". I tried installing this several times, but every time it tells me "The Thunderbolt Display Firmware Update could not complete." Now I have 6 failed install attempts showing in Software Update, plus still the still to be installed update itself.  
    If I click on the "More info" button in the failed installation message, it takes me to this page: About Thunderbolt Display Firmware Update 1.2 - Apple Support
    On that page it suggest to check the "About this Mac" info for Thunderbolt Display, where "The Firmware Version should be 26.2 and the Port Micro Firmware Version should be 2.0.7 after the update." 
    My Thunderbolt Display is currently on Firmware Version 22.2, with Port Micro Firmware Version 0.0.21. Why won't this update install?

    I had a similar problem: The "Thunderbolt display firmware update 1.2" kept reappearing in AppStore, even though the uppdate seemed successful.
    According to Apple[1] the update was successful when the the Firmware Version is 26.2 and the Port Micro Firmware Version is 2.0.7 (visible in About this Mac -> SystemReport).
    Above versions were correct in my case, but the update still kept appering in AppStore... (probably I did download and install the update manually after the first failure, but I don't remember ...)
    To get rid of the annoying update in AppStore I used the softwareupdate command[2] on the commandline:
        softwareupdate --ignore TBdisplayFWUpdate1.2
      [1]: https://support.apple.com/en-us/HT204450
      [2]: https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/ man8/softwareupdate.8.html

  • Thunderbolt Display Firmware Update 1.2

    I have a MacBook Pro (Retina, 15-inch, Mid 2014) and two thunderbolt displays. I recently started getting notified there was an update available, Thunderbolt Display Firmware Update 1.2 and App Store kept prompting me to download and install.
    I tried multiple times, and each time it states it failed to update. According to this KB article About Thunderbolt Display Firmware Update 1.2 - Apple Support it states Firmware Version should be 26.2 and the Port Micro Firmware Version should be 2.0.7 after the update.
    I checked and my Mac is in fact reporting the updates were applied. See information from the system report below. I am prompted every day, multiple times to download and apply this update again, over and over. I don't understand why.
    I contacted Apple Support and the rep I worked with was pretty much useless. In fact, I am fairly sure I know more and *NIX than he does. Anyway, does anyone have a suggestion on howe to remedy this?
    Thunderbolt Bus:
      Vendor Name: Apple Inc.
      Device Name: MacBook Pro
      UID: 0x0001000F04E36360
      Route String: 0
      Firmware Version: 17.1
      Domain UUID: E66642D7-AAB9-2B54-9F69-9854739EA240
      Port:
      Status: No device connected
      Link Status: 0x7
      Speed: Up to 20 Gb/s x1
      Current Link Width: 0x1
      Receptacle: 1
      Link Controller Firmware Version: 0.12.0
      Port:
      Status: Device connected
      Link Status: 0x2
      Speed: Up to 10 Gb/s x2
      Current Link Width: 0x1
      Receptacle: 2
      Cable Firmware Version: 0.1.18
      Cable Serial Number: C4M329400Q3DNWFAG
      Link Controller Firmware Version: 0.12.0
    Thunderbolt Display:
      Vendor Name: Apple Inc.
      Device Name: Thunderbolt Display
      Vendor ID: 0x1
      Device ID: 0x8002
      Device Revision: 0x1
      UID: 0x0001000100955390
      Route String: 3
      Firmware Version: 26.2
      Port (Upstream):
      Status: Device connected
      Link Status: 0x2
      Speed: Up to 10 Gb/s x2
      Port Micro Firmware Version: 2.0.7
      Cable Firmware Version: 0.1.18
      Cable Serial Number: C4M329400Q3DNWFAG
      Port:
      Status: Device connected
      Link Status: 0x2 / 0x1
      Speed: Up to 10 Gb/s x2
      Port Micro Firmware Version: 2.0.7
    Thunderbolt Display:
      Vendor Name: Apple Inc.
      Device Name: Thunderbolt Display
      Vendor ID: 0x1
      Device ID: 0x8002
      Device Revision: 0x1
      UID: 0x0001000000000000
      Route String: 303
      Firmware Version: 26.2
      Port (Upstream):
      Status: Device connected
      Link Status: 0x2 / 0x1
      Speed: Up to 10 Gb/s x2
      Port Micro Firmware Version: 2.0.7
      Port:
      Status: No device connected
      Link Status: 0x7
      Speed: Up to 10 Gb/s x2
      Port Micro Firmware Version: 2.0.7

    Strange. The downloaded dmg file package said that the upgrade was successfully installed, but the App Store still says I need to update. I haven't tried it with my MBP cover open but I'll give that a shot.
    Thanks,
    Clinton
    MacBook Pro (15” Late 2011), OS X Yosemite 10.10.1, 16GB Crucial RAM, 960GB M500 Crucial SSD, 27” Apple Thunderbolt Display

  • Thunderbolt display firmware 1.2 install error not "connected directly"

    I have tried with 2 macs today to install the Thunderbolt display firmware update 1.2. My firmware is old (22.2) and I have had display problems since Mavericks (now with Yosemite too), so I would really like to try the new firmware.
    With the TB Display directly connected with a single TB cable to a mac mini or alternately directly connected to my MB Pro I get the error:
    I have tried to use both software update and a downloaded version of the Firmware update. Both have the same error message issue on both of my computers. Also, software update keeps showing the firmware as a recommended update after the failed installations.
    Does anyone know a fix to this?
    Thanks

    Solution:
    As I proofread my post, I realized I did not note the part about the "built-in" cable and only focused on the "connected directly" part of the error.
    Using the built-in Thunderbolt cable I was able to successfully install the firmware.
    If anyone else makes this dumb mistake, maybe this post will help you not feel too bad!

  • Thunderbolt Display Firmware 1.2 / 10.10.1 Update device connected but no display

    I looked through a lot of the Thunderbolt Display Firmware 1.2 posts about the display not functioning but never saw one with circumstances quite like mine. In my case, I updated the firmware and the display continued working until I had to reboot for the 10.10.1 system update. After the reboot, my display stopped displaying.
    The display wasn't completely non-functional. The symptoms I saw were:
    The Displays system preference only showed one display available (my rMBP)
    The System Report under About This Mac showed my Thunderbolt Display was connected
    The keyboard connected through the Thunderbolt Display worked properly
    Just no display at all. First I tried a simple reboot with no success. Then I tried a PRAM reset (3x) again with no success. Finally I disconnected all Thunderbolt connections from my rMBP and did an SMC reset. After booting back up I reconnected the display and boom back in business!
    Hope this helps someone.

    Solution:
    As I proofread my post, I realized I did not note the part about the "built-in" cable and only focused on the "connected directly" part of the error.
    Using the built-in Thunderbolt cable I was able to successfully install the firmware.
    If anyone else makes this dumb mistake, maybe this post will help you not feel too bad!

  • HT6093 the new thunderbolt display firmware NOW makes my screen go black all the time!!!  how can I uninstall this last update?

    the new firmware for the thunderbolt display now is making the screen go black all the time.  _the fix created the problem!!!
    how do I uninstall this update?
    Jon

    You can't.  There is a long discussion in the Thunderbolt forum.  Look there.

  • HT6093 Updating two Thunderbolt display firmwares

    I have two Thunderbolt displays, one at work and one at home. I updated the firmware of the work one, and want to update the firmware of the home one.
    With the Macbook Air clamshell open and the display plugged in, the App Store at home says that the update has already been applied.
    Suggestions?

    Yes, the firmware is the old firmware, because the update never ran on the home display.

  • No sound from Thunderbolt Display after update to OS X 10.9.3

    So I updated to 10.9.3 this morning only to find there is no sound coming from my Thunderbolt Display after installation. Sound is now only audible from my MacBook Pro (late 2011). Also, see image below, there is no sign of any connected inputs other than my MBP now. I've shutdown and restarted a number of times, but still no audio from the display.
    Really starting to wonder why it's worth spending so much on Apple products now...

    I sent my TB Display in for repair. They had it almost a week and didn't find anything wrong with it. Instead they took in my MacBook Pro and replaced the logic board (2nd time it had been replaced) and the Display seems to be working fine now.
    ...except that for using 3rd party video conf apps, those apps only pick up the MBP camera (even though i try to change settings in app), not the TBD camera... but FaceTime and Skype find the TBD camera.
    Strange.
    Nickkett wrote:
    I Bought all Apple to be 100% compatible and "Just Work"...
    I completely agree with that sentiment. That's why we pay through the nose for their products, so it feels very bad when they don't just work.

  • Fix for Thunderbolt OTA firmware update , when receiving an error message

    Hi, my name is Lou, and I'm not sure if this is the right place to post a solution or fix for Thunderbolt users that are unable to get their firmware update OTA..
    For the last 2 weeks, when i got word that the (OTA) Over The Air firmware update should be coming out, i started going on my phones setting to check for new updates and started to receive an Error message, stating to check back when service was available, well Verizons attempt at fixing the issue was to to a hard factory reset, which didn't work, they also had me go to the local Verizon Wireless store and switch out my SIM card, and that didnt work, and they also tried Forcing the update to y phone, and again No resolve.. There last solution was to send me a refurbished phone, which I am strongly against, cuz I dont want a used piece of equipment, ... well anyways, I found the solution for the fix of getting the update downloaded to your phone, from www.thunderboltforums.com ,
    You first need to downlaod an app from the market titled LTE On/Off app, install it. Once installed, I turned of my WiFi on the phone, then opened the LTE On/Off app, and rememer the original setting that its on, bcuz thats the setting u will have to set it at, when your update begins...   Select the CDMA mode, not the CDMA(PRL) mode...  then exit the app.... By selecting the CDMA mode only, this should make your either 3G or 4G signal switch to a 1X symbol.. then, i restarted my phone, .... i dont think restarting is necessary, but i did it anyways... when it restarted, the signal setting was still at 1X, then I went to setting, aSoftware Update, then Check Now, and within a minute or so, the Download option appeared.  once I started the downlaod, I let about a minute pass by, then I went and opened one last time, the LTE On/Off app, and switched the setting to its default setting, and mine was the 4G option and the 4G signal kicked in, and the 78Mb download completed within 3 minutes...  hopes this helps... It helped me...

    I could be wrong but I believe this has been covered but thanks for sharing still...

  • Built-In Keyboard Firmware Update 1.0 fails with error 23:3 on MacBook 2,1

    I attempted to install "Built-In Keyboard Firmware Update 1.0" on two laptops tonight.
    Macbook Pro 3,1:
    Hadn't experienced the issue that the firmware would resolve. Installed the update anyway, successfully, and continued to have no problems since.
    Macbook 2,1:
    Hadn't experienced the issue that the firmware would resolve. Tried to install the update, but it failed with error "23:3". After the failure, the keyboard was non-responsive for about 30-60 seconds, during which time I assume it restored/re"booted" itself. Keyboard function was restored automatically after this time, though there was no indication that it would return, and I had to suffer a minor sweat. Still, I didn't learn I power cycled the system and tried again, but the update never installed successfully.
    Lessons learned -
    If it ain't broken...
    That said, Apple seems to have designed their hardware well enough to be able to recover from a failed firmware update. In this case, you just have to pray a little until the keyboard responds again.
    Apple: be so kind, let us know what 23:3 means, and if needed, update the Firmware Updater.
    //

    Hi,
    I was just wondering how you were able to get the macbook to accept the update? I had to take mine to apple store and get entire keyboard and trackpad replaced in my macbook. They then told me to ignore the update cause they did not have any other keyboards to replace if it happened again.

  • Thunderbolt Display Firmware 1.2 broke the USB inside the display.

    So, I've had problems with this working since it came out.
    I'm running a MBP Retina, 10.0.1 Yosemite.
    TB Display (TBD) is on FW 1.2.
    Just figured out,
    When the MBP sleeps, then wakes, the USB inside the TBD is dead...no more.
    Here's the things that won't work:
    Audio
    The ports (USB) on the rear of the TBD.
    The Display FaceTime Camera.
    This also kills the ports on the MBP until the TBD is disconnected...then everything on the MBP is fine.
    Reconnect TBD, it works fine too...until the MBP sleeps...then it dies.
    Anyone know how to downgrade firmware?
    I've also checked the system report, everything is showing "connected" ... and all the firmwares are current.

    Have you tried o boot in recovery mode with Option down? when I do that I don't have the choice anymore to choose the startup disk. I discovered that On most portables, a yosemite install will convert your hard drive or SSD into a core storage volume.  A core storage volume is used for things like fusion drives and more importantly file vault encryption. It seems that this core storage volume is the cause of the power loss in the TB display. I found out that
    It is possible to revert the CS volume back to a normal volume (if you haven't encrypted it yet). I did that and all the power problem in my thunderbolt display are gone!
    Run these 2 commands in a terminal.
    diskutil cs list
    and then
    diskutil coreStorage revert lvUUID
    where lvUUID is the last lvUUID reported by the previous Terminal command.
    Then restart for everything to get back to normal after you have run these commands in Terminal.
    Then also the recovery partition will show up again in the startup manager when you boot up with the option key.

  • Thunderbolt Firmware Update 1.2 fails with error 0xb

    Can't update on my MacPro (2013) with OSX 10.9.5. Stuck on firmware 22.2. When I try to install the update manually I get an error that the update is already installed, but both of my displays are on the old 2011 firmware (22.2). Diving into the event logs reveals underlying problem, but I don't know how to fix. Sugestions? Both displays suffer the black display bug this is supposed to fix.
    2014-12-09 11:29:47.354 TBTUpdateChecker[1317:507] Host board-id = 'Mac-F60DEB81FF30ACF6'
    2014-12-09 11:29:48.185 TBTUpdateChecker[1317:507] J59 at 'IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/BR00@0/IOPP /BR12@9/IOPP/UFS2@0/IOPP/DSB0@0/IOPP/NHI2@0/AppleThunderboltHAL/AppleThunderbolt NHIType2/IOThunderboltController/IOThunderboltPort@5/IOThunderboltSwitchType2/IO ThunderboltPort@3/IOThunderboltPort@1/IOThunderboltSwitchType1' with UID = 0x00010001005d7070 (0x0)
    2014-12-09 11:29:48.185 TBTUpdateChecker[1317:507] Switch already has a valid UID (0x00010001005d7070)
    2014-12-09 11:29:48.186 TBTUpdateChecker[1317:507] UID did not need recovery
    2014-12-09 11:29:48.186 TBTUpdateChecker[1317:507] Found TBTD at route 0x3
    2014-12-09 11:29:48.186 TBTUpdateChecker[1317:507] Checking firmware version
    2014-12-09 11:29:48.186 TBTUpdateChecker[1317:507] TBTD ROM Version = 22.2
    2014-12-09 11:29:48.187 TBTUpdateChecker[1317:507] Firmware not up to date.
    2014-12-09 11:29:48.187 TBTUpdateChecker[1317:507] Will update route 3 with UID 00010001005d7070
    2014-12-09 11:29:48.353 TBTUpdateChecker[1317:507] J59 at 'IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/BR00@0/IOPP /BR10@A/IOPP/UFS0@0/IOPP/DSB0@0/IOPP/NHI0@0/AppleThunderboltHAL/AppleThunderbolt NHIType2/IOThunderboltController/IOThunderboltPort@5/IOThunderboltSwitchType2/IO ThunderboltPort@3/IOThunderboltPort@1/IOThunderboltSwitchType1' with UID = 0x00010001005abfe0 (0x0)
    2014-12-09 11:29:48.353 TBTUpdateChecker[1317:507] Switch already has a valid UID (0x00010001005abfe0)
    2014-12-09 11:29:48.354 TBTUpdateChecker[1317:507] UID did not need recovery
    2014-12-09 11:29:48.354 TBTUpdateChecker[1317:507] Found TBTD at route 0x3
    2014-12-09 11:29:48.354 TBTUpdateChecker[1317:507] Checking firmware version
    2014-12-09 11:29:48.354 TBTUpdateChecker[1317:507] TBTD ROM Version = 22.2
    2014-12-09 11:29:48.355 TBTUpdateChecker[1317:507] Firmware not up to date.
    2014-12-09 11:29:48.355 TBTUpdateChecker[1317:507] Will update route 3 with UID 00010001005abfe0
    2014-12-09 11:29:48.358 TBTUpdateChecker[1317:507] 0x156d Host ROM Version = 19.2
    2014-12-09 11:29:48.358 TBTUpdateChecker[1317:507] Host EFI: 0116.B05
    2014-12-09 11:29:48.359 TBTUpdateChecker[1317:507] 0x156d Host ROM Version = 19.2
    2014-12-09 11:29:48.359 TBTUpdateChecker[1317:507] 0x156d Host ROM Version = 19.2
    2014-12-09 11:29:48.359 TBTUpdateChecker[1317:507] Cannot update because of error 0xb

    There is no "cover" on a MacPro. It is not a laptop. I tried updating one at a time. Failed with the same error.

  • Canceling Cinema Display Firmware Update

    I accidentally selected to update the Cinema Display iSight from the Software Update list but I do not own a Cinema Display. Now every time I start my computer up I get a prompt asking me to connect to a Cinema Display so I can update it's firmware. How do I get this to stop trying to complete the update?

    Go into your login items and remove it

  • Firmware update on WRT160NL fails at 98 percent

    Trying to update my firmware 1.00.01 B15 to 1.00.01 B17. I downloaded the firmware to my desktop (using mac os X 10.5.5) and connected my computer directly to port 1 on the back of the router. I used the Firmware upgrade tool under the Administration tab to upload the new firmware file. The update progress starts but fails at 98%. Any one else experience this?

    i upgrade my WRT160nl with B17 frimware version but after it i cant connect to internet with the this router !!! i back to B15 version but this strange problem is persist.!!!
    i used to my backup file that i had it before (when my setup and internet was good and worked fine) but not happen anything .
    i reset router too (2-3) but it was not good for me too (reset with the key in the back of router)
    please help me
    i'm waiting......
    Message Edited by cygol on 10-26-2009 01:30 PM

  • MacBook Pro EFI Firmware Update 2.0 failed

    Hi,
    I just updated my macbook pro but the System Profiler gives me this version MBP71.0039.B05.
    When the computer is rebooted did a beep. Maybe I've done something wrong.
    I made a new control with Software Update, but it still offers the EFI update 2.0.
    Maybe because I have not connected the computer to the power source, the update fails?

    The system update requires you to be plugged into a power outlet (which it states in the instructions) for the update to properly install. The beep you hear when restarting is the Power On Self Test and the one beep pertains to the ROM, which in this case is being updated so this should be normal. Try re-installing the update while connected to a power source.

Maybe you are looking for

  • How to cancel Rep. manufacturing Insp Lot

    Dear All, I have inspection lot with Inspection Type 13 [Rep. Manufacturing], which is having CRTD PASG status. When I go to menu Insp Lot---->functions - > Cancel this has deactivated/Hide mode. Please suggest how to cancel this lot Regards Honyal

  • Navigator tool bar in jsp.

    i am very new to java. just started, can anyone help me in creating navigator tool bar in jsp. i have created table but i dnt know how to create row in same row.if i close that </tr> i will be in different row and i want to be in same row.if i creat

  • Menu Module v2 support for selected state?

    I can't figure out if menu module v2 supports the selected state. I remember reading somewhere that it was slated in the future, but it seems the file /ModuleTemplates/Menu/Default/container.html has accommodations for it. A resource if so, would be

  • Double pictures on iPhone5 after syncing

    I just synced my iPhone 5 with iCloud and now I have two of every picture in photo stream on my phone...how do I get rid of this

  • Doing mathematical formulas with numbers stored as strings

    Hi Everybody. I know I must be doing something stupid here, but I just can't see it. I'm just trying to do a simple maths formula of one number divide by another. However, one of the numbers is stored as a string. I have tried  'X' / Ccur ({'String'}