Skip to main content
Participant
November 21, 2021
Question

"Could not complete the convert to profile command because the ICC profile description is invalid"

  • November 21, 2021
  • 3 replies
  • 977 views

Getting 

"Could not complete the Convert to Profile command because the ICC profile description is invalid"

"Could not complete your request because the ICC profile description is invalid."

Error messages 

 

I'm needing to export end-product sRGB JPEGS and can't seem to convert to ANYTHING and also when "edit in Photoshop" from Lightroom Classic ProPhoto source images.

 

 

Completely lost - have already thrown out the ICC profiles I thought might be corrupted.
When I click 'continue' the images are all HUGELY red-oversaturated/shifted

 

Machine is a Dell XPS 15 9560; and yes I have calibrated both laptop screen and exteral ACER monitor panel with my Spyder4.

?help?

 

 

This topic has been closed for replies.

3 replies

NB, colourmanagement
Community Expert
Community Expert
December 28, 2021

In case it helps, here are some more detailed instructions on how to temporarily set the display profile to sRGB as a test of DFosse's idea:

Windows display profile, display profile issues on Windows

 

Here's something to try

It'll only take a few minutes and is good troubleshooting.

 

At least once a week on this forum we read about this, or very similar issues of appearance differing between colour managed applications.

Of course you must not expect accurate colour with programs such as Windows "Photos", because colour management is not implemented there, so such programs are incapable of providing accurate image display.

 

Unfortunately, with Microsoft hardware: Windows updates, Graphics Card updates and Display manufacturers have a frustratingly growing reputation for automatically installing useless (corrupted) monitor display profiles.

I CAN happen with Macs but with far less likelihood, it seems.]

 

The issue can affect different application programs in different ways, some not at all, some very badly.

 

The poor monitor display profile issue is hidden by some applications, specifically those that do not use colour management, such as Microsoft Windows "Photos".

 

Photoshop is correct, it’s the industry standard for viewing images, in my experience it's revealing an issue with the Monitor Display profile rather than causing it. Whatever you do, don't ignore it. As the issue isn’t caused by Photoshop, please don’t change your Photoshop ‘color settings’ to try fix it.

 

To find out if the monitor display profile is the issue, I recommend you to try temporarily setting the monitor profile for your own monitor display under “Device” in your Windows ‘color management’ control panel to “sRGB IEC61966-2.1”. (If you have a wide gamut monitor display (check the spec online) it’s better to try ‘AdobeRGB1998” here instead as it more closely approximates the display characteristics).

 

 

You can click to ADD to add “sRGB IEC61966-2.1” (or AdobeRGB1998) if not already listed there.

Again - IF you have a wide gamut display I suggest trying “AdobeRGB1998”

 

Once it’s selected, be sure to check “Use my settings for this device” up top.

And click on “set as Default Profile - bottom right

 

Screenshot of Color Management Control Panel

 

Quit and relaunch Photoshop after the control panel change, to ensure the new settings are applied.

 

Depending on the characteristics of your monitor display and your requirements, using sRGB or Adobe RGB here may be good enough - but no display perfectly matches either, so a custom calibration is a superior approach.

 

If this change to the Monitor Display profile temporarily fixes the appearance issue, it is recommended that you should now calibrate and profile the monitor properly using a calibration sensor like the i1display pro, which will create and install its own custom monitor profile. The software should install its profile correctly so there should be no need to manually set the control panel once you are doing this right.

 

 

 

Still got problems?

If you want to try a method that’s proved successful to rule out many an issue we see with Photoshop, you can reset preferences:

 

To reset the preferences in Photoshop: 

https://helpx.adobe.com/photoshop/using/preferences.html

 

Note: Make sure that you back up all your custom presets, brushes & actions before restoring Photoshop's preferences. Migrate presets, actions, and settings

 

 

I hope this helps

neil barstow, colourmanagement net :: adobe forum volunteer

google me "neil barstow colourmanagement" for lots of free articles on colour management

[please only use the blue reply button at the top of the page, this maintains the original thread title and chronological order of posts]

D Fosse
Community Expert
Community Expert
December 25, 2021

I suspect the bad profile here is the monitor profile. While a profile conversion in Photoshop doesn't directly involve the monitor profile, it's still part of the chain as the ultimate end conversion after the document profile has been changed.

 

Both Dell and Acer are notorious for shipping bad monitor profiles. If you have a Spyder, that should override and replace the manufacturer profiles, but maybe it doesn't. Or maybe the Spyder profiles are bad.

 

Or maybe a bad profile for the main display is enough to throw the whole process.

 

Either way, I would start by going into Windows Color Management and delete all monitor profiles for both screens, and then assign sRGB IEC 61966-2.1 to both. Or Adobe RGB if wide gamut. If that stops the error message, you know it's a broken monitor profile and you can start from there. Check all Spyder settings, in particular it should be set to make version 2 and matrix-based profiles. Not v4 or LUT (table-) based.

Sahil.Chawla
Adobe Employee
Adobe Employee
December 25, 2021

Hi there,

Sorry to hear that. Could you please have a look at this conversation and let us know if it helps? https://community.adobe.com/t5/color-management-discussions/icc-profile-is-invalid-photoshop-2020/td-p/10938041

 

Regards,
Sahil

Known Participant
November 11, 2022

I have the same problem - the action will run if I click it from the panel in the app, but if I run it via a droplet, it doesn't 😞