Skip to main content
Participant
Nov 18, 2026 1:15 PM UTC
Open for Voting

Lightroom Classic v16.0: All AI Masking tools fail on iMac (macOS 15.8.3 / Radeon Pro 560X), while working in Camera Raw / Photoshop 2027

Issue Summary:
Immediately after updating to Lightroom Classic v16.0, every single AI selection and masking tool (Select Subject, Select Sky, Select Background, Object Selection, and People/Skin masks) stopped working completely on my iMac Retina 4K. 

System Specifications:
- Model: iMac (Retina 4K, 21.5-inch, 2019)
- OS: macOS Sequoia 15.8.3
- Processor: 3 GHz 6-Core Intel Core i5
- Graphics: Radeon Pro 560X 4 GB (Metal supported)
- Memory: 32 GB 2667 MHz DDR4

Steps to Reproduce:
1. Open Lightroom Classic v16.0 on macOS Sequoia 15.8.3 with an AMD Radeon Pro 560X 4 GB GPU.
2. Open any RAW file in the Develop module.
3. Open the Masking panel and select any AI mask (Select Subject, Select Sky, Objects, or People).

Expected Result:
Lightroom Classic generates the AI mask normally using GPU acceleration, just as it did prior to the v16.0 update.

Actual Result:
All AI selection and masking tools fail immediately and cannot generate any masks.

Diagnostic Proof (Confirmed LrC-Specific Bug, Not Hardware or Catalog Related):
1. Works Flawlessly in Photoshop 2027 & Adobe Camera Raw: On this exact same iMac and macOS installation, opening the same RAW files in Photoshop 2027 via Adobe Camera Raw runs all identical AI masking tools (Select Subject, Object, Background, Sky, People) without any errors. This confirms 100% that the Radeon Pro 560X hardware and macOS Metal drivers are capable.
2. Fails on a Brand-New Catalog: Creating a completely new Lightroom catalog with just 3 RAW files still results in immediate failure for all AI selection tools.
3. GPU Reset & Rollback to LR 15 Failed: Deleted/renamed Camera Raw GPU Config files and local Adobe support directories, rolled back to Lightroom Classic 15, and reinstalled v16.0—the issue persists. This indicates the v16.0 update altered shared background components or GPU/Metal handling specifically for Lightroom Classic.

Support Case Reference: {Case details removed by MOD}

Please investigate and log this regression for Lightroom Classic's GPU/Metal handling on Intel Macs with AMD Radeon 500-series GPUs.

System Info:
[Šeit ielīmē tekstu no Lightroom Classic: Help > System Info > Copy]
 

    8 replies

    Srishti Bali
    Community Manager
    Community Manager
    Nov 18, 2026 7:27 PM UTC

    Hi ​@paul1808  and ​@jurisz65817154 

     

    Thank you for sharing such a detailed report and for taking the time to troubleshoot the issue extensively.

    I'm really sorry to hear about the frustration and disruption this has caused, especially given the time you've already spent trying to resolve it with Adobe Support. I understand how important these AI masking tools are to your workflow, and I appreciate your patience.

    I would also kindly request that you avoid sharing your support case details publicly, as they are confidential information associated with your account.

    I've reviewed your support case and can confirm that it has been escalated to a senior team member. They may reach out to you soon with further assistance.

    In the meantime, could you please try the following steps and let me know how it goes?

    1. You're currently running macOS Sequoia 15.8.3, which is alteast 2 years old OS. Please check whether a newer compatible macOS version is available for your iMac and consider updating, as OS updates can include graphics-related fixes and compatibility improvements.

    2. Please try renaming the ModelZoo folder.

      • Quit Lightroom Classic completely.

      • In Finder, select Go > Go to Folder.

      • Navigate to:
        ~/Library/Application Support/Adobe/CameraRaw/

      • Locate the ModelZoo folder and rename it to ModelZoo.old.

      • Relaunch Lightroom Classic and test the AI masking tools again. 

     

    I understand how disruptive this has been, and I appreciate your patience and cooperation as we work toward a resolution.

    Please let us know how it goes after trying these steps.

    Translate
    Thanks, Srishti Bali | Community & Engagement Strategist, Digital Imaging | Adobe
    Participant
    Nov 18, 2026 8:02 PM UTC

    I am on the latest Mac OS: Golden Gate 27.2.1
    I do not use ModelZoo so it is unlikely that is a culprit.

    Translate
    johnrellis
    Legend
    Nov 18, 2026 8:16 PM UTC

    [View this post in your web browser. It contains formatting and images that don't appear in email.]

    ​@paul1808 I do not use ModelZoo so it is unlikely that is a culprit.

     

    The ModelZoo contains the AI models that LR uses to implement its AI commands.If you’re invoking an AI command, LR is using the ModelZoo. So give Srishti’s diagnostic a try.

     

    If that doesn’t help, then please do the LR menu command Help > System Info, click the Copy button in the upper right corner, and paste into your reply here, so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set.  That will avoid having to play twenty questions.

    Translate
    johnrellis
    Legend
    Nov 18, 2026 7:25 PM UTC

    [View this post in your web browser. It contains formatting and images that don't appear in email.]

    iMac (Retina 4K, 21.5-inch, 2019), Radeon Pro 560X 4 GB (Metal supported)

     

    Over the past year, there has been an increasing number of reports of AI masking and other AI commands failing on Intel Macs with AMD Radeom R500- and 5000-series GPUs.  Apple and AMD released a buggy graphics driver in Mac OS 26.3 that affected a large number of users, and the only known workaround was to roll back to 26.2:

    https://community.adobe.com/questions-675/p-people-mask-detection-fails-no-people-found-1615313?postid=7766598#post7766598

     

    https://community.adobe.com/questions-675/p-people-masking-fails-on-mac-intel-1551766?sort=oldestFirst#comments

     

    Apple has dropped support for Intel Macs in Mac OS 27, and AMD hasn’t sold graphics chips to Apple for six years, so in my opinion it’s unlikely that Apple and AMD will release another version of Mac OS 27 containing fixed graphics drivers for the numerous AMD chips sold with Intel Macs.

     

    That other apps, including Photoshop, work correctly while LR Classic does not is not strong evidence that there’s a bug in LR Classic.  LR isn’t coded for specific GPUs or drivers, instead using the generic Mac OS graphics interface.  And each app uses that interface in unique ways, with some apps tripping over bugs that don’t affect other apps.  With the problem above with Mac OS 26.3, rolling back to Mac OS 26.2 avoided the problem, stronger evidence the issue was in the AMD driver released in 26.3.  (I see that you’re on Mac OS 15.8.3, so you’re not in that bucket.)

     

    Adobe is constantly changing how LR and other apps use GPUs, as they get more capable and newer AI algorithms demand more resources. As a result, LR and other apps that stress GPUs are constantly tripping over bugs in graphics drivers, of which there are many, which is why Nvidia, AMD, and Intel release a couple of new driver versions each month.

     

    As a less-than-satisfactory workaround, you could try rolling back to LR 15.5.1. Luckily, LR 16.0 didn’t introduce a new catalog format, so rolling back should be easy to test.

    Translate
    Participant
    Nov 18, 2026 5:17 PM UTC

    I’m having the same issues. LR just freezes when doing any AI/Masking tools. The progress bar is displayed but no progress. This has happened since installing v16.0. 

    Translate
    Participant
    Nov 18, 2026 5:51 PM UTC

    Thanks for confirming! Could you also share your OS and GPU specs (Help > System Info)? That will help Adobe engineers pinpoint the exact hardware/driver combination affected by v16.0.

    Thanks for confirming! This bug completely destroyed my nerves — I wasted two full days trying to fix it. Adobe support even connected to my computer via a remote screen-sharing session and still couldn't solve it.

    I've lost a ton of time and money, started drinking again, kicked my wife out of the house, and yelled at the dog. All my work is completely stalled. What am I even paying for if a single update gets everything screwed up like this? At this point, we should demand $1 million in compensation!

    Translate