Cannot open PS current version message says "Catch in IPhotoshopApplication, exception encountered:

[lymphocyte@comcast.net]

Cannot open PS current version message says "Catch in IPhotoshopApplication, exception encountered: require fed" (IphotoshopApplication is all one word)

please help

[James24546042idig]

Same problem here

[RoFishy]

same here

[Pushpanjali28312317tpaj]

What is the solution?

[RoFishy]

restart photishop

[sweetyness11]

I am alos having the same problem! I tried to start today and got the error, so then I updated to the newest version and still have the issue. Guess I will keep looking.

[Aleke]

Hey @sweetyness11, welcome to the Community! Could you share a bit more about what you're experiencing? If you could provide your System Info, that would be super helpful. You can find it by clicking on Help > System Info.

I see you’ve already updated the app to the latest version, which is great! We can also try some of the other basic Photoshop troubleshooting steps. These are common solutions to various issues. Hopefully, one of them works! You can find 'em here:  https://adobe.ly/3OPLKJ7

Let me know if you have other questions, and make sure to mention me with an @ when you respond. Thanks!
Alek

[KimberlyPek]

Having same issue. What can I  do????

[Aleke]

Hi @KimberlyPek!

Could you please let me know what version of Photoshop and operating system you're using? Also, when did the error start occurring—was it after an update?

Thanks a bunch!

Best, Alek 😊

[Trevor.Dennis]

@Aleke   I just had the same error message, and it was immediately after a Windows 11 update.

This is the Learn More Link

In my case, simply restarting Photoshop (26.6 m.3014) seems to have cleared the warning dialog.  If this tally's with other people's experience, then it might be useful to say so here.  Check Windows Update History if you are not sure.   26.4.1 Release, and 22.2 also open without any error messages.

[Trevor.Dennis]

I've just realised that the release date on that update was after the other people in this thread posted, so that particular update could not have caused it.