# macOS High Sierra = Carbon Component Manager deprecation
**URL:** https://forum.juce.com/t/macos-high-sierra-carbon-component-manager-deprecation/24293
**Category:** General JUCE discussion
**Created:** [September 20, 2017, 11:32pm UTC](https://forum.juce.com/t/macos-high-sierra-carbon-component-manager-deprecation/24293 "2017-09-20T23:32:51Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@tadnicol](https://forum.juce.com/u/tadnicol)
#### Post date: [September 20, 2017, 11:32pm UTC](https://forum.juce.com/t/macos-high-sierra-carbon-component-manager-deprecation/24293/1 "2017-09-20T23:32:51Z")
Just wanted to clarify. The deprecation of the Carbon Component Manager won’t affect JUCE plugins that have JUCE\_SUPPORT\_CARBON disabled, correct?
ie I won’t have to rebuild old plugins that never had that enabled in the first place?
In the IPLUG community they are discussing it here: [AudioUnits & High Sierra - Cockos Incorporated Forums](https://forums.cockos.com/showthread.php?p=1884702)
---
### Author:  [@olilarkin](https://forum.juce.com/u/olilarkin)
#### Post date: [September 21, 2017, 7:55am UTC](https://forum.juce.com/t/macos-high-sierra-carbon-component-manager-deprecation/24293/2 "2017-09-21T07:55:21Z")
juce has supported audiocomponent entry point for a long time. I’ve noticed some odd behaviour with au validation & apple products on 10.13 to do with this though, so it might be worth checking.
---
### Author:  [@tadnicol](https://forum.juce.com/u/tadnicol)
#### Post date: [September 21, 2017, 7:02pm UTC](https://forum.juce.com/t/macos-high-sierra-carbon-component-manager-deprecation/24293/3 "2017-09-21T19:02:05Z")
Thanks Oli, when I update my aux machine to 10.13 in a few days I’m going to test all our current builds. Will report back here.
---
### Author:  [@tadnicol](https://forum.juce.com/u/tadnicol)
#### Post date: [September 26, 2017, 10:25pm UTC](https://forum.juce.com/t/macos-high-sierra-carbon-component-manager-deprecation/24293/4 "2017-09-26T22:25:42Z")
I tested all our JUCE plugins after doing an update install (without erasing my drive) and a clean install (first erasing my drive). Both work fine, however I may have ran into some macOS bugs when doing the clean install. Skype and Reaper wouldn’t install, but after I restarted (where there was a really weird turquoise screen before it restarted) those programs installed fine. Could have an effect on AU plugins showing up too perhaps, as shown in that Reaper forum thread.
---
### Author:  [@ttg](https://forum.juce.com/u/ttg)
#### Post date: [September 27, 2017, 7:06am UTC](https://forum.juce.com/t/macos-high-sierra-carbon-component-manager-deprecation/24293/5 "2017-09-27T07:06:14Z")
As I’ve also replied on thread @cockos.
We have yet to see regression in support of some API (mind the yet 😉 )
One product is actually hosting AUs (using in-house code not JUCE) to allow 32-bit wrapped to 64-bit using IPC.
So far even very old plug-ins show-up and works from my tests under Logic X.
The only quirk was with plug-ins (also new ones compliant to latest standards) not showing or scanning until I restart my machine.
Even clearing caches simply made auval+LogicX scan the plug-ins that were already showing up and still ignoring the ones I’ve just installed.