P: PS 26.5 Droplets Could not complete the Create Droplet command because the file was not found.

[hadi_9157]

When I create a droplet in Photoshop 2025, it creates a folder instead of an EXE file. What is the solution?

[Dom Henry]

It's a right PIA that the creation of new Droplets with the .app extension is still broken with Sequioa 15.5

However, you can get existing droplets working using the following workaround I got running this afternoon after some terminal fiddling.

1. Open terminal

2. Copy in: 

xattr -d com.apple.quarantine

3. Add a space then drag your droplet onto terminal so it copies over the address

4. Which should be like this xattr -d com.apple.quarantine /Users/Username/Filename

5. Hit enter

6. Open System Settings > Go to Privacy & Security - See the Security Menu where it says Allows Applications From - keep this open

7. Open your Droplet - when you get the ...is damaged and can't be opened message hit Cancel

8. Your droplet name should now appear in the Security window with an "Open Anyway" button - click it

9. Your droplet should work

In previous versions of Sequoia this button used to come up as soon as you hit cancel, in 15.5 it is now buried deeper so you need the terminal entry per droplet first. Sigh.

At least you can get existing Droplets to work. Had a mare of day trying to get our product studio back up after an OS update.

"There's always summat..." as we say in Nottingham.

[Scott_BFAR]

@M-H Sorry, but I can't get past your pejorative snark. Telling users that they're not forced to buy PS and can try a free solution etc is beyond pejorative. It's hostile and does not contribute to the community. That kind of open hostility has no place here. 

[M-H]

@Scott_BFAR it was response to person spitting out [cursing removed] caps in couple of messages in row, dont seem like you've been bothered too much with that, double standards? Guy complains he's having to pay for this and that while its not obligatory. Says it wasnt working for years which isnt true, all in caps, but me pointing it all out is suddenly hostile and out of place?

[ExUSA]

I think the overall tone of this thread could be taken down a bit. Yes there is a bug, if you look on these boards, there are a lot of bugs. And YES there are workarounds. Right now, the developers are probably busy with macOS Tahoe compatibility and finishing the next major release for October. I doubt we will see a bugfix before then. Ranting is never helpful on these boards.

[BjörnJärnankar]

Plus one on above. My mailbox's getting spammed with arguments on if somethings a bug or not, a work around or not. I don't really care. Lets just agree there's alternative work processes that works for some but doesnt suit some. 

Regardless it's a feature in their app and its currently not working so should be fixed or removed. 

While at it, of course it's always worth stressing the importance of the feature as it will more likely be prioritzed if Adobes aware on how many is affected. But in a respectful tone of course. 

And thanks to Adobe @Stephen Nielson for showing signs of life so we know we are being heard. 

[bellevue scott]

I am sick to death of users telling us we should be quiet and wait for fix.
It is not your place to moderate this forum. This is THE place to share
notes, rant, and share possible work arounds.

Several of the last posts have been helpful in shedding light on what's
wrong, and have added value to this thread. If you don't like this thread
then leave it, but as long as we're being civil it is not your place to
tell us to chill out and be quiet.

Sent from my iThingy

[ExUSA]

Its actually not a place to rant.

[Christopher3440329747o5]

Yes sir captain. Eye Eye Captain! 

Don't tell me what I can and can't do! I pay for this product and this is a COMMUNITY FORUM where I can RANT anytime I want especially when I am paying GOOD MONEY for a product that DOESN'T WORK 100%. Yet I keep getting emails of all these new AI features and what not.

Hey ADOBE - Why not fix the problems with your software before introducing NEW FEATURES that will probably have NEW PROBLEMS!

[M-H]

@Christopher3440329747o5 

[Content removed by moderator. Please follow the forum guidelines to be kind and respectful or risk being banned from the forums]

[xinfinity]

I'm having this same problem, and it's important to get it fixed because I export photos in multiple sizes every time I create something.

[Dima Belan]

Have same problem macOS Sequoia ver 15.4.1 

[ExUSA]

If you read through the whole thread, there are workarounds. 

[Christopher3440329747o5]

What is the work around that works?

[ExUSA]

Oh good Lord. I already said to create an Applescript or Automator action. 😠

Put this into a new document in Script Editor, and put in your action name and action set. Save as an application. Now you should have a working droplet.

on open docs
	repeat with a from 1 to length of docs
		tell application "Adobe Photoshop 2025"
			activate
			open item a of docs
			--enter your action name and set
			do action "myAction" from "myActionSet"
			--save and close if your action doesn't include those steps
			save current document
			close current document
		end tell
	end repeat
end open

[Aaron Tipton]

That's actually helpful, thanks. Sorry all us idiots don't know scripting because we had something that worked without it for the last 25 years.

[Aaron Tipton]

But alas, doesn't seem to do anything. No error, just nothing.

[Aaron Tipton]

Oh I see now, saved as Application from ScriptEditor. It worked to run a simple action. WooHoo!

Testing with more specific actions to save new files.

[Aaron Tipton]

Works with basic actions, but more complex things like converting file types and saving new images are trickier, will take more steps than just that apparently. But definitely will be heading down this path if Adobe doesn't get this fixed.

[10greenmen]

Still here on 26.9. This is inept.

[Khadrelt]

Just installed 26.10, the issue persists.

[Aaron Tipton]

DROPLETS WORKING IN THE BETA VERSION!!! I'm now able to make a Droplet with the Beta version 26.11.0. But still not fixed in the current version 26.10. Install the beta and move on, but the next regular update should be the end of this it looks like.

[Scott_BFAR]

Thanks Aaron! That's fantastic to know. Looking forward to them working again 

[pierreb94]

Yes it works with beta...but it does not work. I mean : I can now create a droplet, after fixing the problem of security in MAC OS, I put an image on the icon, Photoshop is lauched but error message and impoosible to get a result.

I have an action to reduce resultion of image. I have created a droplet years ago and I know that it works perfectly. 

What I have done : export this action from PS2025 to BETA, check if it works in BETA >>> no problem. Create a Droplet, fix the issue in MacOS, drag an image on the droplet, BETA is open, and error message : IMAGE SIZE COMMAND IS NOT AVALAIBLE. This command is the 1st line of the action.

So, for me, the problem is half fixed...

Regards

[Aaron Tipton]

Hi @pierreb94 , I would double check of your droplet settings. As far as I can tell the droplets I can make now are just fine, I've tested a few now. I always get confused about when I need an open step and when to use the override action open commands checked, it's a little unintuitive IMO. But my new droplets from the BETA are working fine. Good luck!

[AlessandraKal]

Il problema persiste anche con la versione 26.10 su MacBook con MacOs Sequoia 15.5 (24F74). Ma è arrivata mail da Adobe che dice che il prezzo della creative suite aumenterà di circa 10 € al mese... ma non sono in grado di far funzionare delle funzioni ESSENZIALI per chi lavora