AdobeGC.log files taking over my hard drive

I'm having this same issue. None of the suggestions I found here were helpful. Do you finally have a fix?

sersouly?

I cant believe you didnt test this out before installing. There are hundreds of duplicate files on my mac. I thought I got hacked.

An engineer is going to take a look at one of our machines. Hopefully he can make some headway toward a solution because it's time consuming to have to keep up with over a dozen installations and their ever increasing log files and high CPU utilization.

I as well am wondering when this issue will be permanently fixed with an update. This occurs for ALL installations of Adobe 10, 11 and DC for us, renaming the GCClient to a .OLD file does NOT fix it because the Adobe Genuine Software Integrity service just recreates it. Stopping and disabling this service DOES fix the issue, but I am sure in 30 days we will encounter licensing errors. This needs to be addressed in an update.

Reinstalling CC Desktop seems to prevent AdobeGCClient.ex *32 from taking 13% of my CPU and preventing the log file from growing.

However, on reboot, the problem returns.

After reboot, reinstalling CC Desktop seems to prevent AdobeGCClient.ex *32 from taking 13% of my CPU and preventing the log file from growing.

Perhaps the solution is just that: After every boot, terminate AdobeGCClient.exe *32 in the Task Manager, and then reinstall CC Desktop after every reboot?

What else to do?

I ran into this issue myself and after working with support it had looked like the issue was resolved, but it had come back within 24 hours. After a while of this continuing to occur, I went through my registry and common folders eliminating everything I could find pointing to Acrobat 11 and the AC76BA86-1033-FFFF-7760-000000000006 id. Hoping this had resolved it, I realized that it was still consuming excessive amounts of space. Finally I opened up process monitor to see what the AdobeGCClient was getting looped around on. I found that it was trying to look for several registry keys and fail, but did manage to find one.

In HKEY_CLASSES_ROOT\Installer\UpgradeCodes, there's a key called 68AB67CA000000007706E7A854000000. Inside of that key I have two String Values:

68AB67CA3301FFFF7706000000000060 and 68AB67CA3301FFFF7706C0F070E41400. After some quick glancing, I noticed that the first item looked eerily similar (just numbers shifted around) to the UUID that is getting spammed in my logs.

68AB67CA-3301-FFFF-7706-000000000060

AC76BA86-1033-FFFF-7760-000000000006

As you'll notice with the dashes added in, if you just re-order them, it's the same ID ... there's probably a specific term or something for the way this has been re-arranged. Anyways, I backed up the HKEY_CLASSES_ROOT\Installer\UpgradeCodes\68AB67CA000000007706E7A854000000 key and deleted the 68AB67CA3301FFFF7706000000000060 string. The log almost immediately stopped growing exponentially and started getting back on track. Now, I'm not saying that you should do this yourselves, but I'm saying that (at least for the time being) my logs aren't getting flooded.

It's been less than 24 hours at this point, so I'll report back if the issue recurs -- but so far this seems to have worked for me. Take caution and do not touch your registry without making backups. Please note that I also did a lot of work trying to clear out as many things as I could related to Acrobat 11 before I finally got to this stage -- so it's very possible that just doing this alone won't stop the problem -- it's just what I had observed the AdobeGCClient reading as one of the registry keys which my searches would not have found.

Update - Feb 4, 2016

It's been about two days since I created this post. The adobegc.log file is only 308KB and I have not had the issue come back so far. I haven't attempted to load Acrobat DC or restart my computer since I've done this change, but for the moment it all seems pretty promising.

I tried renaming the folder as suggested by adamhahnderson and the folder was promptly recreated but I did not notice it until today when I saw again my hard disk space had declined drastically.  So that did not work for me.  I am going to rename the execution files .old and see if that helps.  Here is view of the recreated folder.  I will update progress.

This has been happening to me for many months now. Very frustrating. I am forced to keep checking my HD space to see if it has been eaten by AdobeGCClient log files. Ridiculous. Today I implemented the registry hack as well as the folder name change... hoping that alleviates the problem. I tried moving/renaming the actual EXE file but it recreates it when I restart the computer. Running Windows 7 Professional 64-bit.

I too found the executable here:

C:\Program Files (x86)\Common Files\Adobe\AdobeGCClient

I tried all the previous fixes, I uninstall the Creative Cloud installer and reinstall - no luck.

I renamed it - it respawned.  I replaced it with an alternate file with the same name - it respawned. Every night it would regenerate itself and fire up again, writing the same line into a never ending serious of log files over and over until the hard drive was full, taking up 12% of my CPU and lots of HD bandwidth.  Like a zombie it was hard to kill....

What I finally did that worked:

I wrote a key into the registry that blocked it from starting.  It's still there, it still tries to fire up every night, but it can't.  Seems be an OK fix.  I found the instructions here:

How to Block an Application or .EXE from Running in Windows

Good luck, I hope this helps someone..

BTW, this is a totally bogus problem that Adobe should fix, the program is overzelously checking for valid licenses on individual programs, when I have a valid/full CC subscription signed in on this computer - any checking Adobe feels it needs to validate permitted use should begin and end with verifying the CC license, not querying all the installed applications license files over and over and over again...

Bill