Which Hub Upgrade For 2016 C-Max Energi?

Hi, I’d like to add a CarPlay-compatible hub to a 2016 Ford Cmax Energi. Last year I updated the software from 3.0 to 3.4 and now have that annoying “Unsupported Hub” error.

The PN on my current hub is GC3T-14F014-BB.

From what I’ve read on this forum and elsewhere, the HC3Z-19A387-D/E/F would all be suitable replacements, with the E variant being the favorite.
Is this correct? I want to be absolutely certain before buying something I can’t return.

Also the form asks how I updated but it was over a year ago and I don’t remember.
Screenshots attached.


SYNC Region: NA

Navigation Variant: Non Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.18093

New SYNC Version: 3.4.2210

Do you have a error message, if so what is it?
“USB Hubs are not supported. Please Remove”

Update Method: Official Ford

You just need the current REV of part, they are all physically the same.

Current rev is -H

Oh, I see, so they keep issuing revisions.

Does every revision of HC3Z-19A387-x have dual-USB-A ports or do newer ones have Type-C?

And just to be clear, is the absence of this USB hub the only thing preventing CarPlay from working?

That is to say, will CarPlay immediately spring to life as soon as I install this hub, or is there anything else that needs to happen?

I’m just a little concerned because on various distributor sites the later variants don’t show compatibility with the 2017 C-Max.

:warning: Do not bump the thread in the future, use the edit button instead of posting consecutive messages.

I have merged your last messages.

Not having an H series and being on Sync3 2.2.x or higher will keep Car Play from working correctly.

Ignore the random parts sites, to an example the older Ford books for the 2016 Escape & Focus show the G series part number (now superseded to H) and then also show the H series as available with a note of not to be used for warranty work. (the 2016 was built to support Ford Apps so it wasn’t a defect which Ford gave up on for lack of developer interest, they embraced AA first as it was an easier integration with the OS of Sync3 which is QNX auto).