Bridge Photo Downloader does not retain settings between sessions

  • 2
  • Problem
  • Updated 1 week ago
  • (Edited)
Affects Photo Downloader from Bridge on Mac 10.13.6.

User changes made to Location, Create SubFolders, Rename Files, Preserve Filename in XMP, Advanced Options, and Apply MetaData, including selecting the Advanced Dialog, are not retained between instances of the dialog.  This information was saved on previous versions of the product.  This is a bug that affects workflow, causing me to enter error-prone information every time I need to download.  The last serial number for renamed files is also not saved, meaning that I can get overlaps in file numbers.

Operation of the Photo Downloader is not affected, just the persistence of the settings.

Please fix this.

I talked with support over chat.  They opened case ADB-4143873-Q9H9, but told me to report it in this forum.
Photo of Robert Blum

Robert Blum

  • 1 Post
  • 0 Reply Likes

Posted 2 years ago

  • 2
Photo of Jamie Geese

Jamie Geese

  • 4 Posts
  • 0 Reply Likes
I'm having the same problem but, in windows. I talked to tech support and they said it was just a change with the update. I really hope that's not true.
Photo of Robert Baker

Robert Baker

  • 1 Post
  • 0 Reply Likes
Was there any resolve to this....I finally upgraded from CS6 and this was a big part of my workflow.
Photo of Michael Collins

Michael Collins

  • 1 Post
  • 0 Reply Likes
I have the same problem 
Photo of Alex Driesen

Alex Driesen

  • 1 Post
  • 0 Reply Likes
Same here, on MacOS. Any suggestions?
Photo of Derek Adams

Derek Adams

  • 2 Posts
  • 1 Reply Like
I am having the same problem (windows 10), I have lost an important part of my workflow, and the time it is taking me to enter the info again each time is costing me money. It wasn't a problem when I was running windows 7.
I can't believe this has been a problem for 2 years and Adobe still haven't rectified it!
Photo of HHHeflin


  • 21 Posts
  • 1 Reply Like
I've started having the same issue.  Since this thread started two years ago with some people and it seems to have just restarted raising it's ugly head again, and there have been almost daily server updates lately; that suggests that somewhere in those process Adobe has user an old version of at least part of the code to try to resolve some other problem; which then reintroduced the issues back into Bridge. 

FWIW:  I'm on Win10 fully updated.