Skip to main content
PMRPVR
Participating Frequently
April 19, 2026
Question

Bridge 2026  (16.0.3) stopped working on all three of our MAC computers at the same time!

  • April 19, 2026
  • 4 replies
  • 118 views

Bridge 2026 (16.0.3) stopped working on all three of our MAC computers at the same time. Working on Tahoe 26.4.1. We have uninstalled and reinstalled Bridge, have reset preferences and emptied cache, deleted startup scripts, all to no avail. Sometimes we can open a folder of images in Bridge, but get the spinning colored ball anytime we try to do something, so then we have to force quit. Sometimes we get the spinning ball immediately upon Bridge opening. Sometimes we can open a folder of images but only get gray boxes, so there are multiple ways Bridge is not working correctly. Also having the same issue now with Bridge 2025. Any fixes out there?

    4 replies

    nguyenrichy
    Participant
    May 2, 2026

    Today I have the same problem. The Bridge kept crashing and frozen. Tried Uninstall, Re Install Bridge, PTS, PTS beta..., clear catche, start script... all did not work. But latter I found the solution that turn out too simple to believe. What I have done is to open the Bridge (do not click on any folder if not it hang again), go to Adobe Bridge 2026 menu on menu bar then open Camera Raw Setting. Go to Perfomance tab. Look for  Reset GPU Support and click to reset. Then close Bridge completely (or close and restart the computer) for reset to take effect. Done. Hope it will helps you.

    PMRPVR
    PMRPVRAuthor
    Participating Frequently
    May 3, 2026

    Thanks. Initially this fix did not work for us, but it is working now, although sometimes it takes a few tries for it to kick in. At least we can use Bridge now on our computers even if it’s finicky. Hopefully Adobe will fix this issue in a future update. Thanks again.

    nguyenrichy
    Participant
    May 5, 2026

    It works for my Macbook Pro M4 but it still crash sometimes with my cousin's M2. So I did  try to unclick "Use GPU for image processing " in the same Performance tab of Camera Raw Setting before Reset GPU support. Then restart.  Now it is working. You can try the same. Anyway hope Adobe can fix it soon. It is quite anoying.

    Jeff Arola
    Community Expert
    Community Expert
    April 22, 2026

    If you’ve updated to the Camera Raw 18.3 plugin and those folders have camera raw files, then maybe the plugin is at fault.

    I suggest that because there have been enough user complaints about poor performance of the Camera Raw 18.3 plugin that Adobe posted an updated Camera Raw 18.3 plugin, so it’s worth a shot to install the updated Camera Raw 18.3 plugin and see if that makes any difference.

    https://community.adobe.com/bug-reports-562/p-acr-18-3-is-unusable-unless-you-disable-gpu-acceleration-1558055

    PMRPVR
    PMRPVRAuthor
    Participating Frequently
    April 22, 2026

    Thanks for the info, Jeff. I was on the phone with Adobe for 3 hours today with no fix to the multiple issues we’re having in Bridge. Will give this a try. Fingers crossed! 

    PMRPVR
    PMRPVRAuthor
    Participating Frequently
    April 22, 2026

    Unfortunately, this fix did not work for us. We installed the updated version of ACR 18.3 x 2529 using the link provided in the post. We can no longer navigate between folders on two of our 3 Mac computers, nor open new folders, and Bridge continues to crash when trying to quit the program, so we have to force quit each time. With Adobe’s “help” yesterday from a few different agents, it has gone from bad to worse. Frustrated beyond words!!!

    Legend
    April 21, 2026

    Are you using any cloud services (Dropbox, iCloud, Google Drive, etc)?

    PMRPVR
    PMRPVRAuthor
    Participating Frequently
    April 21, 2026

    No.

    Jeff Arola
    Community Expert
    Community Expert
    April 21, 2026

    If you go to Apple>System Settings>Privacy & Security>Full Disk Access, is Bridge 2025 or 2026 listed?

    If not try adding them and see that solves the issues.

    PMRPVR
    PMRPVRAuthor
    Participating Frequently
    April 21, 2026

    Yes, we’ve done that already. Unfortunately it didn’t help. Spent a few hours on the phone yesterday with Adobe and they weren’t able to fix the issues in the time we had available.