3 Replies Latest reply on Jan 3, 2018 7:27 PM by Dave Addo

    Bizarre file association problems - Win 10, CC2018 and CS5

    Dave Addo Level 1

      I set up a new Dell XPS PC a couple of days ago, with Windows 10 Pro. I installed Photoshop CC2018, and then my old copy of the CS5 Suite Premium (after first deregistering it on my old PC).


      I am having huge problems with file associations.  Windows has kindly let me association .psd, .tif/.tiff, .dng and .bmp files with PS CC2018, plus a bunch of other minor formats.


      BUT - I cannot association jpegs or raw files with CC2018.  I am able to set CS5 as the default for .jpg files, but only Windows 'Photos' for .jpeg  or .raw format files.


      It seems completely random which programs Windows puts in the list I can choose from.  Sometimes there is an option to look for more 'apps', sometimes not.  When there is, if I navigation to my CC2018 Photoshop.exe file and select that, the association stays as CS5. With .raw, there is no option to choose anything other than the Windows Photos app.


      Also, if I right-click on any jpg image and select 'open with' the 'choose another app' and navigate to the CC2018 .exe file, it still opens in PS  CS5.


      I thought I had won when I discovered that Bridge CC2018 preferences has a 'File Associations' panel.  I dutifully changed every single CS5 association to CC2018 (by selecting its .exe file) but it's made no difference - the files still open in CS5.  If Photoshop CC2018 is open, the files will open in the new program, however, and fortunately clicking on a jpg from within Bridge does also open the file in PS 2018.


      I realise others have had similar problems, and I've found an earlier post which gives a registry hack to solve the problem.  Only thing is, the registry entry the hack uses - HKEY_CURRENT_USER\Software\Classes\Applications\Photoshop.exe\shell\open\command - isn't valid for my PC. The only thing listed under Classes\Applications is Opera.exe. There isn't a single other program listed there.


      Does anyone have any suggestions re this? Is there another registry entry I can edit?

      Under HKEY_CURRENT_USER\Software\Adobe\Photoshop\12.0 the path for CS5 is:

      C:\Users\dave\AppData\Roaming\Adobe\Adobe Photoshop CS5\Adobe Photoshop CS5 Settings\


      Under HKEY_CURRENT_USER\Software\Adobe\Photoshop\120.0 the path for CC2018 is:

      C:\Users\dave\AppData\Roaming\Adobe\Adobe Photoshop CC 2018\Adobe Photoshop CC 2018 Settings\.


      Hair being torn out by the minute...

        • 1. Re: Bizarre file association problems - Win 10, CC2018 and CS5
          Chuck Uebele Adobe Community Professional & MVP

          Not sure if this will help, but you should always install the earlier version of PS first. You might want to uninstall both versions and reinstall cs5 first.

          • 2. Re: Bizarre file association problems - Win 10, CC2018 and CS5
            JJMack Most Valuable Participant

            On My Window 10 system I now only have 3 creative cloud versions of Photoshop installed. CS6, CC 2014 and CC 2018.  I have set my Windows registry Photoshop.exe key commands edit and open to start  CC 2014 my preferred version of Photoshop.


            Using Windows Settings Default apps (Choose default apps by file type). I see I have set .jpg to be associated with CC 2014.  I see I have not set my CR2 raw files to be associated with CC 2014 its associated with Photos.  This has never bothered me for I always open CR2 files from Photoshop or Bridge and they use ACR to  convert my RAW files into RGB images.  However I had no problem changing  .CR2 to be Associated with CC 2014.  Now when I open a .cr2 file from file explorer if Photoshop is not running  CC 2014 will start and it will use ACR to convert the RAW file to an RGB image.  If Photoshop is running on windows CS6, CC 2014 or CC 2018 it will use ACR to convert the .cr2 file into an rgb document.



            • 3. Re: Bizarre file association problems - Win 10, CC2018 and CS5
              Dave Addo Level 1

              Problem has been solved by uninstalling then reinstalling CS2018.  All file formats are now pointing to this program, so I'm now a happy camper.