Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
J Isner
Enthusiast
J Isner
Enthusiast
Activity
‎Apr 01, 2020
12:04 PM
Two months after the 4-minute launch problem began, it has mysteriously disappeared. For the last five days, Photoshop has launched in under 10 seconds. As far as I know, nothing on my Windows 10 system changed, at least nothing I am aware of. I won't be surprised if the problem returns.
... View more
‎Mar 01, 2020
01:18 PM
Today, when I launched Photoshop from Lightroom (Photo > Edit in... > Adobe Photoshop 2020), I got the following error When I clicked OK, the Photoshop splash screen appeared. Normally, Photoshop hangs for 4 minutes during the "Intializing..." phase. However today it zipped through "initializing" and the program launched in seconds. I checked my preferences and I don't see any changes. Based on the timestamp, the Adobe Photoshop 2020 prefs.psp file wasn't touched. Note that I never followed through on the suggestions various posters have made regarding the preferences file. That's because the 4 minute delay occurs when the splash screen shows "Initializing...". All the other launch phases, including the reading of preferences, go very quickly.
... View more
‎Feb 22, 2020
04:00 PM
The four-minute launch has persisted for over a month. During the four minutes, the splash screen is stuck on "Initializing..." and then it quickly zips through loading preferences and whatever else it does before the window appears. But today Photoshop launched in 10 seconds. Nothing on my system changed. I suspect an intermittant hardware problem, although my PC shows no other signs of misbehavior.
... View more
‎Feb 17, 2020
11:45 AM
Thank you, I learned something! I'm trying to create a grayscale document containing a table of 101 grayscale values from 0% to 100% in steps of 1%. When someone opens the document and samples the cells with the eyedropper, each cell must have the exact K value it was created with. My Gray menu in Color Settings only offers the following choices (I'm using Gray Gamma 2.2 and Dot Gain 20%) One way to do it (clumsy, but it works), is to fill the cell with black and then reduce opacity to the desired percentage. For example, if Opacity = 30%, the eyedroper readout is K=30%.
... View more
‎Feb 17, 2020
10:35 AM
But how can I use the color picker to choose a specific grayscale value? When I entered K=20%, I got K=18%.
... View more
‎Feb 17, 2020
10:07 AM
My document mode is Grayscale, but when I use the Color Picker, it offers me colors. Specifically, When I do an Edit -> Fill and set K=20% (see below), the color actually added has unequal R, G, and B components (208,209,211). After filling, if I check the color with the eyedropper, it reads 18%, not 20%. Clearly, I misunderstand Grayscale mode. What is the correct way to fill with a specific K value? Photoshop 21.0.3 on Windows 10.
... View more
‎Feb 13, 2020
08:22 PM
Device Manager only shows one display adapter. Perhaps the integrated graphics does not show up because it is disabled. The Julianne Kost video does not mention the need to back up actions, brushes, etc. before resetting preferences. Are you implying that they may be lost as a result of resetting preferences? By "backing up" do you mean exporting them to a folder? (Edit -> Presets -> Export/Import Presets)?
... View more
‎Feb 12, 2020
04:59 PM
3 Upvotes
About three weeks ago, Photoshop CC 2020 began taking over four minutes to launch on Windows 10 (it normally takes 10 seconds). During this time, the splash screen is stuck on "Initializing..." and Task Manager shows the process as "Not responding." After it finally launches, I don't notice any performance problems and everything works normally. I updated my Radeon software to the latest version (this has caused problems with Photoshop in the past). I restarted Windows. I uninstalled and then reinstalled Photoshop from the Creative Cloud desktop app. But when I re-launched Photoshop, it still took 4 minutes. Any idea what might be causing the problem? I should mention that since I started having this problem, my mouse cursor displays the "Working in Background" spinning blue circle almost continuously. I wonder if it's related to the problems I'm having with Photoshop. The problem started in Photoshop version 21.0.2 and continues in 21.0.3.
... View more
‎Dec 29, 2019
10:41 AM
Thanks. I reported it here.
... View more
‎Dec 29, 2019
08:57 AM
I am having a similar problem with Photoshop v21 on Windows 10 when saving to an internal hard drive. Progress goes to 99% quickly, then stays there for a relatively long time before the save operation is completed. File sizes are not very large, typically 200 MB.
... View more
‎Dec 27, 2019
02:58 PM
Turning off GPU seems to solve the problem with both import and synchronize! I'm going to keep it turned off and see if I can live with it that way. By the way, in the latest version of Lightroom Classic (v9.1), Use Graphics Processor has three choices instead of a checkbox:
... View more
‎Dec 27, 2019
01:23 PM
Ever since upgrading from Windows 7 to Windows 10, importing even a single photo from an SD card or from another location in the file system routinely takes three to five minutes. During most of that time, Lightroom is "not responding." This is on a PC that was built with PS/LR requirements in mind. The same delay occurs when I synchronize a folder after manually dropping a file there.
My catalog is 917 MB. I never deal with large numbers of files. It's almost always one or two. Export is fast. So it's not all interactions with the Windows file system that are slow, just those that require Lightroom to query the OS. For example, when importing from another location in the file system, Lightroom takes a long time just to display the folder hierarchy in the left panel of the import window.
{Thread renamed by moderator}
... View more
‎Dec 24, 2019
12:54 PM
I updated PS to v21 and did the "Convert to Layers." Thank you again.
... View more
‎Dec 24, 2019
12:18 PM
That's great news. I'm still on v20, so I'll update right now.
... View more
‎Dec 24, 2019
12:00 PM
I have some layers that I converted to a smart object. I'd like to get the original layers back. In other words, I want to replace the smart object by its contents. Is this possible?
... View more
‎Dec 08, 2019
10:51 AM
I have exactly the same problem. I have had the problem with all versions of Lightroom Classic since I upgraded to Windows 10.
... View more
‎Nov 30, 2019
09:56 PM
@JJMack Thank you for the Crafting Actions package. I have been reading the documentation. It looks extremely useful. I know Javascript, so learning scripting shouldn't be too difficult.
... View more
‎Nov 30, 2019
05:37 PM
I just finished converting the action to select layers stepwise for precisely the reason that there are duplicate layer names. In this particular action, duplication is unavoidable. If I knew how to write scripts, I wouldan't be writing actions! I should take some time and learn the scripting language.
... View more
‎Nov 30, 2019
04:39 PM
1 Upvote
I'm writing a Photoshop action that is supposed to select one of the layers inside a group. At the point where this happens, the group itself is selected and its contents are collapsed. Using the shortcut alt-[ ("select backward layer") steps OVER the group so that the layer below the group is now selected. But I want it to step INTO the group. Alt-[ steps into the group if the contents are expanded, but I have no way of controlling whether the group is expanded or collapsed. Clicking on the arrow next to the group to expand is not recorded. Is there a way to do this?
... View more
‎Oct 26, 2019
08:33 PM
1 Upvote
I found a temporary workaround in this discussion. The fix is actually easier than the steps given in the "Correct Answer." I simply RENAMED the directory C:\Program Files (x86)\Common Files\Adobe\CoreSyncExtension\ as C:\Program Files (x86)\Common Files\Adobe\CoreSyncExtension YOU WONT FIND ME\ I re-tried the update and it succeeded. The workaround is temporary because it will have to be repeated the next time Creative Cloud wants to update itself.
... View more
‎Oct 26, 2019
06:15 PM
Thanks for the link. I have seen that discussion and others like it. I don't have any older versions of any of the apps installed, only the latest PS, LR, and BR. The problem is with the Creative Cloud app itself. Three weeks ago, I spent 45 minutes in a remote debugging session with Adobe engineers from India. They walked me through a fix that involved (a) killing one of the Adobe processes that runs at startup (unfortunately, I don't recall which process it was ... there are a seven or eight of them) and (b) renaming two dll's in C:\Program Files (x86)\Common Files\Adobe\CoreSyncExtension\. Then I retried the update and it ran quickly to completion. However just as I suspected, the next time the app needed to update itself (which happened today), it again failed with error 184. I'm pretty sure the same temporary fix will work, but I don't remember which app to kill! It's most certainly one of these: FYI, the relevant line in the instal.log says WARN: Unable to move file at "C:\adobeTemp\ETRA667.tmp\7\CoreSyncExtension\CoreSync_x64.dll" to "C:\Program Files (x86)\Common Files\Adobe\CoreSyncExtension\CoreSync_x64.dll" Error 32 The process cannot access the file because it is being used by another process.. Try setting correct permissions to the specified file/folder or parent folder, so that admin has rights to modify it. Unfortunately, the message does not identify the process. Now here's how the failed update is hurting my system: When the Creative Cloud app finishes updating, regardless of whether it succeeds or fails, it kills and restarts explorer.exe. If the update has failed, CC will try to update itself again the next time the PC is restarted ... and the next time ... and the next time. The attempted update happens relatively soon after I boot the PC, while other programs are still being started. Explorer.exe is being killed while other critical startup events are still happening, leaving my system in a broken state. A possible workaround might be to delay the startup of Creative Cloud, but I have no idea how to do it.
... View more
‎Oct 26, 2019
03:00 PM
In the desktop app, I did Help -> Check for updates. This once again notifies me that an update to PS is available (I get a popup notification in the notification area). When I referesh the web page, it still says "get the desktop app" for Photoshop. Uninstalling the desktop app may be possible, but then you won't be able to run any of your Adobe apps. You can't even quit the desktop app. If you try, you get this: The desktop app apparently plays some role in making sure your Adobe subscription is paid up. So you are FORCED to run it. And you are FORCED to accept whatever damage it does to your system. A bug nest indeed.
... View more
‎Oct 26, 2019
02:24 PM
Hi Samoreen, I don't see that they're "exactly the same." The desktop app is currently telling me that an update for PS is available (which is true). However the web page is inviting me to "get" PS. So the two don't seem to be in sync. But suppose they were in sync. Then running the desktop app should be optional, and you should be able to uninstall it. However Adobe prevents you from uninstalling it: As long as you can't uninstall it, it will continue to try to update itself at every startup. And fail, with consequences.
... View more
‎Oct 26, 2019
01:42 PM
1 Upvote
It's Baaaaack! Today the new Creative Cloud Desktop app installed itself on my Windows 10 PC. The new app has the same problem as the old one: It tries to update itself and fails with Error 184, leaving my system in a broken state (permissions problems). The workaround given to me by the Adobe engineers less than three weeks ago only held until the next update. I was hoping that the new app would fix this bug. Sadly, it appears to only "streamline" the user interface.
... View more
‎Oct 10, 2019
08:29 AM
Let us know what you think. Is there hope?
... View more
‎Oct 10, 2019
07:54 AM
I see that Adobe is "rolling out" a redesigned CC for Mac and Windows with "streamlined interface." I wonder if it includes a fix for the issue discussed here.
... View more
‎Oct 09, 2019
05:28 PM
I also wonder if the next time CC wants to update itself, it will run into the same problem. If it does, I'll rename the same two dll's and hope for another temporary workaround. Who knows, maybe the next update will REALLY fix the bug. Adobe seems to have a handle on it.
... View more
‎Oct 09, 2019
10:05 AM
1 Upvote
Samoreen, Last night I spent a half hour in a remote debugging session with four Adobe engineers from India. They clearly knew how to fix the problem. They had me rename two dll's in C:\Program Files (x86)\Common Files\Adobe\CoreSyncExtension\ (CoreSync_x64.dll and CoreSync_x86.dll), then try updating CreativeCloud again. This time, update succeeded. Of course the screen still blinked (CC does kill explorer.exe) but it did not leave my system in a broken state.
... View more
‎Oct 06, 2019
12:14 PM
I wonder why more people aren't affected by this. Could there be something particular about our Windows setup?
... View more
‎Oct 04, 2019
05:08 PM
1 Upvote
I'm beginning to suspect that CreativeCloud is the source of other problems I've been having on my Windows 10 computer. Here are two pieces of evidence for that theory. (1) If I kill CreativeCloud and restart it, it tries to update itself, and it fails in about 4 minutes. Just before it fails, my desktop "blinks" (briefly goes black) twice. (2) Before noticing the CreativeCloud update problem, I had been getting the double-blinking behavior about 3-4 minutes into startup every time I booted my PC. Since CreativeCloud runs at startup, I now suspect that Creative Cloud is the source of the double blink. But wait, it gets worse: After the double blink (the one that follows startup), there are problems with permissions. For example, if I try to launch Device Manager, I get "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item." I also lose access to my printer and other hardware devices (again, no permission to access). Could CC be causing this?
... View more
Copyright © 2025 Adobe. All rights reserved.
AdChoices