Skip to main content
Participant
April 29, 2025
In Development

P: Adjusting layer properties doesn't work for Hue/Saturation/lum. HSL layers

The tab to click on and change the properties for an adjustment layer randomly disappears. Quitting and re-opening the app solves the issue, but it will happen again within minutes, usually when switching between different projects or different app on the computer. 

On Photoshop v26.6 - Mac Mini M4 pro, 32gb ram, 1tb ssd.

 

Any help would be appreciated!

ss

144 replies

Ged_Traynor
Community Expert
Community Expert
October 23, 2026
Participant
October 23, 2026

I have the same issue. I’m on mac tahoe 26.6.2 and PS 27.11. Any updates on this?

Translate
October 8, 2026

When selecting the Hue / Saturation adjustment layer the Properties does not show, only the layers mask options. This only happens for that adjustment layer.

I’ve tried restarting and it will work only a few times and then go back to not showing the Properties.

It’s on Photoshop 27.10.0 and has been going on for quite a few months now.

See video for example, where it shows how it works fine for the level adjustment layer but not the Hue / Saturation adjustment layer.

 

 

Translate
robertw44482386
Inspiring
September 2, 2026

Bug still exists in 27.10. Can be reproduced by enclosing the layer in question inside a group, as has been mentioned below multiple times. 

Translate
Inspiring
August 28, 2026

​@Srishti Bali 14 days ago you were looking forward to our response?

 

Translate
Srishti Bali
Community Manager
Community Manager
September 17, 2026

​@LEMONardo 

 

Thanks for confirming that the issue still persists, and apologies for the experience. I’ve already shared this with the team, and they’re actively working on it.

Translate
Thanks, Srishti Bali | Community & Engagement Strategist, Digital Imaging | Adobe
Participant
August 27, 2026

Updated to 27.9.1 get it fixed guys ...this is actually really pathetic been going for months now...especially as a subscription service, you guys are too comfortable.

Translate
Srishti Bali
Community Manager
Community Manager
August 13, 2026

Hi all,

 

We have recently released build 27.9.1, which includes fixes for similar issues. Could you please install the latest build 27.9.1 and let us know if you are still experiencing this issue?

Looking forward to your response.

Translate
Thanks, Srishti Bali | Community & Engagement Strategist, Digital Imaging | Adobe
Inspiring
August 13, 2026

​@Srishti_Bali ​@Srishti Bali 

 

No. It has NOT been fixed in Photoshop 27.9.1 as of Aug 14, 2026.

 

I previously provided a simpler way to 100% reproduce this bug, but threaded replies get buried easily in this new forum. So I’m gonna post it here again:

  1. Create or open any image
  2. Create a group and wrap a layer in it
  3. Flatten the group (⌘+E)
  4. Create a Hue/Saturation Adjustment Layer
  5. There is your bug, simple as that.

 


 

Please talk to the engineering team and find out if this error code (0ddf78.171) helps locating the bad codes. I believe they are related.

 

Translate
Participant
July 22, 2026

Just following up to see if this is something that Adobe is looking into or planning to fix. Been dealing with this for over a year now.

Translate
Sameer K
Community Manager
Community Manager
July 23, 2026

Thanks for the comment. The fix is in the pipeline. You can also check Photoshop (beta) from the Creative Cloud desktop app > Apps > Beta Apps section to verify if the issue exists.


Thanks!
Sameer K
(Type '@' and type my name to mention me when you reply)

Translate
Klaus Madengruber
Participant
July 3, 2026

Is this ever going to get fixed. I feel like it got worse again with the last update. I'm working in 27.8 on an M3 Mac Studio. 
To me it only ever happens when I’m working in 16bit and the files are quite large. 

Translate
Participant
June 27, 2026

This issue is so annoying - I get it intermittently too, usually when I’m in a hurry to finish some work (of course).  It’s happening again today… The first time it happened (over a year ago) I assumed it was me as I was still ‘relatively’ new to PS so it’s disappointing to read that this has been a known issue for so long - especially considering the subscription price.

Translate