In PS 2020 it looks like this: ... View more

I have had two versions of PSE on my computer at the same time in the past, but not the two you have so can't be sure what happens; however, I would expect the PSE Organizer database upgrade, if there is one, to be one way, from PSE9 to PSE2020.  Meaning that changes you make in Organizer 2020 might not be visible in PSE9 Organizer, but I also never use Organizer so am least familiar with how things work during an upgrade.   I would upgrade to PSE 2020 with the intention for using that version from now on, rather than bounce bewteen the two versions for old photos vs new photos.     It's possible that PSE 2020 will be 64-bit while your PSE9 is 32-bit (is it?) and as such plug-ins won't necessarily work on both versions.  Plug-ins are typically 32-bit or 64-bit with older ones not having 64-bit rewrites. ... View more

I would leave the old PSE until after you have the new PSE 2020 running to your liking.  You might try the trial of it, first, to make sure it is compatible with your hardware. ... View more

Unless your computer is too old, why not:   Upgrade your Elements to 2020 for $100 (US) on sale for $70?  https://www.adobe.com/products/photoshop-elements.html    or Buy a subscription to PS and LR for $120/yr (US)?  https://www.adobe.com/creativecloud/plans.html   I have the four-year-old PSE14 installed and I can see the version of Camera Raw it has by doing Help / About Plug-in / Camera Raw.  If that shows something older than 12.1 then you should be ok, as the ACR 12.1 install didn't affect Elements.   As Jim says, to work with your camera's raw data, besides updating to the current version of PSE, would be to use the current version of the DNG Converter to create DNGs from your camera's CR2s and then those DNGs but not the CR2s will open in your older PSE's ACR.   Download links for the latest DNG Converter can be found at the bottom of this page.  It converts a folder at a time: https://supportdownloads.adobe.com/support/downloads/new.jsp ... View more

CS6 is compatible with ACR 9.1.1.   You need at least ACR 8.7 for your camera (not 7.1): https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-supported-cameras.html   However, Adobe has recently removed most all downloads for these older versions, so the DNGs are the best you can do, and the graininess you are seeing with the DNGs is the same as for native raws from the camera, anyway.    Does the camera natively produce DNGs or are you using a DNG Converter?   You can get the latest DNG Converter, here, but the ACR 9.1.1 link does not work, anymore: https://blogs.adobe.com/lightroomjournal/2015/07/update-to-camera-support-policy-in-cs6.html ... View more

Why are there two different screenshots, the first and the last in the original message, showing Bridge / Preferences / Camera Raw... ?   Between those two screenshots, the versions of ACR are different and the number of expanded folders under My PC is different, suggesting two different computers.   What is the GLDriverDate in PS / Help / System Information: ... View more

The obvious difference between the two is the lack of magenta on the OLD one vs NEW, both in the magenta fringing along the building-sky edge and overall.   So the OLD one is created on the other systems and the OLD smart object was applied to the merged layer, while the NEW one is a smart-object starting with the same merged layer but created on your system with ACR12, and what we see crops is the difference between you turning your new smart-object layer on and off?   Does this happen with any JPG with a simple smart-object ACR filter applied, perhaps with the default settings both in the original SO on the other systems and the new SO you create?   Obvious questions would be: 1) Are there differences between the default ACR settings on the old system and your system? 2) Did ACR 12 introduce some new setting and perhaps a new process-version that is the reason things look different? 3) Are there differences in the monitor calibration between their systems and yours that could account for the difference?   I think you've said or suggested this in the intial post, but it is your idea that when you had ACR 11 on your system the images looked the same between their systems and yours, so either ACR 12, itself, or the process of upgrading from ACR 11 ot ACR 12 changed something on your system that now makes things more magenta, and perhaps other differences?   ... View more

Are there ANY images you can share that this happens to?   Just to understand, you are saying that a smart object created from a raw using ACR11 look markedly different when the smart object is opened with ACR12 is installed?   Or are you saying that starting with the original raw, a smart object created with ACR11 looks different than another smart object created using ACR12?   Or are you just saying that a preset created with ACR11 looks different when that same preset is applied to the same raw using ACR12, and the issue has nothing to do with the fact it's a smart object?   Are your tests on the same computer? ... View more

If your images have been corrupted by using Nikon software wtih the, there is a utility that can reverse the very specific corruption that can happen.  Be sure to use it on a copy of the imgaes, first, in case they are corrupted beyond repair: https://owl.phy.queensu.ca/~phil/exiftool/fix_corrupted_nef.html ... View more

Can you post one of these NEFs that only works on some of your computers? With Nikon, unsupported or corrupt usually means they have been touched by old Nikon software that corrupts them slightly and Adobe software refuses to read them, but it would be all instances of PS and CR and LR, not just the newest on one computer. ... View more

All raw files you view in Adobe products, regardless of the version of Camera Raw, or the camera model, have an Adobe rendering according to the Adobe factory default or a default you may have set, which will be different than the camera rendering, sometimes not much difference, sometimes quite a bit of difference.  FastStone will show you the camera-embedded JPG which is also what you see on the camera's preview display and you will only see this momentarily in Adobe products before the Adobe rendering is computed and a preview created.   When you say there is a preset being applied, is that another way of saying Adobe rendering is different than camera rendering--which it will always be to some degree, or do you mean that there are non-zero settings in the Basic Toning tab, the area where you adjust Brightness and Shadows, and Clarity and such?    In either case, you can set a new default by opening a brand new image that you hvaen't made any purposeful adjustments to, then make only the adjustments you want to have all photos from that camera to start with.  Usually you set things like enabling lens profile corrections, a default level of noise reduction, and the color profile you want to start each photo with: Adobe Color, Adobe Neutral, Camera Neutral, etc, depending on the specific list your camera has.  Once you have made the handful of adjustments that you'd like every photo to start with (from that camera), press the Alt or Opt key and a button will set Set Defaults... and you click that to save the current settings as the new default for new photos you open for the first time.   There is a problem with the newest Sony model in that Adobe cannot decode some of the information in the raw file and has to guess how to render the files.  What specific Sony model camera are you working with? ... View more

Can you paste a screenshot of the error message you're seeing that includes the Windows version number?   I have Win 10.1903 and Enhance Details works ok, but only on non-demosaicked raw images.   Besides having at least Win 10.1809, your GPU also has to support the Enhance Details code.   For reference, my graphics card is an nVidia GeForce GTX 1060 3GB that I got a year or two ago when LR didn't do everything with the GPU I wanted it to. ... View more

Also, I usually don't have to search for my password when CC applies updates because it's running all the time and just does it when it sees an update, which is typically outsdie the time I'm using Photoshop.   Are you using Photoshop Elements and it only checks for updates when you start it up, which could be annoying, if you are prevented from doing work until it completes. ... View more

The metadata storage in a JPG is more standard than the metadata storage in a RAW or MOV, so LR will use the JPG for the source of the metadata, sometimes. Not sure which takes precedence if there is both a JPG and an XMP file. ... View more

The Camera Raw plug-in can be used to make adjustments to JPGs and othe non-raw files, so I doubt Adobe is going to make it possible to shut off updates, since they contain bug fixes and sometimes new features, that can be used with non-raw images, too. ... View more

It's hard to say what might have happened, but set your PS RGB workspace profile to ProPhotoRGB and enable the profile-mismatch checkboxes in PS's Color Settings and you'll at least know right away once something changes.   Also either have the Color Management Policies for RGB set to Preserve Embedded Profile or Convert to Working RGB, not OFF. Also make sure you're embedding the color profile in what you save, and convert to sRGB prior to saving a copy if the output is to be viewed by non-colorspace-aware application or on the internet:   ... View more

Look at the last part of the filenames, the extension. If it says JPG then they aren't raw. If it says CR2 or NEF or AR2 or DNG or something then they are raw. ... View more

The camera settings are usually Adobe RGB and sRGB in my experience.  That colorspace setting is used when the camera writes out the JPG, not the colorspace when a raw file is produced, which is specific to the camera and something the camera profiles are created to handle.    ProPhotoRGB can be the working colorspace in a color-managed application like Photoshop or Camera Raw and either of those applications will convert the image data from its original colorspace: sRGB, AdobeRGB, raw-specific, to the working colorspace of the application.  It is a good idea to also use a bit-depth of 16-bits, rather than 8-bits when using ProPhotoRGB as the working colorspace because it's a larger bag of colors so having more total color numbers is better.     If you are saving an 8-bit format (like JPG) out of the color-managed application you probably want to convert the colorspace to sRGB then 8-bits, then save to the alternate format.  But if you are saving your work as a work-in-progress then keep it as a 16-bit, ProPhotoRGB image saved as TIF or PSD.   As far as printing a ProPhotoRGB image, through a combination of settings in Photoshop and the printer driver, the combination of PS and the printer should be covnerting from the working colorspace of ProPhotoRGB to the printer's colorspace.  Most printers actually expect sRGB or the printer's colorspace, which you can sometimes download a profile for.  ... View more

Sounds like you're opening a non-raw image, like a JPG.  Did you switch off RAW in the camera, or is it an HDR or panorama where the camera might not have a RAW option, just JPG even if the camera is still set to produce RAWs normally? ... View more

The speed trailing off or things failing entirely for more images sounds like a resource issue on your computer.  It could be too many programs open, an almost-full boot disk, or a bad video driver, among other things.  Not having Photoshop, itself, open, when you're using just Bridge and ACR might be something to try.  There are use-graphics-processor settings for both ACR and Photoshop, independent of each other, so make sure you're doing the one for ACR.  If you have PS open at the same time, it's possible PS's GPU setting can also affect how things work if they're both using the graphics processor and maybe it doesn't have enough resources for both ACR and PS at the same time. Hopefully Adobe support got you going or at least gave you some answers. ... View more

Adobe never says when something will be included; however, most every release Adobe adds a dozen or two lens profiles to LR/ACR, so be patient.  If it's a new lens for an important camera from a mainstream brand, it'd likely be a priority.  This particular lens is $3000 so they probably would need to acquire a loaner from Canon as opposed to just buying one. ... View more

Does it work with less images, like 2?  In other words is the issue related to the amount of work being done, or something is just hanging at the end? Does toggling the User Graphics Processor performance option in ACR make any difference? If the GPU is being used to compute things, maybe there is an issue with your current video driver, and an update might change things. ... View more

What is the purpose of uploading a DNG that is created from a JPG with LR Develop settings applied? Does DropBox show a preview ok if you export a DNG from a raw image? ... View more

Setting the compatibility level to ACR 5.4 is AFTER you update your PSE to use ACR 5.6, not before.  You should still do this. ... View more

You might also try updating your PSE 6.0 to PSE 6.0.1 from the links, here, if you haven't already; Adobe Photoshop 6.0.1 update available: Digital Photography Review ... View more

Please update your PSE 6.0 with ACR 5.6 from this link, then see if the 11.3 converted files open correctly: Adobe - Photoshop Elements : For Windows : Camera Raw 5.6 update If not, then try your DNG Conversion in the DNGC 11.3 using a compatibility level of CR 5.4 or later instead of 4.1 or later. ... View more

You can drag-and-drop photos on the main Loupe area of LR Library (but not Develop) to import them, maybe onto the grid, too, just not the side areas, although sometimes there is Windows security that prevents it and I'm not sure exactly what changes.  I have Windows 10 1809 and LR 8.3, so I can't speak to the precise behavior of the much older LR 3.6 and Windows 8.1. ... View more

The BSOD also shows an associated executable such as a .SYS or .DLL that could give some hint about the issue. JSM’s suggestion about testing memory is a good one. Updating graphics drivers could be another but the multiplicity of errors suggests some sort of hardware issue where memory is hardware. Hopefully that’s it. These sorts of errors come from drivers, not Lightroom, itself, so LR is merely exercising code and hardware that other programs haven’t. ... View more