Get message Cannot complete command because the extension could not be loaded.

When clicking in CS5 Photoshop menu - "Essentials", "New is CS5 "or "CS LIve", I get a message "Cannot complete command because the extension could not be loaded". I get the same message when attempting to acces frm Window>Extensions> then clicking on one of the listed exteneions.  This is been going on for some time for no apparent reason.  Using version 12.0.4 (x32) iMac OS 10.6.8 - Intel Quad Core.

I unstalled Photoshop.  Then I installed on another drive.  External.  It did the same thing!!!!  No mini-bridge, or any extentions loading.  I don't know what is wrong.
I read something somewhere about a Panels file in photoshop.  So I'm looking there.

Similar Messages

  • "Cannot complete command because the extension could not be loaded." with CEP5 Sample

    Hi,
    I have trouble with porting my extension to CEP5. I am getting error "Cannot complete command because the extension could not be loaded." when I open the panel.
    Is there any way to get more info about what happened and why? My extension was properly signed zxp and Extension Managed installed it without trouble.
    Also, to debug the problem, I tried to open the CEP HTML Test Extension - https://github.com/Adobe-CEP/Samples/tree/master/CEP_HTML_Test_Extension_5.0
    I have copied it to "~/Library/Application Support/Adobe/CEP/extensions/com.adobe.CEPHTMLTEST", created .debug file in it (https://gist.github.com/m6k/39a49786b7a85a9e312b), created empty .debug file inside Photoshop CC 2014.app (to suppress signature checking). When I open Photoshop CC 2014, I see test panels listed in extension menu, but when I try to open them, I also get the "Cannot complete command because the extension could not be loaded." error.
    Any hints what i am doing wrong and what can I do to debug this problem?
    Jan

    Hallgrimur, thanks, that is exactly the article I needed!
    My problem was that I forgot about the pref file  "~/Library/Preferences/com.adobe.CSXS.5.plist".

  • "Cannot complete command because the extension could not be loaded" ?

    I have installed a photoshop plugin into photoshop cc. However when I go to windows => extension => photoshop plugin, it shows me "Cannot complete command because the extension could not be loaded". What should I do ?
    Thanks.

    I think you posted on the »wrong« Forum. (edited)
    http://forums.adobe.com/community/labs/extensionbuilder3?view=discussions

  • Extension is not loaded. Cannot complete command because the extension could not be loaded.

    Despite display and hook into the extension manager CC Erweireung in PS is displayed to, but is not loaded.
    Advance: Even reboot didn't help.

    I unstalled Photoshop.  Then I installed on another drive.  External.  It did the same thing!!!!  No mini-bridge, or any extentions loading.  I don't know what is wrong.
    I read something somewhere about a Panels file in photoshop.  So I'm looking there.

  • In Photoshop CS 6 (64 & 32), I get the error "cannot complete command because the extension could not be loaded".  I can click to pass this, but none of my extensions will run.  If I click on "browse in Bridge" I get "Could not complete the command Browse

    Further info is that I have a current update of the JavaScript as of now, my Adobe software is all updated, as is my Windows 7 software.  Everything was running fine until yesterday, and the only changes to my system were the Tuesday Windows updates. Can anyone help me resolve this problem?

    I unstalled Photoshop.  Then I installed on another drive.  External.  It did the same thing!!!!  No mini-bridge, or any extentions loading.  I don't know what is wrong.
    I read something somewhere about a Panels file in photoshop.  So I'm looking there.

  • Could not complete the command because the extension could not be loaded

    I was working in 3D with PS CS5 Extended. I went to the Window drop down menu and selected Color. I got the message "Could not complete the command because the extension could not be loaded" and the color pallet and swatches would not appear. I had to click on OK the error message three times to get rid of it as it kept reappearing. The the mini bridge and Brush pallets opened, including Brush Presets tab and Clone Source tab instead of the color pallets. How can I get my color pallets back?
    I am on an iMac Intel core i3 running OS X Lion 10.7.2
    Thanks for any help.
    Thanks,
    Don

    I unstalled Photoshop.  Then I installed on another drive.  External.  It did the same thing!!!!  No mini-bridge, or any extentions loading.  I don't know what is wrong.
    I read something somewhere about a Panels file in photoshop.  So I'm looking there.

  • Could not complete the video frames to layers command because the file could not be opened

    I recently learned to make gif images using KMPlayer and my Photoshop CS6, but today I hit a snag that I can't seem to get around. Normally I capture a scene from a show DVD I have in KMPlayer and then import the video frames into layers/frames in photoshop with no problem. Well today I went to do that, and captured the scene with what seemed like no problem (the small captured scene saved with no problem) but when I went to CS6 to import the video into layers, I got the error message "Could not complete the video frames to layers command because the file could not be opened". At first I thought it was the KMPlayer saving the files wrong, so I retried and got the same error message. Irestored the players settings back to a default and the file still wouldn't open in photoshop, and then I even tried uninstalling/reinstalling the player trying to get it to work, and then I thought it must be photoshop, because even scenes I had captured at an earlier day that worked perfectly fine when importing would not open.
    What could possibly be causing this problem to occur. Should I uninstall/reinstall photoshop and see if that works, or am I doing something wrong?
    The files I'm trying to import are AVIs as always, I even tried to capture scenes in other formats to no avail. What could be causing the problem?

    I uninstalled an reinstalled photoshop totally and it didn't fix the problem either. I made a post on the KMPlayer's forum hoping for an answer but I haven't recieved one yet. I'm starting to think it's the kmplayer having a problem capturing, since I've started getting the error "could not import the file to layers because the file has no layers" sometimes in photoshop, but I'm still trying to work around in photoshop to see if the problem came from there.

  • I receive the message: "The extension could not be loaded because it was not properly signed."

    When I try to open the Library in Photoshop, I receive the message: "The extension could not be loaded because it was not properly signed." It worked last week, but now I get this message and the Library is completely empty in Illustrator. My Library has stuff in it and I can see it on my iPad Apps.

    I am working on a PC, using Photoshop CC 2014
    Operating System:
    Error Message:
    Settings in Photoshop > Preference > Performance:
    Type of file you were working on: No file; just opened up Photoshop to begin working
    This is the first time this has happened - I have not doe any other troubleshooting.
    Camera Raw does not apply here.
    Thanks.

  • Could not complete the export command because the file could not be found

    When I try to save for web, Photoshop pops up a dialog box that says "could not complete the export command because the file could not be found".
    What is the solution for this?

    Please provide more information (Photoshop version, OS, target volume, …).
    Does the file’s or one of the folders’ name contain problematic letters (slash etc.)?
    Boilerplate-text:
    Are Photoshop and OS fully updated and have you performed the usual trouble-shooting routines (trashing prefs by keeping command-alt-shift/ctrl-alt-shift pressed while starting Photoshop after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved and making a note of the Preferences you’ve changed, 3rd party plug-ins deactivation, system maintenance, cleaning caches, font validation, etc.)?

  • PS show The extension could not be loaded because it was not properly signed

    When I'm open Libraries in photoshop cs2014 it's show
    The extension could not be loaded because it was not properly signed
    I'm try to reinstalled but it still error.
    How can i'm fixed this

    This is an open forum, not Adobe support... you need Adobe staff support to help
    Adobe contact information - http://helpx.adobe.com/contact.html
    -Select your product and what you need help with
    -Click on the blue box "Still need help? Contact us"

  • 0x80230729 (The extension could not be loaded.)

    Hi,
    I've been working on this most of the day without any luck. I'm wondering if anyone has seen something like this.
    PCNS can successfully deliver the password change to an AD target, so PCNS should be OK.
    The failure occurs when we add the Oracle EBS Web Service management agent to the password sync targets.
    The error message indicates that the Microsoft.IdentityManagement.WebService.MA.dll cannot be loaded due to an incorrect .NET framework version.
    An unexpected error has occurred during a password set operation.
     "BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\core\passwordext.cpp(322): 0x80230729 (The extension could not be loaded.)
    ERR_: MMS(5080): d:\bt\9394412\private\source\miis\ma\core\passwordext.cpp(804): Please verify that the password extension dll can be located in the Extensions directory.
    If the extension is present, confirm that the version of the .NET framework that can run the extension is installed on the server and that a supportedRuntimes entry in the configuration files specifies that version. The synchronization engine will not be able
    to load an extension that is built with a newer version  of the .NET framework than the version of the .NET runtime it is hosting.BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\core\passwordext.cpp(806): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\extensible\export.cpp(2821): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\extensible\export.cpp(2866): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\server\server\exportpassword.cpp(474): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\server\server\ma.cpp(7961): 0x80230729 (The extension could not be loaded.)
    BAIL: MMS(5080): d:\bt\9394412\private\source\miis\server\server\ma.cpp(8410): 0x80230729 (The extension could not be loaded.)
    Forefront Identity Manager 4.1.2273.0"
    I ran an Environment.Version command and it returns that we are using 4.0.30319.296.
    In the dllhost.exe.config file, we have the settings:
    <?xml version="1.0" encoding="UTF-16"?>
    <configuration>
    <configSections>
    <section name="resourceManagementClient" type="Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClientSection, Microsoft.ResourceManagement"/>
    </configSections>
    <!--
    .NET Runtime startup configuration: If you use a .NET 4.0 runtime, the useLegacyV2RuntimeActivationPolicy attribute is required and must be set to "true".
     When multiple versions of the runtime are listed, the first supportedRuntime element should specify the most preferred version of the runtime,
    and the last element should specify the least preferred version.
    Currently, the Synchronization Service supports the following runtime choices: v2.0.50727 and v4.0.30319. If selected, the version must be found in the \Windows\Microsoft.NET\Framework or \Windows\Microsoft.NET\Framework64 directories.
    -->
    <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0.30319"></supportedRuntime>
    <supportedRuntime version="v2.0.50727"></supportedRuntime>
    </startup>
    <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
    <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.1.0" />
    <bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.1.0" />
    </dependentAssembly>
    </assemblyBinding>
    </runtime>
    </configuration>
    So, I think it looks like it should be trying to run the dll under the 4.0.30319 framework. The documentation says that framework is required and we are running it.
    The dll is in the Extensions folder.
    Has anyone seen this before or something like it? Any ideas on where else I could check?
    Thanks,
    Sami

    Thank you for your reply. I've tried running in and out of proc with the same error showing up.
    I tried a few different modifications to the miiserver.exe.config (as well as Mmsscrpt.exe.config and the Dllhost.exe.config files). I tried changing 4.0.30319 to 4.0 as per this article:
    http://msdn.microsoft.com/en-us/library/w4atty68.aspx
    Even though we are only on FIM R2 (not on SP1), I tried a variation on the config file changes recommended here:
    http://support.microsoft.com/kb/2772429 but I referenced the newVersion as 4.0.1.0.
    Still no luck.
    Here's the miiserver.exe.config file. Maybe you'll see something glaringly wrong? Thank you for your help!
    <?xml version="1.0" encoding="UTF-16"?>
    <configuration>
      <configSections>
        <section name="resourceManagementClient" type="Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClientSection, Microsoft.ResourceManagement"/>
        <section name="resourceManagementService" type="Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection, Microsoft.ResourceManagement.Service"/>
        <section name="resourceSynchronizationClient" type="MIIS.ManagementAgent.ResourceSynchronizationClientSection, mmsmafim"/>   
      </configSections>
      <!--
        .NET Runtime startup configuration: If you use a .NET 4.0 runtime, the useLegacyV2RuntimeActivationPolicy attribute is required and must be set to "true".
        When multiple versions of the runtime are listed, the first supportedRuntime element should specify the most preferred version of the runtime,
        and the last element should specify the least preferred version.
        Currently, the Synchronization Service supports the following runtime choices: v2.0.50727 and v4.0.30319. If selected, the version must be found in the \Windows\Microsoft.NET\Framework or \Windows\Microsoft.NET\Framework64 directories.
       -->
      <startup useLegacyV2RuntimeActivationPolicy="true">
        <supportedRuntime version="v4.0.30319"></supportedRuntime>
        <supportedRuntime version="v2.0.50727"></supportedRuntime>
      </startup>
      <!--
      <resourceManagementService/>
            Additional properties that can be specified for the <resourceManagementService /> configuration section
            PropertyName                                   
    DefaultValue                                Description
            dataReadTimeoutInSeconds                        58                                         
    Database timeout for read operations
    Range: 0-max(int16)
            dataWriteTimeoutInSeconds                       58                                         
    Database timeout for write operations
    Range: 0-max(int16)
            synchronizationDataReadTimeoutInSeconds         1200                                       
    Synchronization operations (FIM MA import / export)
    that read from the FIM Service are tied to this timeout
    to allow these operations extra time to complete if there
    are a large number of objects / values in a batch.                                                                                                   
    Range: 0-max(int16)
            Note: The following registry key : ReadTimeOut , in the registry path : HKLM\SOFTWARE\Microsoft\Forefront Identity Manager\2010\Synchronization Service ,
            overrides the synchronizationDataReadTimeoutInSeconds property.
            synchronizationDataWriteTimeoutInSeconds        1200                                       
    Synchronization operations (FIM MA import / export)
    that write to the FIM Service are tied to this timeout
    to allow these operations extra time to complete if there
    are a large number of objects / values in a batch.                                                                                                   
    Range: 0-max(int16)       
            externalHostName                                Defined by
    Administrator during set-up      This value is used by FIM to define the external host name
    that should be used by clients to connect to FIM when you deploy
    a Load Balanced configuration.       
        -->
      <resourceSynchronizationClient/>
      <!--
            Additional properties that can be specified for the <resourceSynchronizationClient /> configuration section. This configuration is used to configure the FIM MA
            settings.
            PropertyName                                   
    DefaultValue                                Description
            asynchronous                                   
    true                                        This property controls
    whether FIM MA uses the older synchronous channel
    or the new asynchronous channel when communicating with FIM Service.
            aggregate                                      
    true                                        This property controls
    whether FIM MA can send data to FIM Service in batches.
            aggregationThreshold                            1000                                       
    This property controls the number of attributes per aggregated batch.
            delayUpdateAcknowledgements                     false                                      
    This property controls whether the FIM Management Agent sends acknowledgements to
    FIM Synchronization Service immediately upon Request completion, or withholds them
    until the end for Update operations. Setting this to true may reduce the overall time
    to export data, but the FIM Synchronization Service UI statistics are not updated as frequently.
            exportRequestsInProcessMaximum                  50                                         
    This property controls the maximum number of export requests that
    can be in process.              
        -->
        <system.diagnostics>     
            <sources>
                <source name="ForefrontIdentityManager.ManagementAgent" switchValue="Warning">
                    <listeners>
                        <add initializeData="ForefrontIdentityManager.ManagementAgent" type="System.Diagnostics.EventLogTraceListener, System, Version=2.0.0.0, Culture=neutral,
    PublicKeyToken=b77a5c561934e089"
                             name="MAExceptionEventLogListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, Callstack">
                        <filter type="" />
                        </add>
                    </listeners>
                </source>
                <source name="ForefrontIdentityManager.ManagementAgent.EventTracingForWindowsTraceSource" switchValue="Verbose">
                    <listeners>
                        <add name="MAEventTracingForWindowsListener"
                             type="System.Diagnostics.Eventing.EventProviderTraceListener, System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                             initializeData="{C4D0C1D4-909D-481b-B011-10E682A6009C}" />
                    </listeners>
                </source>
            </sources>
        </system.diagnostics>
        <!-- Instructions for collecting ETW Traces
             To collect ETW traces for Microsoft.ResourceManagement.Service. Run the following commands in the specified order from
             an elevated command prompt.
                1. To start a new etw trace session    : logman start mysession -p {C4D0C1D4-909D-481b-B011-10E682A6009C} -o FIMMAETWtrace.etl -ets
                2. To stop a running etw trace session : logman stop mysession -ets
                To format the collected traces run any of the following commands (from an elevated command prompt) depending
                on the required output format.
                1. tracerpt FIMMAETWtrace.etl -o FIMMAEventTrace.xml -of XML -lr -summary FIMMAEventTraceSum.txt -report FIMMAEventTraceRpt.xml
                2. tracerpt FIMMAETWtrace.etl -o FIMMAEventTrace.evtx -of EVTX -lr -summary FIMMAEventTraceSum.txt -report FIMMAEventTraceRpt.xml
                3. tracerpt FIMMAETWtrace.etl -o FIMMAEventTrace.csv -of CSV -summary FIMMAEventTraceSum.txt -report FIMMAEventTraceRpt.xml  
      -->
        <!--
           Full Diagnostics configuration.
           Uncomment the following section and replace the default <system.diagnostics> configuration to
           enable all trace sources and obtain all available traces for Microsoft.ResourceManagement.Service
      -->
        <!--
        <system.diagnostics>     
            <sources>      
                <source name="System.ServiceModel" switchValue="Verbose"
                  propagateActivity="true">
                    <listeners>                  
                        <add name="ServiceModelTraceListener">
                            <filter type="" />
                        </add>
                    </listeners>
                </source>
                <source name="ForefrontIdentityManager.ManagementAgent" switchValue="Verbose">
                    <listeners>
                        <add initializeData="ForefrontIdentityManager.ManagementAgent" type="System.Diagnostics.EventLogTraceListener, System, Version=2.0.0.0, Culture=neutral,
    PublicKeyToken=b77a5c561934e089"
                             name="ExceptionEventLogListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, Callstack">
                        <filter type="" />
                        </add>
                        <add name="ServiceModelTraceListener">
                            <filter type="" />
                        </add>
                    </listeners>
                </source>
                <source name="ForefrontIdentityManager.ManagementAgent.EventTracingForWindowsTraceSource" switchValue="Verbose">
                    <listeners>
                        <add name="EventTracingForWindowsListener"
                             type="System.Diagnostics.Eventing.EventProviderTraceListener, System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                             initializeData="{C4D0C1D4-909D-481b-B011-10E682A6009C}" />
                    </listeners>
                </source>
            </sources>      
            <sharedListeners>
                <add initializeData="ForefrontIdentityManager.ManagementAgent_tracelog.svclog"
                  type="System.Diagnostics.XmlWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                  name="ServiceModelTraceListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack">
                    <filter type="" />
                </add>
            </sharedListeners>
            <trace autoflush="true" />
        </system.diagnostics>
        -->
      <!--
        .NET Runtime startup configuration: If you use a .NET 4.0 runtime, the useLegacyV2RuntimeActivationPolicy attribute is required and must be set to "true".
        When multiple versions of the runtime are listed, the first supportedRuntime element should specify the most preferred version of the runtime,
        and the last element should specify the least preferred version.
        Currently, the Synchronization Service supports the following runtime choices: v2.0.50727 and v4.0.30319. If selected, the version must be found in the \Windows\Microsoft.NET\Framework or \Windows\Microsoft.NET\Framework64 directories.
       -->
      <startup useLegacyV2RuntimeActivationPolicy="true">
        <supportedRuntime version="v4.0.30319"></supportedRuntime>
        <supportedRuntime version="v2.0.50727"></supportedRuntime>
      </startup>
      <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
            <bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.1.0" />
            <bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.1.0" />
          </dependentAssembly>
        </assemblyBinding>
      </runtime>
    </configuration>

  • The extension could not be loaded  because it was not properly signed

    when I start PS cc 2014 I meet this problem.
    what should i do to resolve this problem?

    What's the extension name? Please remove and reinstall it as it has likely been updated.

  • When opening Photoshop I receive "Cannot Complete Command because extension cannot be found"

    I have downloaded the Trial for CC and when I open Photoshop I receive "Cannot Complete Command because extension cannot be found". Please advise on how to fix it.

    Moving this discussion to the Photoshop General Discussion forum.

  • HT1386 I am trying to download ios 5.1.1 on my iphone from itunes and i get an error message that my iphone cannot be updated because the filmware is not compatible?  What do I do?

    I am trying to download ios 5.1.1 on my iphone from itunes and i get an error message that my iphone cannot be updated because the filmware is not compatible?  What do I do?

    iOS 5 is only compatible with the iPhone 3Gs and later...
    Updating to iOS 5   http://support.apple.com/kb/HT4972

  • How do I resolve: "Could not complete the Crop command because the file is not compatible with this version of Photoshop" error message?

    Photoshop document created in current version of PSCC2014, now will not crop, resize, etc without throwing compatibility error.
    "Could not complete the Crop command because the file is not compatible with this version of Photoshop."
    How do I resolve without recreating the file?

    Ooops.  Hit save reply prematurely. 
    You may be able to open the flattened composite or the embedded JPEG preview of your file in Adobe Illustrator, GraphicConverter (Mac only) or some such application, but your layers will be gone.
    The problem of working across a network is that it's not supported by Adobe:
    This is the boilerplate text often used in connection to saving to a network (please NOTE the part where it explains that normally, it does work, but that it is impossible to troubleshoot someone else's network remotely, and that's why it's not supported by Adobe):
    If you are opening files over a network or saving them to a network server, please cease and desist immediately in the event you are currently experiencing problems with one or more files. Working across a network is not supported.
    See: 
    http://kb2.adobe.com/cps/406/kb406793.html
      Copy the CLOSED file from your server to your local hard disk, work on it, save it again to your local hard disk, close it, and copy the closed file back to the server.
         Of course, the fact that Adobe does not support working across a network does not necessarily mean it won't work.   It should.
        Adobe's position is that there are too many variables in a network environment for them to guarantee that everything will work correctly in every network, especially given the fact that if something does not work properly, it's probably the network's fault, and Adobe has no way of troubleshooting your network.
      If you can't work locally, you are on your own, and if something happens, you're on your own. If you must work from a server, make sure your network administrator is a competent professional.
    When problems arise, a lot of valuable work can be lost.

Maybe you are looking for