Skip to main content
bclee337
Inspiring
October 28, 2025
Answered

"There was a problem with Generator." error popup at start on new install of Photoshop 2025

  • October 28, 2025
  • 2 replies
  • 350 views

I just installed Photoshop 2025 on a new computer, M4 Max MacStudio on MacOS 15.7.1, and when I open it I get this error popup.

There was a problem with Generator. If the problem persists, please see:

http://www.adobe.com/go/photoshop_generator_errors_en

None of the solutions there seem relevent to a new install. I have no virus protection for instance. Log errors are copied below, starting with "No viable plugins were found in '/Applications/Adobe Photoshop 2025/Plug-ins/Generator/'" -- and indeed that directory looks to be empty? The later ones make it look like there's a bug in some script.

I've read many posts here on similar problems but none of the mentioned solutions that I've tried so far have made any difference. Help?

From the log:

 

Log file created on Thu Oct 16 2025 16:28:32 GMT-0700 (Pacific Daylight Time)

[info:core 16:28:32.136 generator.js:114:22] Launching with config:
{}
[info:core 16:28:32.136 generator.js:116:26] provided PS information:
version 26.8
path/Applications/Adobe Photoshop 2025/Adobe Photoshop 2025.app

 

info:core 16:28:32.142 generator.js:237:30] Detected Photoshop version: 26.8.0
[warning:app 16:28:32.151 app.js:234:29] No viable plugins were found in '/Applications/Adobe Photoshop 2025/Plug-ins/Generator/'
[info:core 16:28:32.152 generator.js:1926:26] Loading plugin: generator-assets (v2.9.13) from: /Applications/Adobe Photoshop 2025/Adobe Photoshop 2025.app/Contents/Required/Plug-ins/Generator/assets.generate
[warning:core 16:28:32.213 generator.js:915:26] WARNING the imageChanged event is expensive, please consider NOT listening to it
[info:core 16:28:32.214 generator.js:1942:26] Plugin loaded: generator-assets
[info:core 16:28:32.215 generator.js:1926:26] Loading plugin: crema (v3.2.13) from: /Applications/Adobe Photoshop 2025/Adobe Photoshop 2025.app/Contents/Required/Plug-ins/Generator/crema.generate
[info:core 16:28:32.333 generator.js:1942:26] Plugin loaded: crema
[warning:core 16:28:32.567 generator.js:915:26] WARNING the imageChanged event is expensive, please consider NOT listening to it
[warning:core 16:28:34.878 generator.js:133:30] Photoshop error {
id: 15,
body: 'Error 1302: No such element\rLine: 8\r-> var desc = app.getCustomOptions(params.key);'
}
[warning:core 16:28:34.879 generator.js:378:26] Error in JSX file with params ./jsx/getCustomOptions.jsx { key: 'crema' } Error 1302: No such element Line: 8 -> var desc = app.getCustomOptions(params.key);
[warning:generator-assets 16:44:58.446 layer.js:554:34] Unhandled property in raw change: timeContent true
[info:core 17:04:55.777 generator.js:128:30] Photoshop connection closed
[error:app 17:04:56.785 app.js:141:17] Exiting with code 0: Generator close event

Correct answer bclee337

I decided to try running it under Rosetta once to see if it made a difference, and running under Rosetta there was no error. I then switched back to running it native, and still no error! That's an odd fix, but for now it's working. Even more suprising: I had installed Photoshop Beta, and while it had Enable Generator off by default, once I turned it on, it had the same error. After I ran normal Photoshop 2025 in Rosetta, Photoshot Beta also stopped having the error. I had not run it in Rosetta.

In any case, there's the full list of steps in case it's helpful to anyone else. Reading this forum it sounds like versions of this are a common problem, and the fixes seem random and may or may not work for anyone else. 

First, make sure you have Enable Generator checked in Photoshop settings.

 

  1. Right click on the Photoshop app, select "Get Info", and check the box "Open using Rosetta". You might be asked to install Rosetta at this point.
  2. Restart the Mac.
  3. Open Photoshop. (It was slow!!!) Hopefully there's no error. Close the app.
  4. Same as step 1 but uncheck "Open using Rosetta" this time.
  5. Restart the mac.
  6. No more error mesage, hopefully.

 

2 replies

bclee337
bclee337AuthorCorrect answer
Inspiring
October 28, 2025

I decided to try running it under Rosetta once to see if it made a difference, and running under Rosetta there was no error. I then switched back to running it native, and still no error! That's an odd fix, but for now it's working. Even more suprising: I had installed Photoshop Beta, and while it had Enable Generator off by default, once I turned it on, it had the same error. After I ran normal Photoshop 2025 in Rosetta, Photoshot Beta also stopped having the error. I had not run it in Rosetta.

In any case, there's the full list of steps in case it's helpful to anyone else. Reading this forum it sounds like versions of this are a common problem, and the fixes seem random and may or may not work for anyone else. 

First, make sure you have Enable Generator checked in Photoshop settings.

 

  1. Right click on the Photoshop app, select "Get Info", and check the box "Open using Rosetta". You might be asked to install Rosetta at this point.
  2. Restart the Mac.
  3. Open Photoshop. (It was slow!!!) Hopefully there's no error. Close the app.
  4. Same as step 1 but uncheck "Open using Rosetta" this time.
  5. Restart the mac.
  6. No more error mesage, hopefully.

 

Legend
October 28, 2025

Ah, the other show (involving Ps Beta) drops...

 

Larry
Legend
October 28, 2025

My /Applications/Adobe Photoshop 2025/Plug-ins/Generator/ folder is empty, too. I'm going to guess this condition isn't responsible for the crash.

Your second screenshot shows 'Enable Generator' is checked in Settings; so, the error doesn't crash Ps? Have you tried to uncheck/close/reopen Ps? (it's unchecked on my system, 26.0.1).

--

edit: I checked the Enable Generator box, quit Ps, restarted without error.

 

Larry
bclee337
bclee337Author
Inspiring
October 28, 2025

Unchecking it and restarting makes the error go away, checking it and restarting it makes it come back. The help page made me think unchecking it was a temporary workaround at most. I have no idea what it does, but it was checked by default after the install.

Legend
October 28, 2025

How frustrating for this to occur on a brand-new system! My trickle of ideas has run out. The Mighty Brains Who Lurk the Community should be along shortly.

 

Larry