Lightroom 6.3/Camera Raw 9.3: Broken "Default Develop Settings"

  • 9
  • Problem
  • Updated 7 months ago
  • Solved
  • (Edited)
Massive issue after updating to Lightroom 6.3.
The “Default Develop Settings” isn’t working, the settings are reset every time you start Lightroom.
I’ve got hundreds of default settings for different ISOs saved for a number of cameras, all don’t work.
The folder with the Default Develop Settings still contains all my defaults:
But they don't load anymore with Lightroom 6.3, so when I hit "reset" on a photo it resets the photo to lightroom default values instead of what I set in the "default develop settings".

When I try to set a new “Develop Setting”, let’s say, default develop setting for clarity on ISO100 photos is +10, it works for the duration of my lightroom session, BUT as soon as I close lightroom and restart it, the default develop setting doesn’t work, i.e. when I click "reset" on a photo, it resets the clarity back to 0 which is the lightroom default and not +10 which is my default for the ISO100 photo (this is of course a simplification of the problem).

Does anybody else have this issue? This is a very big deal for me, these default develops settings save me huge amounts of time normally...
Photo of Michael Wiejowski

Michael Wiejowski

  • 10 Posts
  • 0 Reply Likes
  • frustrated

Posted 9 months ago

  • 9
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 869 Posts
  • 179 Reply Likes
Official Response
Hi Michael, I able to reproduce the bug using your test files (it is Sony camera specific). The bug has been affecting a few specific camera models for a while. But what's new in Lr 6.3/ACR 9.3 is that the bug started affecting all Sony cameras. Lr 6.3/ACR 9.3 began to honor some in-camera defaults at the request of the vendor, but unfortunately it exposed the unexpected side effects to all sony models.

Sorry about that and the team will fix the bug in the next update of Lr and ACR update. Thanks for reporting the issue.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Chief Customer Advocate

  • 11158 Posts
  • 887 Reply Likes
Official Response
This issue should be resolved by installing update that was released today: