25.1 - Rosetta mode and Remove Tool

Well....It's not a matter of buying - the product hasn't been updated. If you could show where to find this update I will be surprised - especially after this message. 

@SeanBPics Adobe has been pretty clear that going forward the Remove tool requires native versions of PS not Rosetta. If you choose to continue to use the plugins requiring Rosetta, you should probably stay on your stable version until and update for the plugins is available.

I also reported this same issue with the remove tool not working in rosetta ever since 24.7 photoshop beta and according to adobe support it will not updated in the up coming versions. Also stuck on version 24.6 currently where it still works perfect in rosetta with all my plugins still intact.

@gs-dk what do you need to get in contact with the vendor for? You need to purchase the upgrade.

I have been in contact with Anthropic 2 weeks ago - and still it's just PortraitPro that's working. But I will try it again. 

Just a quick search shows the latest updates from Anthropics supports M1/M2 chips. You may want to do some research.

https://www.anthropics.com/portraitpro/photo_editing_software/new_in_v23/#m1-support

You're basically on the clock with those plugins. There will come a point where even Rosetta will not work for those with current Photoshop. If you wish to continue to use them I would strongly suggest turning off updates for both your OS and Photoshop in order to continue using them, even with this workaround solution.

A future OS or PS update could render them completely unuseable.

I guess you are rigty - but - it worked around Beta 24.6, so I guess it can work now as well.

I have a lot of very good plug ins that don't work in Native- Products from Anthropics (only plugin working is Protrait Pro) - Plug-in from Infinite not working - ADP Lumiflow not working - and several others. That's why....

@gs-dk Remove tool will never work in Rosetta mode. Rosetta mode is meant for older version plugin support - your focus should be on pressuring the plugin developer to update for native M1/M2 chips or find other solutions that are native supported. This will only get worse as time goes on.