Premiere and Media Encoder creating D:\AppData\Roaming\Adobe\Common\LUTs on launch

[R Neil Haugen]

A number of users on the U2U forums are having issues with Premiere or MediaEncoder creating a folder tree on their D: drive as follows ...

D:\AppData\Roaming\Adobe\Common\LUTs

or

D:\AppData\Roaming\Adobe\Common\LUTs\Technical


It first was noted by people with Onedrive or Dropbox, but now several others have popped in that do not have those sync apps and everytime Premiere or Me launch, the apps create the folder-tree and folders.

Delete the folders, launch Pr or Me, the folders are created again.

A bug of some kind perhaps.

R.Neil Haugen

[grendizerus]

It's not Onedrive's fault, it's Adobe's.

[N22742848z7x7]

I can't believe this has not yet been resolved. It would take a dev literally minutes to step through this and catch any bad code that tries to stitch an AppData folder to a random folder.

I'm on a Win box and in my instance, it was creating a "LUTs" directory and its corresponding subfolders:

F:\AppData\Roaming\Adobe\Common\.LUTs\Input
F:\AppData\Roaming\Adobe\Common\.LUTs\Output

My suggestion is to create a symbolic link to the folder it's trying to write to and have it linked to the ACTUAL location it's supposed to write to.

1. Delete the Adobe folder only so that the only rogue directory that stands is: X:\AppData\Roaming\ where X == your drive or the path in which it's not supposed to be. This directory should be empty since you deleted the Adobe folder and its subdirs

2. Open a command terminal with Admin rights and go to that same folder: X:\AppData\Roaming

3. Now you want to create an "Adobe" directory and make that symbolic link to the legitimate "Adobe" directory that's in your user profile's AppData dir:

mklink /d "[X]:\AppData\Roaming\Adobe" "C:\Users\[YourUserName]\AppData\Roaming\Adobe"

Ensure you replace X with the incorrect drive or path and replace [YourUserName] with your username and then execute the command

4. Type the "DIR" command to see the changes and you'll notice that a new "Adobe" folder has been created, it's a symbolic link, and you'll see the target pointing to the legitimate location of AppData\Roaming\Adobe

5. Launch Premiere Pro or Media Encoder or the offending Adobe application and you'll notice that it'll dump the LUTs folder in the correct place now (assuming it's not already there)

6. In Windows Explorer, right click on the [X]:\AppData folder and go to properties and set the folder to Hidden so it's ugliness is not in your face

You should be good to go.

[grendizerus]

Thanks NA for your help, but symbolic links do not work with synchronized folders such as Onedrive... Adobe must FIX this!

[Paul_Cybulska]

It's such an annoying bug. I hope they fix it soon!

[bradleya68856429]

Having the same issue with Premiere re-making the folder in my onedrive instead of my actual AppData folder.

[Lukas_5]

The problem is still occurring.
For me, it's After Effects combined with OneDrive.

[skillful_cause16B6]

Facing same problem, Adobe puts AppData\Roaming\Adobe\Common\LUTs path under Documents path instead of %userprofile% path, easy to fix but Adobe f*cks for their customers.

[Yamagata]

Can't believe that already 2 years have passed and still continue with this error
Is this how they care for their customers?

[ti99597247]

This would be such a fast fix and would help so many people who use One Drive and Dropbox for backing up of essential data. @Adobe, please have someone look into this!

[macgnarley]

Hi Id love to know your workaround. I think the poster above finally answered why this happens- i too have moved my documents folder away from its original location. /No idea why that means premiere must put Appdata on my desktop, but its happened for years. Your link does not go anywhere specific - do you have a link to your actual work around? Thank you!

[macgnarley]

Actually, I realized I could click your name and see the posts. Found it, will try it tomorrow. You're a champ, Adobe should hire you. I literally started having this problem in 2019 with a prior laptop.

[macgnarley]

This has been happening to me for years, because I do not store my documents folder in the standard directory. It is terribly annoying and has been reported dozens of times over the years. Adobe ought to have fixed this years ago.

[skillful_cause16B6]

The Adobe UserVoice is no longer accessible, could you please share your workaround to us?

Thanks and regards

[damien.benoit@gmail.com]

Jeez, has noone figured out how to fix this? I havent found any setting telling my D drive to save whatever data. and Yes, i have always moved my documents and everything else like pictures, music, video , and such to a D drive "Docs drive" and that for one makes it easier to deal with every having to reformat and install i can get back to 100% from 0% pretty much in 4 days of working none stop so thats why i do that and I see that adobe AFTER EFFECTS for me is making folders where it wants, and thats following my documents like a little buddy. It has also created that folder once when i was using media encoder.

[litework]

Adobe... fix this yesterday. Actually crazy this problem still exists.

[fixthebug]

Same problem here...

[francisc75144729]

I only have C:drive on my laptop.  I use Microsoft's One Drive and have nothing in Adobe cloud and would not expect to use it.  I have paid for and use Acrobat Pro and Photoshop Elements - nothing else although some things I have never heard of let alone use seem to get added with Acrobat Pro.  Every time I open my laptop I get AppData/Roaming/Adobe/Common/LUTs/Input and Output.  Both input and output are nothing but empty.
In other words I have a set of folders on my laptop I don't want, have not asked for, do not use and seem to serve no purpose.  If I delete them it seems to have no effect whatsoever - positive or negative - but next time I boot up, back they come.  Anyone have the least idea what this is and how I can stop it please?

[R Neil Haugen]

I have no clue about your "trouble" with those folders. Like any app, Premiere Pro has a number of folders it sets up for various uses, and scans them on launch to see if something is there. Those folders are for users that choose to add LUTs to the program on their own.

So ... yes, it expects those folders to be there, it will create them at need as they are part of the main operations of the app, and if you don't use them they take no space whatsoever.

[KnowledgeIndia]

Hi, 

I was facing the same issue. I did the following: 

1.  Navigate to "Edit > Preferences > Media Cache". In this, you can specify custom folder locations for "Media Cache Files" and Media Cache Databases". I created 2 folders in D drive and specified those.  
2.  On creating a new project, specify the project location to be a folder in D drive (or wherever you like). 

After doing this, closed the Premiere Pro and started again. Though I had deleted the "AppData" folder from OneDrive, it got created again on the start of Premiere Pro, but it does not save any files in that. Just the folder structure gets created, so you need not worry much about it. 

All the files are actually getting stored in the folders I specified from the D drive.

If it helps you, please UPVOTE and let others know. 

Thank you.

[Pixel_Cube]

I just moved the "Images" and "Documents" folders to drive D, but every time I start Pr, Ae, or Me, they create an appdata folder containing LUTs in the root directory of drive D, which is very annoying.

[Pixel_Cube]

To be precise, I am moving the folders for "Pictures", and "Documents" ("Images" is a text error on my part)

[ORothe]

I came here, because I have exactly the same problem... but in my case, the files are somehow created by some background processes set up by Photoshop Elements 2024. 

[Kevin-Monahan]

Hello @R Neil Haugen and others on the thread,

Thanks for filing the bug report. I merged a few different reports to this one, which received the most upvotes. The traffic stats and upvotes did not carry over, so please upvote if you have not already done so. Our team should consider that statistic when considering the status of this bug.

Unfortunately, this report lacks input from the product team, and I apologize. I will update the bug's status to raise the severity of the bug and see if there's a way to get this bug some more internal traction.

I am so sorry for this issue. It's gone on for far too long.

Cheers,
Kevin