Any way to stop CC apps from creating huge files in CRLogs folder ?

  • 3
  • Problem
  • Updated 1 month ago
  • (Edited)
Hi

I can't accept that Adobe CC apps create a lot of huge files on my SSD without even asking (C:\Users\<user>\AppData\Roaming\Adobe\CRLogs). Also, uploading them using a DSL line consumes much bandwidth and generates problems for other applications. This appears to be new after I installed CC 2019 apps.

Any way to opt out of this logs uploading mechanism ?

Thanks in advance.

Photo of Patrick Philippot

Patrick Philippot

  • 440 Posts
  • 111 Reply Likes
  • frustrated

Posted 3 months ago

  • 3
Photo of Patrick Philippot

Patrick Philippot

  • 440 Posts
  • 111 Reply Likes
OK. I went to this page https://account.adobe.com/privacy and disabled the Machine Learning option. Not sure if this will be enough.

Photo of Massimiliano Luchi

Massimiliano Luchi

  • 10 Posts
  • 3 Reply Likes
Opting out doesn't work. I still get logs created every time LR crashes and they don't get deleted, filling up my SSD very fast.
Photo of Patrick Philippot

Patrick Philippot

  • 440 Posts
  • 111 Reply Likes
I confirm that opting out has no effect. I couldn't find any way to stop this.
Photo of Massimiliano Luchi

Massimiliano Luchi

  • 10 Posts
  • 3 Reply Likes
Customer support just told me that it is not possible and I should file it under "feature request".

I even tried to change the properties of the folder to write protected, but LR changes it upon launch.

In other words, you have to keep an eye on this folder and manually delete it's content. Which I already have to do for example with the NVIDIA "Installer2" folder everytime I update the drivers.

I assume that if you don't submit the crash report, the big files aren't created. I might just try that.

And hopefully I found all the poorly written programs that litter our SSDs...
Photo of Patrick Philippot

Patrick Philippot

  • 440 Posts
  • 111 Reply Likes
> I even tried to change the properties of the folder to write protected

It depends on how you did this. You could try to use ICACLS to deny write access to everyone. Something like :

ICACLS "C:\Users\<user>\AppData\Roaming\Adobe\CRLogs" /deny Everyone:(GW,WD)

entered from a command prompt running as an administrator. You can restore the initial permissions with

ICACLS "C:\Users\<user>\AppData\Roaming\Adobe\CRLogs" /grant Everyone:(GW,WD)

I'm not sure that (GW)(AD) will be enough but you can see the other options of ICACLS by entering

ICACLS /?

I have not tried this solution yet and setting the permissions this way could cause a crash of the calling program. So be cautious.

Hope this helps.
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 440 Posts
  • 111 Reply Likes
I made some tests. In order to restore access, the following command might also be needed :

ICACLS "C:\Users\<user>\AppData\Roaming\Adobe\CRLogs" /grant Everyone:(GA)

or

ICACLS "C:\Users\<user>\AppData\Roaming\Adobe\CRLogs" /grant Everyone:F
(Edited)
Photo of Massimiliano Luchi

Massimiliano Luchi

  • 10 Posts
  • 3 Reply Likes
It seems to not be working, though I might've done something wrong, I'm not used to command prompt. Anyway looks like at least one file in this folder is constantly in use by some background Adobe Cloud process, so it probably isn't something you can't just block without issues down the line.
Photo of Patrick Philippot

Patrick Philippot

  • 440 Posts
  • 111 Reply Likes
I have edited the command arguments. With

ICACLS "C:\Users\<user>\AppData\Roaming\Adobe\CRLogs" /deny Everyone:(GW,WD)

launching PS or LR no longer triggers the creation of additional 0 byte files in this folder.

There's always a file in use because it is created by Adobe Desktop Service.exe  service upon system startup. Killing this process allows to delete this file.
Photo of Massimiliano Luchi

Massimiliano Luchi

  • 10 Posts
  • 3 Reply Likes
Nice, thank you Patrick! I'll give it a shot, and if you don't hear from me anymore, it means it works :)

P.S. How did you figure out it was Adobe Desktop Service.exe using the file? Is there a direct way, or did you just kill all the processes one by one?
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 440 Posts
  • 111 Reply Likes
P.S. How did you figure out it was Adobe Desktop Service.exe using the file? Is there a direct way, or did you just kill all the processes one by one?
Massimiliano, sorry for the late answer. Whenever you need to determine which process is using (locking) a given file, you can use the Find feature of Process Explorer utility (sysinternals.com). Hit Ctrl-F or click on the Search icon and enter the name of the file. That's it.

Photo of Massimiliano Luchi

Massimiliano Luchi

  • 10 Posts
  • 3 Reply Likes
Thank you very much Patrick! This is like the Holy Grail :D
Photo of Rob Rippengale

Rob Rippengale

  • 84 Posts
  • 57 Reply Likes
Thanks for finding this, Patrick.

Adobe: I SHOULD HAVE BEEN ASKED TO OPT IN. This stealing of my information is completely unacceptable.
Photo of dmeephd

dmeephd

  • 282 Posts
  • 62 Reply Likes
They're selling your information.  We are Adobe profit centers, not customers.