Bug Reports

포토샵 25.9 or 25.91 버전으로 자동 업데이트 후프로그램 오류로 인하여 "제목 없음-1.psd"을(를) 다른 이름으로 저장할 수 없습니다.라는 창이 떴습니다. 이 후 하위버전으로 다시 설치하여 사용중인데 이 버그는 왜 생겼던 건지 알고싶습니다. 그리고 추가로 셋팅되었던(색상,그라데이션,단축키 등등)도 유지버튼을 클릭하고 설치해도 사라졌다는데 그것 또한 다음 업데이트 전에 유지시킬수 있는 방법도 요청드립니다.

When upgrading to version 25.7.0, user-defined correction presets stop working. We can not see a particular pattern based on which some work, some dont. Those presets that don't work, are greyed out and it says they are incompatible, however, this does not make sense, since other presets who do the same thing continue to work.   This is not a minor thing. We built a variety of presets which many of our customers are using and all of them are now facing the same problem.

In the latest photoshop build 25.7 (windows 10), the adjustment layers histogram is not shown accurately.  It's showing the whites clipped here, and they are not.  The adjust->levels histogram I beleive is correct.  both are shown here on the exact same image.    

when I go to close psd after doing work I get a popup that says "can't write new documents photoshop" ..I updated to 25.11 from a previous version which didnt have that popup. Im on Windows 11 full system updates.I also was looking online and one site said change your Adobe photoshop 2024 settings folder to a different name in AppData\Roaming\Adobe\Adobe Photoshop 2024..That didnt work. 

Using Microsoft EdgeVersion 126.0.2592.87 (Official build) (64-bit) uploading a 6GB jpg file.  It Never finishess loading. Even the tutorial multiple images doesn't load the image.  Using 1GB wired Cox Cable connection. What gives?Photoshop will not load on pc due to upgrade?   

Bit of a long title, but that's what going on here. I think this has to do with when new colors were added to label layers with.   I am on Photoshop 25.6.0 on Windows 11.   Here's what I did: In the Layers panel, change the search to "Kind" to "Color". Change the color to search to "Fuchsia". It returns the correct layers. Switch to another open document and switch back. It will now be set to filter for "Gray" layers.   It seems the following colors to search get swapped out on switch: Seafom changes to Magenta Blue changes to Seafoam Indigo changes to Fuchsia Magenta changes to Violet Fucshia changes to Gray Violet changes to Blue Gray changes to Indigo   So if you start with filtering for Magenta and Tab between documents, it will cycle from Magenta > Violet > Blue > Seafoam > Magenta. This cannot be intentional. The colors not mentioned worked just fine.

I just updated to 25.7 and I'm noticing a visual glitch where the curves adjustment layer has a grey bar down the sides of the histogram. It makes it look like the white point slider has been dragged in from 255in/255out to say 255in/250out. Attaching a screenshot of how the curves adjustment layer properties window currently looks as well as the curves adjustment (non layer) screen does, which matches how the adjustment layer did until today. Note how there's a gap to the right of the white point on the adjustment layer. (there's also one on the left but that one doesn't matter as much since the output gradient is in the way, but it's probably caused by the same glitch I'd imagine)

Weird color swatch bug with the new adjustment brush. I generally work on images with both foreground and background swatches set to 255 white. When I cycle through brush tools with shift-B, the swatches stay white-white until I get to the new adjustment brush. Then the background swatch turns to black. However, if I then click the double-arrow icon or press X to swap foreground and background, both swatchs become white. Clicking the background swatch to show the color picker, also has it set to white. Just noticed it on Mac, Sonoma 14.5, PS 25.9. Have not tested on Windows.

I am opening CR3 files directly into the Photoshop 2024 Camera Raw Filter from archiving software (Fotostation) and applying changes (exposure, contrast etc), however when I click  'OK' to commit to changes and open the image in Photoshop, the changes are not applied. If I then re-open the image from Photoshop in the Camera Raw filter by selecting 'Filter - Camera Raw Filter' and re-apply the changes, when clicking 'OK' the changes ARE applied.  I've uninstalled/reinstalled Photoshop with no change. Any ideas? Thanks.  PCPhotoshop 25.1.0Camera Raw 16.0.0.1677Windows 10 Pro ver. 22H2 Dell XPS 1711th Gen Intel(R) Core(TM) i7-11800HNvidia GeForce RTX 3060 Laptop GPU

During vector field editing, the corner rounding direction changes.

While moving more than two artboards on a page to a specific place; those artboard moving randomly on the page to different locations that was intended to. *We a studio with more then 20 PCs and this occur in more then 5 PCs in Photoshop 25.11 (and some before that) and Photoshop Beta too. (in all of my tests)THANKS! 

Recently I have come across a post regarding color differences between layered and exported files here https://community.adobe.com/t5/photoshop/problem-with-curvers/m-p/11036512?page=1but it turned out, once again, to apparently be about the preview of Adjustment Layers on noisy images at magnifications other than View > 100%. I seem to recall that setting the Cache Levels to 1 could be used to address this issue (at a cost naturally). And according to this pagehttps://helpx.adobe.com/photoshop/kb/optimize-photoshop-cc-performance.htmlit should be possible, but when I set the Cache Levels to 1 they revert to 2 at restarting Photoshop. (Photoshop 21.1.1 on macOS 10.15.3)What could I be overlooking? Thanks in advance and have a good weekend!

1.- Probado con tres archivos tiff. Uno era copia del primero con el que ocurrió. El tercero de fecha anterior.     Los tres editados previamente a partir de raw.2.- Las dos primeras se abrieron en PS y mediante Filtros CR. Tras pequeños ajustes, ajuste de líneas en ACR     para corrección de líneas verticales distorsionadas por lente.  Aceptar y regreso a PS.3.- Herramienta Recortar para terminar el ajuste de líneas verticales en ACR.4.- Al ejecutar recortar la imagen pasa a un tamaño mínimo. Junto a ese punto la barra de IA.5.- Capturas de pantalla:      1.- Características tamaño archivo al inicio, tras abrir PS:                  2.- Tras recortar          3.- Tras deshacer recortar               Creo que el mensaje apareció aplicando laa herramiento mover para desplazar la foto hacia el centro de la     

Saving a file in Photoshop leads to sudden big peaks in CPU usage. In that for about 10 seconds the CPU goes to full 100%, and other running programs (of which there are not many) are impacted by this. This happens consistently when I test this with single layer PNG files. These file are 2048 x 2048 pixels, so not big at all. I have an up-to-date Windows 11, up to date graphics drivers, GPU enabled, plenty of memory, and an AMD Ryzen 9. But since a few weeks the CPU usage goes through the roof when I save even simple files like the PNGs I described before. That really should not be happening! Does anyone know how to fix this? 

Here is a summary of the bug: When I create an action in Photoshop (PS) that includes the SAVE command, those files do not get sent back to Lightroom (LR). However, if I manually save each file, they do get sent back to LR. More info: The other post mentions that this issue is also affected by a close action, but I have confirmed that the problem specifically arises with an automated save action. This action overwrites the first file that was opened and sent to Photoshop. For example, I have an action that adds a white border, saves the file, and closes the file. In Lightroom, I select five files, right-click, and choose "Open in Photoshop." In Photoshop, I select batch action, choose the script, and let it run on all open files. As the script runs, each open file sequentially overwrites the first file. After all files are closed, the only modified file in Lightroom is the first one, which now contains the data of the last saved file. This post is at the request of Sam, a member of Ado

In both Photoshop v.25.91 and Beta v.25.12 using latest Bridge v.16.4 I am unable to open either raw or jpg files in camera raw. I have had no problems up until now and my system reports my GPU ( NVIDIA GTX 1050) is working fine and has no issues (screen shots available). Any idea what is going on? Anyone else experiencing similar? Usual methods tried to no avail including reboot reset nvidia settings to default.  

Hallo! Ich habe PS Desktop unter Win10 und mir zusätzlich die Beta-Version heruntergeladen. Alles funktionierte prima. Die Beta-Version habe ich nun wieder deinstalliert. Als ich wie immer meinen Workflow mit Lightroom öffnete und das Bild über »bearbeiten in« an PS weitergeben wollte, war dieser Punkt grau  unterlegt und eine Übergabe an PS ging nicht mehr. Ich folgte der Anleitung Photoshop gänzlich neu zu installieren. Also habe ich auch PS Desktop deinstalliert und wollte jetzt PS neu installieren. Das geht nun nicht mehr. Es wird mir angezeigt »Fehlercode 306«. Egal was ich versuche, es bleibt immer bei dieser Aussage und ich kann PS Desktop, auch egal mit welcher älteren Version ausprobierend  nicht wieder installieren. Ich hoffe da gibt es einen Rat, was ich da noch probieren kann. Grüße

Hallo Zusammen!Ich habe Folgendes Problem:Ich habe ein Notebook ( Samsung Galaxy Book 3 Ultra) welches über eine Intel Grafikkarte onboard verfügt,diese verhindert das Photoshop nur über (Software) arbeitet aber nicht über (D3D12).Nun ist die frage ob es eine Lösung dafür gibt oder eine einstellung welche ich vielleicht noch übersehen habe. Mein Workaround ist derzeit vor dem Start von Photoshop die Grafik zu Deaktivieren und nach dem Start wieder zu Aktivieren damit PS flüssig läuft. Windows 11 Home mit Neustem Update PS 25.11 Neustes Update Intel I9 evoNvidia RTX 4070TI Neustes Update Adobe Photoshop Version: 25.11.0 20240716.r.706 b326a7d x64Anzahl der Starts: 390Betriebssystem: Windows 11 64-BitVersion: 11 oder höher 10.0.22631.3880Systemarchitektur: Intel CPU-Familie:6, Modell:10, Stepping:2 mit MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, AVX2, AVX-VNNI, HybridCPU(6:8), Hyper-ThreadingPhysischer Prozessor: 14Logischer Prozessor: 20Prozessor-Taktf

I brought this up over in the photoshop beta forum as well already and now the same bug has pushed to the live version.    I have a custom shortcut set up to open my foreground picker and it's now no longer working. This is affecting my workflow heavily as I rely on that shortcut. It is still showing that it is enabled in my shortcuts, but when I click N on my keyboard, nothing happens.    Please fix this asap.    Photoshop v 25.11

There seems to be a weird issue with the select/modify/expand command. Any attempt to use this tool results in cutting the corners of any rectangular shape, its not rounding off the corners but adding a 45 degree  notch on every one. The same effect is not present  on the contract command . The black line shows the original selection , the red outline shows the result of select/modify/expand 50 pixels and the green shows the result of Select/modify/contract.

After the 25.11 update i still have the same problem as started with 25.9. My file info screen "CMD+OPTION+SHIFT+I" is still running in English white the rest of my PS surrounding is in Dutch. It can't be that difficult to fix?

if you look at the top you can see that the menu mar is slightly squished and the share button pops out of it, you can see that some icons are elongated becuase of this.

Hola como están!, no se si a alguien le paso lo mismo, el problema que tengo es que en photoshop y en illustrator, los MENUS DESPLEGABLES dentro del programa están muy alargados, tienen mucho espacio entre cada uno. He hecho lo siguiente:DESINSTALAR / INSTALAR DE NUEVODESINSTALAR Y LIMPIAR CON UN PRORGRAMA / INSTALAR DE NUEVO USAR LA HERRAMIENTA DE ADOBE CREATIVE CLOUD CLEANARY siempre que vuelvo a instalar, sigue apareciendo el mismo problema.

Hallo! Ich habe ein Problem mit der KI-Funktion in Photoshop. Der nachgereichten Hintergrund hat nicht die weiche Textur des Originalbildes, sondern ist mit kleinen Rauten gemustert und sieht aus wie ein durchsichtiges, feines Netz. Das Programm ist frisch aktualisiert. Das Problem tritt bei allen Bildern auf, immer das gleiche.LG Elena