P: Program error with actions that have save command in 24.3

Same issue.  A BIG problem for me when batch processing...

Is the »Save« part of the Action itself or »Save and Close«?

Does setting a Destination Folder make a difference? 

the latest version of Light Room Classic also has disk permission issues, even though I've given it full disk access. 

Same issue.  A BIG problem for me when batch processing...

The current version of Photoshop (24.3) is so buggy that I've had to revert to the previous version. The primary issue is files constantly failing to save, with a 'program error' message. When using (Custom) Actions that include saving as part of the Action, the same issue arises, making the chosen Action fail. Full Disk Access has been granted and other 'workarounds' don't make any difference.

I updated PS last night and since then I've had issues with running certain actions. One in particuar I use often and everytime it gets to the 'select subject' part of the action the error message 

"Could not complete the command because of a program error" comes up. I've uninstalled the newest version and went back to an old one and it's still doing the same thing. Any advice?

Replacing "save" then "close" with "close with save" worked great and got me out of a jam here! Many thanks to those who suggested!

This should be fixed by now. Serious slow down in my workflow.

• Revert to the previous version using the Creative Cloud app
• Turn off automatic updates for applications in preferences for the Creative Cloud app

Thanks for the advice, but I think you may have missed a couple of points in my post.

• The reason that I upgraded is that Bridge would not do a photo merge unless I "Upgrade to the latest version of Photoshop".

Now, a couple of fun additional facts here. First, I was using Bridge 2022 when I got that message. Why? Because in Bridge 2023, Adobe stuffed the Slideshow mode by removing the (already limited) ability to display metadata under the image. I therefore continued to use Bridge 2022 to keep what functionality Bridge had in that regard. So what happened after I upgraded PS to the latest version?

I still got the same message.

Figuring that Bridge 2022 was simply too stupid to know that the latest version of PS WAS now installed, I opened Bridge 2023 and tried the PhotoMerge from there instead. It... ran. Sort of. Though for some reason the Latest! And! Greatest! version of Photoshop seems to think that a "photomerge" of 4 horizontal images is best done by joining two of them together and putting them at the top of the canvas and then joining the other two together and putting them at the bottom of the canvas with a huge, empty space between the two.

So clearly Adobe has made yet ANOTHER "improvement", but that's a separate conversation.

I don't need to keep using Bridge 2022 since I now do most metadata management through the vastly superior ACDSee Ultimate, so the error message is no longer relevant.

Second point:

• Yeah, bit I don't HAVE automatic updates on. I intentionally do not have automatic updates turned on. As I said in my post, I manually triggered the update for one reason and one reason alone, that I thought it was the only way to get Bridge to launch a PhotoMerge in Photoshop. As it turned out (a) that was a Bridge issue, specifically a Bridge 2022 issue and (b) it looks like PhotoMerge has been "improved" to the point of complete uselessness.

If Adobe screw up, and here they screwed up not for the first time in trashing Actions, they need to issue a fix. Not someday, not next time they get around to it, but rather As Soon As They Have One. The very day.

@jane-e As an exception(TMI), even if you turn off automatic updates, sometimes the settings are ignored and updated. Therefore, need to always check and back up settings folder by date.
About 2019 auto update bug in creative cloud?It's been there since then. I wanted to let you know that turning off automatic updates is not the absolute answer.

@Mal Reynolds 

"I didn't even WANT this update"

Hi Mal,

You might want to do two things:

• Revert to the previous version using the Creative Cloud app
• Turn off automatic updates for applications in preferences for the Creative Cloud app

Adobe staff will announce in this thread when they have a fix and it is released.

Jane