“Could not complete the Camera Raw Filter command because of a program error”

[BhargavKbmy]

i m facing issue in letest photoshop..
i try all the ways, like reinstallation, older version, but still not working 

any buddy knows solution ???
please Help me...
Bhargav

[subject renamed for clarity]

[Klaus5F8D]

Hello Sameer,

I also never touched label names.

Also - In preferences you cannot change a file's name ... only general behaviour, e.g. what the colours codes mean

or the explanations for shortcuts of ratings.

File names can only be changed at the file itself - colour or stars.

So - I don't know what you are talking about ...?

Also - for the topic in general - it seams to be highjcked ...?

The issue of my post was ONLY for editing alreadt existing PSDs or JPGs via Photoshop > Filter > Camera RAW Filter!!

NOT about opening RAW files from Bridge ... no problems there!

Thanks

[D Fosse]

@Klaus5F8D 

It most likely is the same problem - but it sounds like you're opening raw files hosted by Bridge, not hosted by Photoshop. This is a Photoshop issue, not a Bridge or ACR issue.

Hosting ACR in Bridge is actually a good workaround that I hadn't thought of. It won't work for the ACR filter, but it will for raw files.

I'm waiting for the ACR module to fail so I can test this, but when you need it to fail, it works as if nothing ever happened... 😉

In the meantime - can you still open raw files from Photoshop, or by double-clicking them in Windows Explorer? Can you open the Liquify filter in Photoshop, or Save For Web? They fail at the same time.

[Klaus5F8D]

Hi D Fosse,

thanks for your time.

I'll go through your comments:

Yes, I always import RAW files via Bridge, which converts them automatically into DNGs and gives them a separate folder under a choosen name. Works very well ... can't even even imagine how elso to import images from the camera.

When I want to edit them I open Bridge, click the DNG image and it opens in Camera RAW ... without Photoshop being bothered yet ... and I do an initial editing, then open in PS for further editing and finalizing as PSD.

All this works without a problem.

My problem only starts now ... and only in case I decide to want to take the PSD back into Camera RAW editor for certain features I find better than in PS. As mentioned before ... get the error message ... sometimes ... with every image ... sometimes only occasionally ... weird!

That for explaining my workflow.

Strangely, I just had a session where everything worked without errors, every image ... and I thought it's gone.

But started another session later and it was back ... every image ... excep, of course, no problems when restarting PS every time.

To your suggestons:

- can I open RAW file from explorer?

Yes, no problem. They either open in Windows Pictures (I set it that way) or ... right click and "open with" in PS ... and opens in Camera RAW. ... all as it supposed to be.

- Liquify works (with a PSD file, PS > filter> Liquify)

- Save for web (PS > export > safe for web(legacy) - NOT working! No reaction!?!

I hope this might gives you some new ideas

Thanks

[D Fosse]

There, it finally broke, took about an hour this time...

OK, try this. First keep working until the ACR filter stops responding. It can take a while after launching PS. Are you getting this error message?

Once you have that error - open a raw file (not jpeg or PSD) from Bridge by right-clicking and choosing a) Open and b) Open in Camera Raw. If it is indeed the same issue, the first should not work but the second should:

EDIT: Hang on. The plot thickens. Now it started spontaneously working again here! It has never done that before! Was it because I launched ACR through Bridge, thus maybe kickstarting it back? That's something I haven't done before. This is beginning to feel like chasing ghosts...

[Klaus5F8D]

Hi D Fosse,

I try and try ... so far every image works (meaning to open a PSD or JPG from PS into Filter > ARC) ... no pronlems .. no error.

However ... befor I get another error ... openeing a DNG from Bridge as you described, both "Open" AND "Open In RAW" ... both open in RAW ... as double clicking does as well. This is what it always did ... "Open / Open InCamera Raw / double click" all open Camera Raw

I'll post again once I get an error.

K

PS: just as an observation I never gave to much attention to:

DNGs from Bridge - 3 options: - "Open" - into ACR with PS running

                                                      - "Open With" - into PS (default) but... is the sane as above

                                                      - "Open In Canera Raw" - opens into ACR without PS running

JPGs from Bridge - 3 options: - "Open" and "Open With" ... both open in PS

                                                   - "Open With Camera Raw" opens in ACR

PSDs from Bridge - 2 options: - "Open" and "Open With" - both opn in PS

So, to reedit a PSD in ACR is only possible from PS > Filter

while a jpg can be opened inACR from Bridge and from PS > Filter

Interesting though is that for JPGs some features in ACR are not available from Filter but only from Bridge > Open in Camera Raw (e.g. Straighten tool)

[Klaus5F8D]

Hi D Fosse,

it finally failed again.

Yes, as you said: after having the error message, "Open" a dng from bridge = same error message

                                                                              "Open in Camera Raw" = no error, opens in ACR

But, again, the problem was never with dngs ... and ... double clicking the DNG always works fine.

Chosing "Open with ACR" with a JPG also always works.

Only with PSDs you don't have that choice. To edit a PSD in ACR again is only possible from PS > Filter ... where it fails (sometimes)

It seams that directly from Bridge to ACR always works (dngs and jpgs) but with opening PS first and then into ACR creates the problem (sometimes)

[D Fosse]

That's what I'm saying: ACR hosted by Bridge works. ACR hosted by Photoshop fails (when it fails).

ACR (Camera Raw) can't open or run by itself. It's a plugin that needs to run under a host application - Photoshop, Bridge or After Effects.

[Tele55]

That's what I meant ... open from Bridge, without Photoshop running.

Should have said it clearer.

To come back to the original issue and phenomenon that it sometimes gives the error

and other times works fine for hours ...?!? with the same images ...

[yang_kobe]

Oh！It works！It's useful！Thx so much！！The problem that has been bothering me for most of the year!

[Mikael32965992xqm2]

I may have found a workaround for this, but I'm not sure if it can be implemented. As the majority of posters here, my ACR stops working and displays the error message after some time of activity in PS. However, I've found that ACR still works when invoked via an action. That is, I can start recording an action, opening ACR, change some settings there, close ACR and stop recording the action. This action will play even when PS gets into the tiresome mode of not being able to open ACR from the menu or the keyboard shortcut. The problem is that I simply want to open ACR. I can't record the mere opening of ACR in an action. The button for stopping the recording of the action isn't active while ACR is open. I can stop the recording first after having closed ACR.

Does anyone know if this is possible? I.e. recording just the opening of ACR in an action.

I should add that it isn't possible to edit the action afterwards. The whole process of opening and closing ACR is shown as one step in the actions menu, and hence can't be edited.

[D Fosse]

Yes, I noted this in an earlier post:

In other words - ACR works, but it fails to bring up the UI. So an action works with predetermined parameters, but it won't open the UI to change or add any parameters.

[Mikael32965992xqm2]

Right Fosse. You've noticed the very same thing as I did. I somehow missed that. 

[dc289]

Still have this issue as well. I'd thought the latest updates had finally fixed it as I managed a couple of hours work and then it struck again. It's almost as if a very specific command or sequnece triggers the error in the program and after that point it stays. Now back in the same pattern, open a couple of raw files and error message returns. So still stuck using PS25.9 (which works fine all day long).

Surely somebody at Adobe can figure this one out, as for me it's very specific, the first run of acr always works on a restart every time and then breaks after a couple more runs/few minutes.

[D Fosse]

Yeah, that's exactly the behavior we all see.

I don't think there's any doubt that this qualifies as a bona fide bug. The problem is that it can't be reproduced on command; it's unpredictable when it kicks in.

[scottbu]

I NEVER have CC Desktop set to auto update.  But it did for ACR 17.4.1 anyway.  When I checked CC  Desktop, auto update was on.

Ok, except I when trying to open a file in PS from ACR, I kept getting "Could not save because of a program error."  I tried all of the suggestions from "Learn how to fix" short of reinstalling, but nothing worked.  This was especially a pain because every time I got into ACR after one of these errors, it acted as if I had never installed ACR before.  All the panels were rearranged, my saved workspace was gone, my presets were there but no longer favorites... I had to reset everything several times.

So I went to CC Desktop to down rev ACR.  That option no longer appeared.  But I noticed that even though PS was open and running on my computer, CC didn't think I had PS installed.  Ok - no other choice, I clicked on install PS.  It immediately said there was conflict because PS was already running.  So I closed it and the install of 26.8.1 proceeded.

Big mistake.   This install has wiped everything I had set up in PS.  My workspace - gone.  All my actions - gone.  Tool bar tools and groupings - gone.  It remembered a few things, like how much memory to use (70% of 64GB), but it forgot what scratch drives to use.  Just a few of MANY problems.

I cannot begin to explain what a monumental disaster this is.  It will take me DAYS to get PS back to something usable.  I simply cannot understand how Adobe could allow software so clearly not stable to be released.  I have been VP of Engineering in multiple small software companies.  If we had this level of quality assurance on our products, we would have gone out of business - and quickly.

If anyone has suggestions on how to recover my settings, and especially my actions, I would sincerely appreciate your help.

[scottbu]

Update... 

First, a correction: the error message I was getting is "Could not open (filename) because of a program error."

It's a PS error, not an ACR error.  Closing PS and opening it again sometimes fixes the problem.  But it still hapens with 26.8.1.

Probably related: many times per day (before and now after the aformentioned disaster), when I save and close a file in PS, I can't bring Bridge forward.  It's there and running, but clicking on the Bridge tab (Windows) does nothing.  I have to minimize PS to get Bridge to be visible.  When that happens, the next time I open a file in PS from ACR, PS is no longer maximized - it's windowed.  My suspicion is that PS is crashing because when this happens, a psautorecover file appears in that folder.

Just more foolishness to slow me down.

[scottbu]

 Another update:  Using the latest ACR and PS, whenever I get the "Could not open (filename) because of a program error" in PS, the next time I open ACR by double-clicking a file in Bridge, ACR reverts to the fresh install AGAIN.

Someone, PLEASE HELP.

[kglad]

@scottbu 

if you're still having an acr problem, start your own thread in the acr forum.

[Tele55]

This is for scottbu,

you are having a major disaster going and I feel for you.

I don't have answers to all your problems but maybe some:

- I have the same problem with opening images in ACR, sometimes!! / not every time!!. But all images always open in ACR when opening from Bridge. 

- Your PS Workspaces, Actions, etc, etc are all in C>Users(You)>Application Data (not visible until you change under View>Show>Show Hidden Items). All in Roamind>PS>Presets and Settings. I back those always up just in case.

- ACR are under CameraRaw>Settings, I think.

I guess you just retype e.g. the workspace name again under Window>New Workspace and it should refetch from AppData.

Actions are retreavable from the Actions window where all saved actions.action groups are listed (under the three bars)

- I have no answer why ACR looses all settings, neither to PS misbehaving.

I pretty much gave up on further investigating or asking for help regarding the Error>"Could Not Open ...". It only happens sometimes (some images) and ONLY when attempting to open from PS > Filter. From Bridge always works.

I hope you stay sane resetting everything. Good Luck!

Cheers

[D Fosse]

@kglad 

Actually, this is the right place for the post. This is a Photoshop bug, not an ACR bug (except for some additional unrelated issues brought up by @scottbu which should be posted separately).

This is a very long thread, merged from many separate threads, so it's unfortunately quite incoherent and difficult to follow chronologically. But anyone taking the trouble to read through all of it, will find that the problem is very well defined and precisely described in the above.

Alas, still unresolved. The workaround is to launch ACR hosted by Bridge, which is unaffected by this bug. This will kickstart ACR hosted by Photoshop back into correct operation - including the ACR filter. Or relaunch Photoshop.

[Tele55]

D Fosse, You are absolutely right ... if I can say so, being not as knowledgeable as you.

Yes, the problem only occurs when trying to open fron PS > Filter.

ACR is absolutely working fine. 

Bridge always opens in ACR just fine ... regardless if RAW image or anything else.

It must be a PS issue ... and no solution yet.

Yes - scottbu's problems are largely something else (loosing presets, workspaces, actions,, etc)

Yes - this thread is so large ... without solution ... I'll opt out.

It s really not a major distraction since I work from Bridge mostly.

Cheers

[stevevonb]

ARC stopped working for me in both Photoshop and Bridge.  I have updated the latest Nvidia drivers.  The type of file I'm working with does not matter, neither does file size.