Bug Reports

Hello Adobe Support Team,I am experiencing an issue with GPU acceleration in Adobe Camera Raw on my HONOR MagicBook Pro 16 (2026) laptop.System configuration: Laptop: HONOR MagicBook Pro 16 (2026) Processor: Intel Core Ultra 5 338H GPU: Intel Arc B370 (Panther Lake) Operating system: Windows 11 26H2, OS build 26300.9711 Photoshop version: 27.11.0 Camera Raw version: 18.7 (18.7x2743) RAM: 32 GB Camera Raw detects the Intel Arc B370 GPU and successfully reads its hardware specifications. However, GPU initialization fails with the following errors:DXGI_ERROR_DEVICE_REMOVEDDXGI_ERROR_DRIVER_INTERNAL_ERRORCreateCommandQueue failedAfter this failure, Camera Raw reports that no compatible GPUs are available and automatically disables GPU acceleration. The GPU settings become unavailable, and I cannot switch to Custom mode.I have tested two Intel graphics driver versions: 32.0.101.9175 32.0.101.8509 The issue persists with both driver versions.GPU acceleration is enabled and work

When creating a new brush mask in ACR, if the brush is resized in between changing a slider and making the first brush stroke, the slider resets to zero.  For example- Press K to create a new brush mask- Set the highlights slider to -100- Right click on the mouse to resize brush- The highlights slider resets to zeroIf you don’t change the brush size, the mask works as intended.  This seems to have started happening since version 18.3.1 

Recurring Camera Raw GPU Acceleration Error – NVIDIA GTX 1050 Ti – Windows 10Hello Adobe Support Team,I am experiencing a recurring GPU acceleration issue in Adobe Camera Raw.My PC specifications: Windows 10 Home 22H2 AMD Ryzen 7 2700X NVIDIA GTX 1050 Ti 4GB 32GB RAM NVIDIA Driver 582.66 Camera Raw 18.4 / 18.7 Troubleshooting steps I have already tried: Updated the NVIDIA graphics driver. Reset Camera Raw GPU support. Renamed the Camera Raw GPU configuration file to allow it to regenerate. Tested GPU processing and Open & Save settings. Restarted Photoshop and Windows multiple times. Tested Photoshop 27.10 and Photoshop 26.6. Installed Camera Raw 18.4 to check whether an older version would solve the issue. Important observation:Camera Raw 18.4 worked perfectly for approximately one week after installation. However, the same GPU acceleration error returned.The issue also occurs in both Photoshop 26.6 and 27.10.The GPU is detected by Windows, but Camera Raw dis

the above message comes up followed by :-due to a run-time error, GPU acceleration has been disabled for the remainder of session.

Automatic person detection for removing distractions option does not work.There is a person clearly visible in the foreground of the photo.

there is no way to tell the tool where the reflection needing to be removed is, it doesn’t change the image at all, and there is no effective way to submit feedback, the whole thing amounts to hollow slop

Turns out this (over a year old) issue is an upstream bug in camera raw.To reproduce, load any photo with distortion corrections enabled and move a linear gradient around. The stronger the distortion correction, the larger the effect. Might be resolution dependent as well, as I've only tested with photos from an a7R V and a7R VI. So please test with a high resolution camera and something like a fisheye lens correction profile before downplaying the issue by claiming "the effect is less than 1°" or something. With some correction profiles, I've noticed rotations close to 90°. I won't bother putting down any platform information here as I've observed this issue on half a dozen devices on every OS, including the web client.

The option “match exposure by camera settings & light” in Camera Raw is disabled when using nef files. Only “match exposure by camera settings” is enabled

my photoshop was Chinese interface, When I use ACR 18.0--ACR18.7 , I open the raw pictrue. The first time was Chinese interface,but the second or third times always switches to English interface, I must close photoshop,and open photoshop again, open a new pictrue, ACR18 was chinese. but alway switches to English interface. Many Chinese users have encountered the same problem as meI don't know why? please help me ,thanksmy computer was windows 10 , Photoshop 2026

This is the image after I denoised having previously cleaned out the reflection totally with the reflection tool.  I am shooting raw with a Nikon Z8

Opened image (TIFF or DNG) via LightRoom ClassicDuplicated layerOpened new layer in ACRSelected Remove toolSelected remove PeopleTwo people selected, one of which I did not want to removeCursor changed to Zoom toolUnable to exit that Zoom mode to select the person I did not want to removePressing H to change to Hand tool did not helpSeems there is no way to deselect the selected peopleTried restarting PS; rebooting computer..  no joy in MudvilleWhat _did_ work was from the main PS window, was to select the distracting person via the lasso tool and use Gen AI to remove with the prompt "remove person".####Mac OS Tahoe 26.2Mac Studio M2 MaxPS v27.11ACR v18.7

I am using Camera RAW v16.4 and LrC v13.4. A recent RAW photo had a particular item of purple colour but it shows as more like blue when imported to LrC - when using 'Camera Standard' profile. I Have not observed other colours to be quite so obviously different. Shown below, camera faithful, camera standard, and the out-of-camera JPG : Observe the centre image (camera standard profile) is more blue'ish than purple.   Looking at the Adobe profiles and all the camera profiles shows that only camera standard, portrait and landscape have this colour shift - I also included the Canon G9x standard (tweaked to show for the G7x), as I understand this uses the same sensor, it too resembles the JPG colour much better: Whilst I can certainly work around this, I thought I'd report the issue as I expected camera matching profiles to be close to the out-of-camera JPG, as it appears to be with the G9 profile.

Adobe Camera Raw 18.5This problem occurs on both Nikon D850 and D500 raw files which have been opened in ACR by right clicking on the files in the Mac finder and selecting open in photoshop.  The files have not been previously processed in any way.When I right click on the image in Camera Raw, the option for “Show Autofocus Points” is greyed out and not responsive.  I have repeated this with multiple files from both cameras taken using different autofocus modes.I have checked two of the files (one D500, and one D850) in Raw Digger to examine the EXIF data, and both show values for “Focus Position” (0x11 on a D500 file) and “AF Points in Focus” (E9 on the same file), so this metadata information should be available to Camera Raw.Are these cameras supposed to be supported by this feature?  Adobe’s documentation says nothing about what cameras are supported.I watched a video today showing someone using this feature (although with a different camera’s files), so I know that I was looking a

After upgrading to 15.4, several, but not all, of my hdr pano photos report the above error, along with “The file appears to be unsupported or damaged”. Restored these “damaged” photos from versioned backup on Backblaze from versions several months old and still received the error. Reverted to 15.3.1 and these files no-longer show the error. So, 15.4-->Broken; 15.3.1-->Working

Hi, using latest Lightroom Classic on MacOS 26. I have found that sometimes LRC gets confused about the exposure. I have a two image example where the images are exposed exactly the same but the resulting pano is messed up. One half of the resulting pano is exposed correctly, the other half is light. I've only seen this in iPhone RAW HDR images. The one I kept was from Apple Camera but I've also seen it using Project Indigo camera. On the Indigo forum, another person was complaining about pano issues (black bars ending up in panos). I've also seen this issue and have example RAW images.https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-discussions/p-introducing-the-project-indigo-camera-app/m-p/15440106/page/21#M106426I tried attaching example files but that failed. How can I get images to the Lightroom team?   [moved from bugs to discussions according to the community rules - Mod.]

Using an R6III with en EF 11-24 F4L via an EF to RF adapter, and I am noticing significant barrel distortion at the wide end that the profile in Adobe Camera Raw isn’t taking out.The strange thing is that I used the exact same lens and adapter on my R6 mark 1, using the same lens profile in ACR and it corrects the distortion well.Anyone have any insights?I can correct manually but it gets tedious (shooting real estate)

Recent Camera RAW update… when I access the Geometry panel  Shift T, the default is collapsed, I always have to click it to expand. Used to not be this way… any fix?  

Hello Adobe Team,In a series of identical tripod shots, a manually created mask does not synchronize correctly.When I copy the mask to a single image, it is positioned correctly. When I synchronize it to multiple images simultaneously, the mask appears shifted—even though the camera, subject, framing, and image dimensions remain unchanged. Is this a known issue?Thanks - Michael

This is a pretty simple bug that was introduced when "Raw Details" was changed into a button instead of creating a new DNG, it removed the ability to apply raw details to several raw files then merge them to a Panorama. You used to be able to do this with separate DNGs, but now this ability has been removed, please put it back!!!   I have tried this many different ways, applying Raw Details to the raw files, when merged to Panorama it's undone and turned off permanently (visible when comparing the raw and merged Pano side by side). I tried applying raw details, then converting to DNG, then merging to panorama, same effect. The wonderful algorithm of Raw Details is completely wiped out when the image is merged to a Panorama, it used to work when it made a separate DNG, PLEASE FIX this newly introduced bug.   Have not tried but likely the same with HDR merging!  

See Full Report.txt

Just find out, that DENOISE dont work for RAW files from Ricoh GRIIIx (DNGs)

Lightroom Classic version: 15.4.1 [ 202606201310-b9f148a4 ] Operating system: Mac OS 26 Version: 26.5.2 [25F84] Computer: Mac Studio M4 Max Camera: Canon R5 Mark III noticed that in some photos enabling Denoise results in a checkeboard-like pattern, there are very distinct tiles. This is shown in the following photo:Checker BoardI exported a catalog with the above photo including the edit history that demonstrates the issue. I couldn’t attach it as it’s ~100MB, instead I uploaded it to google drive: Exported Catalog with the above photo

If the working profile in both Photoshop and ACR are the same, the skin tones match the proper hue when a photoshop image is brought into ACR.  However, the skin tone line on the new vector scope is not moving to adjust for the fact that the Hue value associated with skin tone varies between color spaces.  The skin tone line seems to be set at a hue of about 18 regardless of what the working export color space is, so it gives incorrect skin tones unless you are exporting to Rec709. space.Open an image in photoshop with skin and convert it to Rec709 color space.In the settings panel ensure that ACR working space is also Rec 709. Open the base layer in ACR and select the skin of the subject.  The skin tones will properly align with the skin tone line on the new vector scope, at a hue of about 18-19 degrees. Now, cancel in ACR and use the Edit menu to convert the image to ProPhoto color space.  In the settings panel, change the settings to ensure that ACR is also exporting to the ProPhoto

In some photos, applying the Adaptive Color Profile produces weird, blotchy artifacts in brighter areas, particularly in a sky where there is strong contrast between the bright and dark areas, like a sunrise or sunset. In the attached video, the photo in Develop begins with Adobe Color as the Profile, adjusting the Highlights slider brightens and darkens the sky as expected. Changing the Profile to Adaptive Color produces noticeable, blotchy artifacts in the sky. Adjusting the Highlights slider dramatically changes these blotchy artifacts. Adjusting the Profile Amount slider also changes these artifacts. Enabling HDR mode makes these blotches disappear; adjusting the Highlights moves a prominent bright band up and down in the sky, but the blotches do not appear. I reported this in another photo a year ago, but the problem remains. It means that for some photos, Adaptive Color is quite useless. Has anyone else seen this problem when using the Adaptive Color Profile?