Bug Reports

Hello,I started using the new photoshop version 27.0 and noticed some really annoying problems while using the "subject select (SS)" and "remove background(RB)" features from the taskbar, in some instances it just doesn't recognize images at all, images that it had no problem working on the previous version.At first I thought this was a problem after i rasterized the image, as soon as I imported and used SS or RB on the smart object it worked as expected. But if i rasterized the same image and then tried to use the same features, photoshop would select the outer bounds of the image imported.But after trying again on both smart objects and rasterized images i realized that the same thing happened with both types of layers.I also thought this might have been a problem with images generated with firefly, but again, i had the same problem with photos and other files that were not ai generated. Here is an example of the weird selection it made on non-generated image as a smart object l

When I try to use the function “ Select > Subject” on v26, the software will select the object from the background on the image with out any issues.however the exact same function does not work on v27 and pop up a warning saying on subject can be found no matter using the AI function or the basic one to achieve the same goal.

I updated to Photoshop 27.10.0 and now when I click “generative fill” in the contextual taskbar, the cursor to type the prompt no longer appears automatically in the box for the prompt. So when I start typing, it cycles through the toolbar keyboard shortcuts instead. This is a glitch that did not exist in previous versions, I could always immediately start typing my prompt after clicking the generative fill button in the contextual taskbar.

I have been using the remove tool for general clean up for months now. But since the update for PS CC 2026 it is borderline unusuable. I haven’t read much about it on here, so I though I’d ask if this is an actual but or a simple case of “ens***ification. Ever since the 2026 update I can no longer replace details in snow or sand textures for example because the resulting textures either rendered by the AI or in Photoshop itself do no longer look like the neighbouring textures but patchy, blurry and simply unusable. It doesn’t matter whether I set AI to auto, on or off. Results look like from 2010’s patch tool basically, neither texture, nor color or luminosity match the general area. On top of that for about two months now the tool has become incredibly slow for whatever reason and since I do have a 300mbit fiber conection I doubt it is the internet needed for the transfer of the image data as has been hinted at here on the forums recently.I then tried to simply mark the areas I would

After moving the zero point to a different place, Photoshop continues to create a New Guide as if the zero point had not changed. Why?

since today morning i tried may times to open photoshop on my laptop, but it is not opening.

ACR 18.6  / Mac Studio Tahoe 26.7Trim and generative expand applied to image. Additional edits caused them to vanish.Edits such as profile change and glow each reversed the Crop & Expand edits.

After upgrading to 27.10 the crop with Generative Expand co longer works. If I select a crop and go beyond the image, even tough I have Generative Expand selected on the toolabar the new area is rendered transparent.  If I then subsequently just select the area ans use Generative Fill, that works - but I shouldnt have to !!!  Can we expact a fix anytime soon ??? I’ put a little pic below - I would post a little video but not sure how to upload it to hereBTW can we please have the ‘check mark’ and  the ‘discard’ icons back on the crop toolbar - its a right pain putting down the mouse/stylus and having to press ENTER or ESC when before we could just do s imple click to confirm or discard. 

Since updating to the latest version of Photoshop and Camera Raw, the "Image Processor" batch script initiated in Bridge stops working when processing TIFF files with previously applied parameters in ACR. Instead of smooth batch processing in the background, the process freezes, and Adobe Camera Raw either forces an interactive window or interprets specific layer metadata/color profile information in the TIFF files as a required edit prompt.This completely disrupts established, automated, professional workflows. The exact same TIFF files processed without any issues in previous versions of Photoshop/ACR, and reverting to the older version immediately resolves the issue. This indicates a regression in how the latest ACR engine handles raster files during batch operations.Product and Version: Photoshop 27.10 / Camera Raw (latest version)Operating System: Windows 11 ProExpected Result: The image processor should sequentially batch convert TIFF files in the background, without launching th

when trying to open a picture the icons of the pictures are not showing the thumbnail in the open file window

Al abrir Photoshop, al crear un documento nuevo, la ventana de "Nuevo documento" tarda, se comporta de forma extraña e incluso llega a abrir después de la interfaz antigua. y hay parpadeos de pantalla al trabajar dentro de interfaz.

Photoshop crashes on resume from sleep when network connectivity is enabledSummaryPhotoshop consistently/regularly crashes when Windows 11 resumes from sleep, but only when network connectivity is enabled.The crash occurs even before logging back into Windows in some cases. Photoshop is otherwise stable during normal use and does not crash during ordinary network activity.I have traced a crash dump with WinDbg. The crash is a C++ exception originating in Photoshop's bundled msvcp140.dll, and the call stack shows Photoshop interacting with the Windows Network List Manager (netprofm) through COM/RPC during a network connectivity-change notification.This strongly suggests a Photoshop bug in handling Windows network interface/connectivity notifications during or immediately after resume.ReproductionStart Windows 11 normally with Photoshop running. Put the PC to sleep. Wake the PC. Photoshop crashes during/after the network interfaces transition back to their connected state.The behaviour i

When using the “Remove” tool in Photoshop 2026 (27.8.0) on Windows laptop I receive “Tool is not responding - check internet and try again later” error.  Internet is perfectly fine however it does this about 10mins and then works for a bit.

Adobe Photoshop 27.10.0 on Mac OS 14.6.1When adjusting a Color Balance (or other) Adjustment Layer by dragging the handles in the Properties Panel it incorrectly disregards the effect of a Curves Layer above that is Clipping Masked to a 0% Fill Layer. This does not happen when the Color Balance Layer is edited by entering numbers or when the Curves Layer has a Layer Mask instead of being Clipping Masked. Hiding and revealing the Color Balance Layer corrects the display.Steps to recreate: • create a Color Balance Adjustment Layer with some changes• create a Layer with pixels (plain, Solid Color, Smart Object, …) and set it to 0% Fill and uncheck »Blend Clipped Layers as Group«• create a Curves Adjustment Layer with some changes• Clipping Mask the Curves Layer to the 0%-Fill-Layer• drag one of the handles of the Color Balance Layer in the Properties PanelExpected result: The combination of adjustments should be displayed correctly. Actual result: The Curves Layer’s effect is not honored.

Hey everyone,Up until recently, I was using Photoshop 27.8 (Mac 26.5.1) and everything worked perfectly fine.The newer Generative Fill and Expand model produces textures that are way too smooth. I’d even call them blurry. And yes, I’m aware of the 1024×1024 px limitation, but this happens even with 100×100 px selection.Because of that, I’ve been using the old Firefly 1 model from 2023, which, unlike the newer model, works really well for my use case. It handles textures amazingly well. I mainly use it for removing distractions: I select the unwanted object, leave the prompt empty, hit Generate, and Firefly 1 understands perfectly well that the selected area should be removed.However, something seems to have changed starting with version 27.9.If I leave the prompt empty now, Firefly 1 starts generating completely random objects instead of simply filling/removing the selected area. For example, I had a white T-shirt with some red text on it that I wanted to remove. I selected the text, l

Ever since the latest update of Photoshop (version 27.10), the content-aware fill tool has been rendered useless. When using this tool, it will bug out when i straighten an image out or will fail when cropping an image. When I go to cancel the content-aware fill load screen, it will not cancel and I have to force quit out of Photoshop. Because of this issue, my usual editing speed has been significantly slowed down. I rely on this tool heavily for my job and without it working correctly, it is causing delays for complete projects and unnecessary stress. 

The preview function in the Image Size dialog is seemingly incapable of dealing with complex large resolution files.For example, I am working a 10,000x6,000pixel image, with about 100 layers, there is a mix of Smart Objects (with and without filters applied, both linked and embedded), pixel layers, and adjustment layers. If I attempt to resize the document, by any amount, the Preparing to Build Preview comes up, then I instantly get a spinning beach ball, no chance to even cancel the preview. Out of curiosity, I have let it run for up to an hour, never finishes. Only solution is to force quit the app.This has happened across multiple versions of Photoshop on multiple computers going back years.If there is no fix, please let me disable the preview, in 30 years of using this app, I have never once needed a preview of how my image is going to re-size.System info and a screen shot of the image size dialog doing nothing attached. -Sam  

Issue summary:  Photoshop 2026 hangs when I select any of the buttons in the print dialog Product and version: Photoshop 27.10.0 20260824.r.26 9d9635d  arm64 (final, Release) and Photoshop Beta 27.11.0 20260909.m.3669 481f204  arm64 (beta, Internal) Operating system: MacOS Tahoe 26.6.2 Steps to reproduce: 1. Open an image in PS 2. Select File>Print. Print dialog displays 3. Select Cancel, Done, or Print buttons Expected result: Print workflow would continue Actual result: Have to force quit the app to get out of PS Attachments (optional): Screenshots, screen recordings, sample files, or short videos that show the problem.

I have tried just about everything to get this to work. I am not sure when exactly it stopped working but I am guessing during one of the updates for some reason that got screwed up. It works on all my home computers and my work laptop but not my desktop.    I have unistalled and reinstalled, tried less up to date versions, turned on and off the screen recording for photoshop in my settings, restarted my computer, none of it has solved the problem. This is so frustrating and I haven't found anyone else having this issue besides people that forget to turn the screen recording button as I mentioned.   Also I should mention with all my other Adobe products that fuction works just fine. If I am missing something here please let me know because I need a solution to this madness.

# Generative Remove runs on the CPU instead of the GPU since version 27.9.1**Issue summary**Since updating to Photoshop 27.9.1, the Remove tool in Generative mode loads about 6 GB of data into the graphics card memory, then performs the actual work on the processor instead of the graphics card. The graphics card stays at idle power for the whole operation. A removal that used to complete quickly now takes several minutes.**Product and version**Photoshop desktop version 27.9.1 (build 20260803.r.1 65900e1)**Last version where it worked correctly**Photoshop 27.8.0 (build 20260610.r.13 4081857). The problem started immediately after updating on 6 August 2026.**Operating system**Windows 11 Pro, version 26200**Hardware**Graphics card: NVIDIA RTX PRO 4000 Blackwell, 24 GB, driver 32.0.15.9672Processor: Intel i9-13900K (32 logical cores)Memory: 128 GB**Steps to reproduce**1. Open any photo.2. Select the Remove tool.3. In the options bar, make sure the generative mode is turned on.4. Paint over

Ich habe tagelang gesucht und am Ende etwas gefunden, das ich hieraufschreibe, um euch vielleicht viel Zeit, Stress und ärger zu ersparen.  ## 1. Das Symptom Lightroom Classic und Photoshop starten ganz normal, aber die Grafikkartewird nicht genutzt. In den Einstellungen (Bearbeiten → Voreinstellungen → Camera Raw → Leistung) steht, dass keine GPU verfügbar ist.Entrauschen dauert länger als es sollte, die KI-Funktionen sind lahm. Dabei ist der Rechner völlig in Ordnung: Spiele laufen flüssig, der Browsernutzt die Grafikkarte, alles andere funktioniert. Nur Adobe nicht. Bei mir: Notebook mit NVIDIA RTX 4070 und Intel-Grafik, Windows 11, 16GB Ram. Also kein High-End Gerät aber mehr als fähig für die Grafikbeschleunigung... ## 2. Alle Standardempfehlungen — ohne jede Wirkung Ich habe wirklich alles durchprobiert, was man dazu im Netz findet: - GPU-Einstellungen in Camera Raw zurückgesetzt- Den GPU-Ordner von Camera Raw gelöscht (mehrfach)- Voreinstellungen von Lightroom und Photoshop zurü

Photoshop 2025 bug: auto numbering in lists using text tool causes file corruptionI have identified a bug. I noticed that a new feature was when you use the text tool and type1. text 2. text 3. text this triggers auto numbering.  Well it took me four hours to figure out this is what was currupting my files and it is very repeatable When you try to reopen the file, it says a problem wont allow it.   The auto numbering in text tool had been working ok without file corruption until very recently.   If I paste a list in text tool with numbers alread in place, it corrupts the file if I start inserting numbers before a list in the text tool, it corrupts   my work around is this: I type or paste this: text text text   to create a numbered list i do this:   t1. ext t2. ext t3. ext   than i backspace to remove the first letter to create my desire:   1. text 2. text 3. test   the auto numbering feature either needs to be removed or fixed   under

Hi everyone, I would like to report this explicitly as a bug report, and I kindly ask that it not be converted into a question. The behavior is reproducible in my setup and, from my point of view, affects WinTab support in Photoshop 27.6. After updating to Photoshop 27.6, WinTab still no longer works reliably. I need WinTab because pen input is much smoother and more precise with it, especially when working with sliders, numeric input fields, and Photoshop UI controls in general. Reproducible behavior With WinTab enabled, Photoshop 27.6 freezes as soon as I move the brush size slider. Important detail:The freeze happens even when I move the slider with the mouse, not with the Wacom pen.To me, this strongly suggests that this is not simply a Wacom pen issue, but a problem in Photoshop’s WinTab handling itself. Test results in Photoshop 27.6 WinTab enabledopened a new test document selected the Brush tool moved the brush size slider using only the mouse Photoshop freezes immediately afte

Is there a way to actually get rid of the Layer Cleanup panel menu item?I have it set to be not visible in settings, but it’s not working.thanks

When using Adobe Photoshop 2026 any Version of 27.x up through the latest 27.10 we cannot open .png files that were created by our engineers using Creo 8. As soon as you open them Photoshop crashes to the desktop.  We have hundreds of these files saved on a network file share from the past 6 or 7 years. If we open the file in another tool like MS Paint and save it as a .tiff or other file type it will open in the new version.  If we save the same file as a .png file inside photoshop 2026 it will then work fine moving forward.  We won’t be able to upgrade to a newer version of Creo and Windchill yet so we either have to open all of these files in another tool and resave them or we can open them in Photoshop 2025 Version 26.XX with no issues.  We have ruled out all graphics card issues by disabling the GPU and using onboard graphics, also disabling it in photoshop as well.  We checked all the system files and C++ redistributable files and repaired all of that and ran a full system filesc