Video Screencast Help

Be aware: Thunderbolt Firmware Update 1.2 issues identified

Created: 14 May 2013 • Updated: 17 May 2013 | 12 comments
sven_frank's picture

Not Working: 

  • MacBook Air Model Identifier 5,2 13"

Working: No other model so far reported but not guranteed   

We have seen two instances of the MacBook Air Model Identifier 5,2 13" model failing to boot after installing the latest 1.2 Thunderbolt Interface firmware update. Please use caution when updating on this model. For more info please see http://www.symantec.com/docs/TECH206300 for more info. 

Important: Installing PGP WDE aka Drive Encryption(default) is sufficent to cause the boot problem the disk doesn't need to be encrypted 

List will be extended and KB Updated if we see more

Operating Systems:

Comments 12 CommentsJump to latest comment

Alex_CST's picture

That's good.  Is there a time frame for 10.3.1?  It was Q2 2013, which is fast approaching the end

Please mark posts as solutions if they solve your problem!

http://www.cstl.com

sven_frank's picture

Hi Alex,

the Release schedule got changed as you might have figured by the now. 

The next Release is 10.3.0 MP2 (10.8.3 is already supported by 10.3.0+) 

Regarding the Release Schedule for 10.3.1 this is delayed since some changes for Windows are getting incorperated. 

Are you waiting on anything specifc for OSX in 10.3.1 ?

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

Alex_CST's picture

Not with regard to OSX, but Outlook 2012 support is a big bugbear atm for our clients

Please mark posts as solutions if they solve your problem!

http://www.cstl.com

sven_frank's picture

Outlook 2013 you mean: Then it seems there is no need on waiting for 10.3.1 will get more specifics soon 

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

Alex_CST's picture

yea 13... :)

Please mark posts as solutions if they solve your problem!

http://www.cstl.com

Alex_CST's picture

I thought Windows 8 + Outlook 2013 support was being introduced in 10.3.1?

Please mark posts as solutions if they solve your problem!

http://www.cstl.com

sven_frank's picture

This was true until some weeks ago. Stay tuned :-)

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

PGP_Ben's picture

Note: We are not compatible with Target Disk Mode via Thunderbolt interface for Symantec Drive Encryption right now. So please be aware of that here is the article on that issue and the related feature request:

http://www.symantec.com/docs/TECH201009

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

PGP_Ben's picture

FYI: We had one report of a 2012 Retina Macbook Pro being bricked after installing the Thunderbolt update released.  This machine had Symantec Encryption Desktop 10.3.0 installed but the drive was not encrypted using SDE. Please use caution in installing this update. I would make sure you have a good time machine backup and another machine to recover with if needed before installing the update.

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

PGP_Ben's picture

Be aware, we have only a report of machine failing at this point. but Symantec would be very interested in hearing the results from testing of other customers on their various hardware also. We have a compatilbility matrix shared on TECH206300 as part of the update being release. If you do decide to test the thunderbolt update on your Mac, please do post your results.

Thank you

If/when you consider your issue resolved, please click Mark As Solution on the most helpful response.

turn1200's picture

I'm seeing the issue on my macbook air 2013 and had to totally re-image it. So this is clearly a major issue. Any updates on when this is going to be fixed?

PRR3's picture

I'm having the same issue with my Mid-2012 MacBook Pro (Retina), PGP version 10.3.0.  At lease I assume it is the same problem - the symptoms sound the same.

I was unable to edit the table for the TECH206300 page as requested.

As a side not to others like turn1200, there is a good chance don't need to totally re-image a broken system. Most likely you only need to rewrite the MBR on the drive back to Apple's default.

There are a couple of ways to do this - my choice is to use the command line. First I reset the NVRAM (just for good messure), then boot into the recovery partition, launch the terminal window and use fdisk's -u flag to update the MBR (you might also have to set the bootable flag with fdisk if the partition is not marked as bootable).

I would be very interested in Symantec's most current option about this - we  are ramping up our deployment and may need to rethink our approach if this continues to be an issue.