Adobe CC Users: Palette Extension could not be loaded because it was not properly signed
Hi all,
Over the last 12 hours, we've received reports from many of you that you're seeing the following message when opening an Adobe CC app: "Palette Extension could not be loaded because it was not properly signed".
Following this error, the Palette integration does not work. This affects each of the following apps to some degree:
- Photoshop
- Premiere Pro
- After Effects
- Illustrator
- InDesign
- Audition
First and foremost, I would like to apologize on behalf of our entire team that this error has occurred. Unfortunately, there was a timing implication surrounding our Adobe Signing Certificate.
Our development team has isolated the issue and created 2 solutions, each of which are available below...
macOS: Recommended Fix
1. Quit all instances of PaletteApp and your Adobe CC apps first (this is important)
2. Go to Finder and press Shift+Cmd+G, or select Go > Go to Folder in the Menu Bar
3. Paste in the following path, then delete any folder titled “Palette Beta” or “Palette 2" contained inside:
~/Applications/
4. Repeat Step 2 with the following file path:
/Applications/
5. Download, unzip, and run this installer: PaletteApp 2.6.502 for macOS
6. PaletteApp will automatically re-open following installation. Select an Adobe profile and you'll be prompted to reinstall the Adobe CC Extension (requires an admin password)
7. Optional but recommended: Reboot your computer, and re-open PaletteApp immediately after startup
8. Open your Adobe CC apps
macOS: Alternative Fix
1. Quit all instances of PaletteApp and your Adobe CC apps first (this is important)
2. Open Terminal: Press Cmd+Spacebar to open Spotlight Search, then search "Terminal"
3. In terminal, type/paste in:
defaults write com.adobe.CSXS.9 PlayerDebugMode 1
4. Press the Enter/Return key
5. In terminal, type/paste in:
killall cfprefsd
6. Press the Enter/Return key
7. Restart PaletteApp
8. Restart your Adobe CC apps
Please Note: We recommend this fix as a last resort when re-installing PaletteApp with the version above is not possible or advisable. Making these changes to the Adobe CC preferences allows your system to run unsigned extensions, which is a potential security risk.
Windows: Recommended Fix
1. Quit all instances of PaletteApp and your Adobe CC apps first (this is important)
2. Go to File Explorer and select the filepath bar at the top of the window
3. Paste in the following path, then delete any folder titled “Palette Beta” or “Palette 2" contained inside:
%PROGRAMFILES(X86)%
4. Repeat Step 2 with the following file path:
%PROGRAMFILES%
5. Download and run this installer: PaletteApp 2.6.502 for Windows
6. PaletteApp will automatically re-open following installation. Select an Adobe profile and you'll be prompted to reinstall the Adobe CC Extension (requires an admin password)
7. Optional but recommended: Reboot your computer, and re-open PaletteApp immediately after startup
8. Open your Adobe CC apps
Windows: Alternative Fix
1. Open Registry Editor: Press Win+R or select the Windows search bar, then search "regedit.exe"
2. In Registry Editor, select the registry path bar (at the top) and type/paste in the following path:
Computer\HKEY_CURRENT_USER\Software\Adobe\CSXS.9
3. Right-click and select New > String Value
4. Type/paste in the following name:
PlayerDebugMode
5. Double-click on the string and set the following value: 1
6. Restart PaletteApp
7. Restart your Adobe CC apps
Please Note: We recommend this fix as a last resort when re-installing PaletteApp with the version above is not possible or advisable. Making these changes to the Adobe CC registry allows your system to run unsigned extensions, which is a potential security risk.
--
Again, on behalf of the entire team, please accept our apologies for any frustration and disruption you've experienced as a result. I hope the above instructions help you to get back up and running ASAP. As always, please reach out directly to us via support@monogramcc.com should you need further help.
-
Daryl, this is definitely possible! The exact behaviour may change depending on the version of Photoshop you're using, and also any PS settings that pertain to extension security/signing.
There will be a forthcoming patch update for PaletteApp (either 2.6.5 or 2.6.6) that has this fix and you'll be prompted to update then, but we wanted to get an immediate fix out ASAP for anyone affected to the point they can't properly use Palette.
-
Hello
Good Day
Thanks for your opinion. in reference https://palette.zendesk.com/hc/en-us/community/posts/360060965352#comment-overview
but still, I'm facing with same problems. I have been tried both options.
Thanks again
Please sign in to leave a comment.
Comments
9 comments