After the 10.0.3.138 update, Bridge no longer opens files using Windows Explorer's file type associations. For example, if you try to open an mp4 file Bridge will not open it in Movies & TV. Instead it will open it in a third party app if you have one installed that handles that file type. Otherwise, if there isn't a file type associated with it, Bridge will simply not open the file. Changing the file type associations won't work because there are no options for any of the native Window apps. This was not the case in 10.0.2. For now the only fix I have found for this is to roll back to the previous version of Bridge. I hope this bug gets addressed in future updates.

If a video is selected (last in a move block or selected for copy), the move/copy fails because the video is open in the DyanmicLinkMediaServer.exe (error discovered in File Explorer). Apparently, the file is opened in the media server used to sort of play the file (it is a poor video player).

The move/copy fails and must be done with file explorer externally. I don't recall encountering the issues with previous versions, but you must have the video file selected for it to manifest--the last in a selection or individually.

Also, the media player does not support HEVC Main or Main10.

I just installed Bridge CC 2019 yesterday on MacOS Sierra. On local and Network drive files, the option to perform an EDIT -> Cut the file is greyed out. Command + X doesn't work either. I can only Copy and Paste. I tried uninstalling and reinstalling, didn't work. I tried running Bridge 2018 separarely on my MacOS system, and the file cut function works as is it's supposed to. It also works on my Bridge CC 2019 on Windows 10 system as it should, so this is really limited to my install of Bridge 2019 on my iMac.

Anyone else having this issue or facing this problem?

Windows 10. Bridge 2019.
When starting, Bridge 2019 loads existing collections from ".../AppData/Roaming/Adobe/Bridge CC 2019/Collections".

BUT.. Having had multiple versions of bridge CC on the workstation as they have upgraded and removed themselves over time, I have "Bridge CC/Collections", "Bridge 2014/Collections" up to "Bridge 2019/Collections" under my AppData directory.

Currently any new Smart Collections created actually SAVE themselves under "Bridge CC/Collections", which is not even looked at by Bridge 2019 when loading smart collections.

So, to create any new Smart collection, I have to manually move the collection file "New Smart Collection #.collection" from the "Bridge CC/Collections" to "Bridge 2019/Collections" and restart Bridge 2019. It then shows up in Bridge 2019. Very irritating.

In vain I searched for a registry entry, hoping that maybe it was a leave-behind during upgrades I could just change. No such thing.

Also tried to "hide" the older "Bridge CC/Collections" directory (renaming it), hoping that Bridge 2019 would then start using the correct directory on saving. This instead has the side-effect that attempting to save a new smart collection simply silently fails. Simply, nothing happens, with no error message at all, when clicking the "Save" button on the new collection settings. The collection settings window stays active, no error message. Only way out being the Cancel button.

Please teach Bridge to use the same directory when saving and when loading Smart Collections.

In Adobe Bridge CC 2019 sidebar view (left sidebar with folders), some hidden system directories are visible in macOS High Sierra 10.13.x and Mojave 10.14.x.

These folders are for example:

• "private",


• "Network",


• "usr",


• "sbin",


• "cores",


• "bin".

All folders are located in the macOS root directory. Normally these folders are not visible and should be hidden. Hide and Unhide files/folders within macOS preferences is has no effects in Adobe Bridge CC (at least not in the macos root directory).

Turning on/off the "show hidden files" in Adobe Bridge CC preference option has also no effect in the macOS root directory but in all other directories (e.g. show/hide user "Library" is working with turning on/off appropriate preference in Adobe Bridge CC and macOS).

It seems Adobe Bridge CC does not understand the "hidden" flag of files in the macOS root directory. This bug is visible in Adobe Bridge CC version 2017/2018 and in the current version.