I have a client with a Windows 10. He’s trying to install my .CCX file but:
Double click, the mouse loads for a second and nothing happens.
Right click and open with → UnifiedExtensionManager, nothing happens.
Manual installation on paths:
C:\Program Files\Common Files\Adobe\UXP\Plugins\External
C:\Users\user\AppData\Roaming\Adobe\UXP\Plugins\External
Nothing loaded into Photoshop neither Creative Cloud. There’s no error message no feedback to the client or to use on how to solve this. I know how frustrating is for the client and it is more for us.
If someone have had this issue and solved, could you help me?
Try the AEScripts ZXP/UXP installer. I’ve had the most luck directing people at that. But on Windows, there is a trick to it. After they install the AEScripts tool, they need to open it and close it and then open it again before it will allow UXP plugins to install.
If they actually did the manual install, then this may not work, but they also might not have installed it correctly. Be sure to tell the user to take the CCX file out of the zip(if it is in one) and put it on their desktop first.
Works for me, but I had similar troubles with an external user where the file association for CCX was broken. Naively pointing the file association to “Open with” the CC exe did not help. Looking at my registry, it should go thru UPIA instead.
In a command window, cd to the UPIA dir, along
cd %CommonProgramFiles%\Adobe\Adobe Desktop Common\RemoteComponents\UPI\UnifiedPluginInstallerAgent
Of course some genius used space in the path, so you likely need to sort that out beyond copy-paste. We used individual cd per each directory level.
Then call the agent - better have the ccx in an easily reachable place.
The actual registry entry is different in that it uses /doubleClick instead of /install to take you thru CC.exe UI with its disclaimers. We attempted to fix that (for other CCX) but since the install already worked did not yet go deeper.
Thank you Erin! I’m having a client having this issue (Window defender thing) because the obfuscation of my UXP plugin. Because the strong obfuscation, windows is detecting the index.js as a trojan and blocking the plugin… I really don’t have time to rework the architecture of the plugin to find a workaround, is there away you guys can do something at your end asap? This is getting more a more into my support lately… People resist to use software because the complicated installation and problems like this, and for us as developers is a headache dealing with this kind of support very often and finding workarounds that will be broken with new Photoshop updates.