Colorsync utility can't fix the icc file ?

Go to Macintosh HD/Aplications/System/Librabry/ColorSync/Profiles/ Scroll down to ITU-2020.1cc Select the profile, Right click on it, Get Info, Change Permissions To Read and Write for wheel and for everyone. Run ColorSync Utility, Verify. Problem solved!

Check your Permissions for your Macintosh HD first. If needed, change to Read and Write for wheel and for everyone. Restart. Go back and try to change permissions as described in previous post. Should work without problems. Good luck.

I just upgraded to 10.15.5 and it did fix my color issues with my LG 4K LCD. The ITU-2020.icc file was updated.

The ITU-2020.icc file was recently update February 29, 2020 with the point release of Catalina 10.15.4. Once Apple release 10.15.5 the file has an update of April 6, 2020 which should address all these issues. Currently Apple just release the 4th beta for 10.15.5 so I have no idea when it will officially be released to the public. Maybe someone from Apple could respond and provide a possible date for release?

I found the solution (after the update 10.15.5): I took out the option (check mark) 'high dynamic range' in the system menu for the monitor. Now it seems to work fine (crisp white screen again).

firstly, turn off your computer

secondly, hold down the shift key for ten seconds right after you click the button to turn it back on

thirdly, log in

fourth, go to history and clear history

fifth, restart the computer and sign in again

then it should be fixed because that is safe boot

Just released today (May 26th) macOS Catalina 10.15.5. That will probably solve the problem?

"This is happening to me" comments add weight to the issue. But you may be correct about us just talking to ourselves.

I suspect the .icc file is packaged the way BSD/Linux OSes tend to do, and isn't detectable as a file distinct from its package. You should be able to "see" it in the Colorsync Utility under Profiles > System > Rec. ITU-R BT.2020-1, "Open." The header is visible there in the new panel as the lead component. I don't know enough to diagnose the header by examining its bits, but that's at least one way to see the "problem" data.

St. Steve Jobs, pray for us!

fourth, go to history and clear history

What do you mean by this? Clear the browser history or what?

Please provide steps.

Sherry_2020_MACupdate_causes_M wrote:

firstly, turn off your computer

secondly, hold down the shift key for ten seconds right after you click the button to turn it back on

thirdly, log in

fourth, go to history and clear history

fifth, restart the computer and sign in again

then it should be fixed because that is safe boot

One interesting point: The ITU-2020.icc panel lists the Header size as 556 bytes, but the component itself in the scrollable table above reports "128." Not sure if it's bytes or bits. Even so, it doesn't make sense since bytes are composed of bits (making 128 bits a lot smaller than 556 bytes). This may be the issue.

Just chiming in to say I seem to have the same issue with my Acer 4k monitor after updating to Catalina 10.15.4. Switching the monitor to HDR mode, unplugging and replugging it seems to have helped the issue, but the color is still off, with reds looking purple and blacks looking grey. As well text does not display with the same sharpness as before.

Really hope this is fixed in the next update as another poster suggested as this is super dissapointing.

No, it's not resolved. I have the same issue and when I search for the exact match of the file "ITU-2020.icc" on my mac it doesn't appear. I have hidden files set to display and this file does not exist in any searchable drive. However, it appears as an error when running first aid on Profile First Aid.

Can we have someone who is competent actually reply in this thread? I don't think we need more "this is happening to me" comments. Doesn't that one pretentious bald guy usually show up and ask us to run a bunch of basic diagnostic files and then tells us he can't help us? Why is this color profile issue still happening, I see another thread from 2015 with the EXACT same file that has the SAME repair blocked by a locked file message. What is the issue with apple support, or is this just a glorified forum that is run by fans?

I tried starting up in safe mode, learned this seems to clear the user cache as part of that process (good to know). The instructions are here: https://support.apple.com/en-au/HT201262

But, this hasn't resolved the problem. Can you explain specifically what "go to history and clear history" you are referring to? There are plenty of histories this could be (terminal, browser....).

I am having the same issue with my MAC Pro 15" running Catalina 10.15. That file was updated on02/28/2020 per a system OS update. Tried all the recommendations and nothing works. Apple really needs to fix this.