Bug Reports

Hello, I just noticed that the"Color Settings.csf" found in the preferences folder of the computer I'm facing (still running 22.4.3) is listed as "Color Settingscsf", without the period. and therefore without an extension... According to the help files, it should have the period in the name... I wonder if it works properly as is... the file properly updated, still without the period.   Users\[user name]\AppData\Roaming\Adobe\Adobe Photoshop [version]\Adobe Photoshop [version] Settings   Can anyone check if it is also the case on their machine? 

I thought I would make a comment about the Select Object and maybe it can filter back to the people who do marvelous things like that.  First of all, I want to let everyone know I am amazed at how the "AI system" does its thing!  But I have an image that doesn't do the norm.  The image is of an elk, and the "blue" silouette doesn't follow the "ants" selection - the blue outline is better!  I was wondering if I could get the "ants" to follow the blue outline?  (I am on a Windows 10 computer.)

Hello,   I just came across a bizarre Polish translation of the menu in the new Photoshop 23. In the Export as ... menu, we can choose the quality of the jpg file in which the graphics should be, we can choose 7 values. The last two are: - doskonała and świetna. Doskonała means perfect, świetna means great. There can't be something better than PERFECT i supouse. Anyway, We should can choose quality just as with old "Save as for internet". Especially when we need to save a file with a specific value in kb, and the difference between the grades to choose from is too significant.

Hi Team, when importing a layered PSD into InDesign (all software versions have been updated) the adjustment layers are not rendering correctly. Specifically, using a Black and White adjustment layer with a Gradient Map above. The preview shows the masked area as mono, yet when a composite layer is placed at the top of the stack it renders correctly in InDesign. Any ideas? Cheers, Mark

Hi,I have recently "upgraded" to Windows 11 and now I am having issues with the Photoshop UI. I am not sure if this is really Adobe's fault but since it's happening in the Software I'm posting here first.The issue is that on popup windows the mouse pointer is offset downwards. I have reinstalled Windows 11 on Friday because I heard upgrading instead of re-installing can cause issues but this did not resolve the issue (and neither my other Windows 11 issues).Here is a video explaining it a lot better than words could do: Photoshop:Version 23.0.3 OS:Edition Windows 11 HomeVersion 21H2OS build 22000.318Experience Windows Feature Experience Pack 1000.22000.318.0Thank you for your help!

I was unable to open photoshop after I have perform the update today. It was constantly crashing. Please help.

I keep having an issue with white boxes obscuring portions of my files when I am zooming in and out or saving the image. It happens when I try to flatten the image, save as a PDF, or save as a JPG. Prior to updating to version 22, I had found a workaround to the issue by using the Legacy Compositing checkbox. However in this version, that option is no longer available and I cannot find any way to stop the boxes now. I am running on a Macmini using macOS Catalina. Someone please help!

We can manually access 3 Performance checkboxes (Accelerated, Step by Step, Pause for: / value) in 'Playback Options' from dropdown menu of 'Actions' Panel. There is no problem to set them by script. Unfortunately we can not read them:     sTT = stringIDToTypeID, ref = new ActionReference() ref.putProperty(sTT('property'), sTT('playbackOptions')) ref.putEnumerated(sTT('application'), sTT('ordinal'), sTT('targetEnum')) executeActionGet(ref)     The above codes gives error, but the similar one to read 'Add "copy" to Copied Layers and Groups' (which manually we access from 'Panel Options' of 'Layers' panel dropdown menu) works with no problem from first CC release (as in CS6 it didn't work yet):     sTT = stringIDToTypeID, ref = new ActionReference() ref.putProperty(sTT('property'), sTT('addCopyToLayerNames')) ref.putEnumerated(sTT('application'), sTT('ordinal'), sTT('targetEnum')) executeActionGet(ref).getBoolean(sTT('addCopyToLayerNames'))    

If a guide is ctrl/cmd-dragged while a transform is in process, the guide creation is not added to History. 1. Create new document 2. Use marquee tool to select an area of the canvas 3. Select Free Transform 4. Ctrl/cmd-drag a guide onto the canvas 5. Enter a rotation value 6. Apply the transform Result- transform is applied, new guide is added, guide creation not in history (see attached video) Windows 10 Pro, PS 22.5.3

After updating the photoshop in my mac pro, when I use the zoom in the trackpad it works with some delay, like if it was trying to make it "smooth" but it's actually really annoying. Anyone with the same problem?   {Moderator note: Edited the thread title, PS-63413}

v23 has brought a lot of problems so far on my Surface; first the touchscreen crashes, and now the difficulty accessing my own body of work. Why am I getting this error, and why only on my Surface?     I can download the file through the web interface as a PSD, and then open it and save it as a new Cloud Document, but that's obviouly not an ideal situation.The Cloud Docs all open on my Windows desktop without any problems. Both devices are running Windows 10 21H1, both are running Photoshop 23.0.1.Does anyone know what might cause this?

Hi, When I start to have multiple layers on a file Photoshop crashes when adding adjustment layer of making a free hand selection with lasso tool.  I tried all the workaround suggested on the help page, what can do now ? Thanks for the help. - Photoshop 23.0.0 MPB 2019 AMD Radeon Pro 5500M 8 Go, 64 RAM MacOS 11.6

After the update to Photoshop CC 2020 (now 21.1.2), there are problems with working on the Wacom tablet: elements (especially smart objects and layers grouped in group folders) jump back and forth when moving and cannot be placed precisely. This happens on several computers with different tablets. This does not happen with other programs (inkluding Photoshop 2019, Adobe Illustrator CC 2020, Indesign CC 2020, Open Office, operating system and including Photoshop 2019). The mouse is working proper.   View example: https://www.dropbox.com/s/ws1k63n9epfcxfg/wacomspringen3beispiele.mp4?dl=0   I had called the Adobe support before and was finally referred to Wacom. After writing extensively with Wacom Support and performing various tests without success, I was referred back to Adobe (because the problem is only in Photoshop) and write with the Adobe support again – but without result. Now they send me to the forum.   My Setting (s):   x Wacom Intous 4 XL (PTK-1240)  

It is so annoying. For years this bug is not fixed in the German version: Tool tips can be enlarged with #. But in some Photoshop modules they are reduced in size (in Liquefy for example). This drives me crazy...

Say I have a RGB/8bit photoshop file, with one or more spot channels in it:   I make sure the visibility of those spot channel(s) is currently OFF ( by togling off each spot channels' eye icon ), and that only the RGB channels are currently selected and visible. I then create a new layer, and add a layer mask to it. I then select the new layer's RGB channel ( result: the RGB channel and its R, G, and B component channels are all selected and visible )  If I now select the new layer's 'layer mask', again, all the spot channels are made visible, AUTOMATICALLY.   Why is this happening?  The visibility of the spot channels was previously off; why does selecting a layer mask ( any layer mask of any layer, as a matter of fact ) makes all the spot channels visible?  This is really distracting and I can't think of a reason for this behavior.  I assume this is a bug.   Note: changing the solidity percentage of the spot channels to 0% doesn't preven

This checkbox has never worked as it should, but now it's more broken than ever.   It's supposed to do two things. In addition to the obvious, embedding the profile, it should also turn on the color managed view, using the system monitor profile to display the file correctly in the chosen document color space.   At the moment it doesn't use the monitor profile. People with standard monitors may not immediately notice this, but with a wide gamut monitor it becomes very obvious (oversaturated). It behaves like Save For Web with Preview set to "Monitor Color".   In the old Save For Web, there were two separate settings - an "embed profile"-box, and a rolldown for "Preview". Setting this rolldown to "use document profile" turned on the color managed view (and this still works reliably). It actually makes perfect sense to roll these two into one, so that's fine. But it doesn't work.   One more thing: Please make the "embed color profile"-box checked by default! Or at lea

Photoshop version:  22.5.1 and earlier OS: Mac OS Steps to reproduce: Make sure the file has a profile like sRGB and Save a file as PNG Close the file and open it you get the following warning: The RGB document “name of doc” has a file format that does not support embedded color profiles. Expected result: The profile would be saved like in Save for Web and using ExportActual result: Profiles are not saved and even removed when saving a PNG in Photoshop

I always start my editing process with making a Smart filter, and apply the Camera RAW. I edit in here with multiple selective edits (brush tool, gradient, etc.). When I'm done in Camera RAW I close it down and start edit with muliple layers in the normal Photoshop view.  Whenever I come to my final stages I like to do tweaks to the crop. I do this at the end, with many layers in the layer panel, including the smart layer with camera RAW from the early stages. Whenever the crop render the selective edits from the smart object get misaligned. My work-around is to create a new merged layer before the crop, but that limits my ability to go back and edit again later if I'd want to do that.    Are there any other work-arounds or will the bug be fixed in the near future? 🙏

I upgraded to PS 2022 (v23.0.0) and it looks like an old bug has resurfaced.   Expected behavior: When I click a Shape, the Properties panel should show the Shape Properties options, with things like Fill, Stroke, corner radius, etc. (Basically the same options as what appears in the top bar.)   What's happening: Some shapes will show the Masks options in the Properties panel instead of the Shape Properties options. No Fill, Stroke, etc, just Density and Feather. (I've verified that they are shapes, with the square-with-corners icon in the Layers panel.)   To reproduce: Create text object. Right-click its layer, select "Convert to Shape". Non-converted shapes (rectangles, ellipses) seem to work correctly. I've done this thousands of times in PS 2021 and 2020, and it always worked correctly.   Is anyone else having this issue? I know this bug existed for a year or two when they first introduced the Properties panel, so it's unfortunate to see it resurface a

Issue: record action bug when setting keyframes on an object property Photoshop version: All Photoshop CC versions from 2015 to 2019 (does NOT happen in the CS6 version) OS and version: Windows 10 21H1 Steps to reproduce the behavior (most options are not mandatory, posted just for reference): - open Photoshop without creating or opening any file - start recording your actions - File / New / random resolution transparent Document - Timeline: Create Video Timeline - 3D / New Mesh From Layer / Mesh Preset / Sphere - select 3D Panel: Scene: Sphere, then its Properties: Coordinates in the appropriate panel, then Timeline: <Current Layer>: 3D Meshes: Sphere, and click the stopwatch to Enable Keyframe Animation [stopwatch turns yellow] - go to a random time in the Timeline and set, say, the Y axis angle to 90 degrees - stop recording - play your recorded actions   Expected result: the recorded actions should play without issues / errors (like in Photoshop CS6)

Just noticed this bug when resizing the Shape window in the options bar Photoshop version 23.0 Windows 10 GPU RTX2600 Super, latest studio driver installed CPU i9 11900k RAM 64GB DDR4 Tested with deactivate native canvas on and off, same result Seems to be the same in version 22.5.2  

Photoshop 23.0.0 and 23.0.1 crash on startup on mac M1, big sur, native mode. Switching to rosetta fixes this, but at a pretty hefty cost to performance. I've sent crash reports, but posting it here too because its a big one. 

Using PS 22.5, each time I try to shift+click to select multiple anchor points in a Warp transformation, Photoshop crash without any message. It just quit.PS Prerelease 23.0 is is behaving exactly the same. This is a Apple issues since this is working fine on Windows.Does this is related to the fact that my GPU is not supported anymore on my old MacBookPro? macOS 10.15.7 Catalina.

I just updated to v22.5 of Photoshop and I've noticed the new "Export As" dialog is now the default (it says v5.5.5) and I've noticed quite a few regressions in the user experience compared to the previous version.   First, the font is far too thin. I am on Windows 10, my monitor is 2560x1440 and I'm not using any scaling, so this does not look great for the most part.   Keyboard shortcuts have stopped working. Before, pressing Enter upon first opening the window would do the same thing as clicking the Export button below.   Pressing Ctrl+ to zoom in and out used to work as well. Now, zooming is only possible with the small plus and minus buttons. I was wrong about this one, but it would still be nice to be able to zoom in with keys if the image area is in focus.   When selecting multiple images, the previews appear too sharp and there's visible sharpening noise around finer details that weren't there before.   It also looks like exporting SVG isn't possible a

I'm having trouble using the Line Tool in PS 22.0.0.    How do I set the width/weight of the line? In PS 21 there was a "Weight" option along the top bar, but I don't see that anymore. Am I missing it? Or did it move?    This might be a separate issue, but the lines I'm drawing are not showing up. I have a fill color and stroke color selected, but when I make a line, I don't see it. I just see a blue outline of where it is... the same that might happen if I made a "path" instead of a "shape."    I just need to make a line with a width/weight of 20px.