When I start CC it creates a folder named GPUCache on my desktop. I like to keep things organized and I'd rather not have folders on my desktop. Is there a way to change the folder location?
Thank you in advance
I have the same issue too and I also don't want that folder showing on my desktop.
I too have this same problem, and it just started happening. This is NOT acceptable behavior for an application. Adobe needs to resolve this issue.
What OS are you using? Can you confirm that you have Creative Cloud desktop application 188.8.131.524 installed (Release notes for the Adobe Creative Cloud desktop app ).
Also do you have any Third party firewall software installed?
I'm using windows 10 and I can confirm I have the latest version of CC (184.108.40.2064) installed. The problem first occurred after the latest update. I do not have any third party firewall software installed.
juniorv4195568 SG... Hi, I am also having the same nuisance with the GPUCache folder popping up every time I launch the CC desktop application. This was not occurring before today, and I have had the creative cloud suite (220.127.116.114) since around April 2018.
I'm using Windows 7 and have been using norton antivirus. And as far as I know, none of the antivirus settings have been recently changed.
I'm using Windows 7 Pro with MicroTrend installed. I have the latest CC installed. 18.104.22.1684
Those with Firewalls, can you check to see if there are new alerts that are flagging any Adobe processes?
I'm also trying to reproduce on my end.
I'm having the same problem. I'm using only the built in Windows 7 firewall and I gave permissions to Adobe apps. Also I have set an exception for Creative Cloud in my antivirus NOD32.
Haven't had this GPUCache problem before.
Can you gather another data point that will help out? The steps are a bit labored sorry.
1) Go to the Creative Cloud Desktop application preferences and uncheck the 'Launch at login' option.
2) Now restart WinOS
3) After login to OS, go to your desktop and delete the GPUCache directory
4) Now go to C:\Program Files (x86)\Common\Adobe\Creative Cloud Libraries and double click the CCLibrary.exe
Is the GPUCache directory created?
If not, launch the Creative Cloud desktop app and see if the directory in now created.
After following your steps I have te following results:
- Unchecking 'launch at login', restarting WinOS, deleting GPUCache directory and double clicking CCLibrary.exe does not create the GPUCache directory
- Launching the CC desktop app after all 4 steps creates the GPUCache directory again
I have followed your steps. They're not hard steps, I'm not a beginner at using Windows.
The result is the same as the above user said. Double clicking CCLibraries.exe after all the followed steps does not create the GPUCache folder on desktop.
Launching Creative Cloud desktop app from the desktop icon/shortcut re-creates the same GPUCache folder again.
Thanks for reporting back. The labored part of the steps was the OS reboot. 😉
I have an inquiry off the the folks developing the Creative Cloud desktop app.
Just chiming in to add myself to the list of people having this issue. I'm on Windows 7. I turned my computer on a while ago and the CC app wasn't open since I don't have it set to launch on startup. Then I had to step out for an hour.
When I came back, I saw the CC app icon in the notification area and the desktop shortcut was moved so I figured it must have opened and run an update. Some Adobe desktop icons move after updates. Not important.
I right clicked the CC app icon in the notification area to pull up the right click menu and quit the app but nothing happened so I double clicked to launch the app and again nothing happened. Both are abnormal behavior, so I double clicked the actual desktop CC icon and that did launch the app, but it also generated the GPUCache folder on the desktop.
The folder contains five files (date_0 through data_3 and index). I checked the version number on the CC app and it's now 22.214.171.1244 which was released today, so that's what it updated to when I stepped out and is clearly what's causing this odd behavior. Glad I'm not the only one noticing and hopefully the team will have an answer soon! Thanks.
Copy link to clipboard
Thanks for reporting this. Below are quick steps to stop creation of "GPUCache folder on desktop" when launching Creative Cloud:
Do let us know in case you face any issues with these steps.
I have followed these steps and it worked. It is fixed for me. Thank you!
All the best!
Your fix works for me thanks.
Windows 7, CC 126.96.36.1994.
Updating the shortcut worked to stop the cache folder from appearing for me as well, thanks!
I'm still curious about the other issue to do with the CC app seemingly running on its own in the background now yet I can't interact with it. See this snapshot of my notification area.
Prior to the update, I had only the black tray icon for CC, which would only appear when I actually launched the app. After the update, that red one appeared on its own and can't be interacted with.
If I launch the app, the black icon appears next to it (as shown here) and if I quit the app (either from inside the app or from the right click menu on the black icon), the red icon will disappear too.
But when I restart my computer, the red one appears there on its own again even though I still have the app set not to run on startup. Did the update enable something on the backend that's not fully implemented yet? Like is that red icon supposed to replace the black one but something buggy split them up and that's why I can't interact with it at all?
Just curious about it, it isn't affecting the running of my apps or anything.
Same problem, and now fixed.
This seems like something Adobe should be patching. Do you expect everyone to jump through all those hoops you laid out to "fix" the issue? It's nonsense. Just make it an update patch!
Patch is not live the site you posted listed the last update as July 16th and the issue is still occurring. Even checking inside the creative cloud app says no updates.
188.8.131.524 is my current version though the fix looks like its applied to .391 which isn't being pushed out. Yes mine is set to auto update.