Skip to main content
R Neil Haugen
Legend
April 12, 2020

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

  • April 12, 2020
  • 44 replies
  • 7564 views
A number of users on the U2U forums are having issues with Premiere or MediaEncoder creating a folder tree on their 😧 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

44 replies

Participant
April 2, 2025

Same problem with Adobe Premiere Elements 2024 here.
Has Adobe really not managed to fix the problem in four years?

skillful_cause16B6
Inspiring
March 8, 2025

it wasnt fixed.

Participant
March 8, 2025

Thank you. Exactly, the cause of the error has precisely nothing to do with whether you use any kind of cloud drive or internal or external hardware drives.

 

The reason for the error is simply that Premiere does not mount the LUTs folder and its subfolders correctly in the AppData directory path and thus incorrectly creates a second AppData folder in the wrong place.

 

AppData is a hidden Windows system folder and is created exclusively by the operating system for each user account on the respective computer.
For every Windows computer on the planet, it is ALWAYS under: “[SystemDrive]:\Users\[Username]\AppData”
All applications store their (user) specific application data under this system directory. This is also how Adobe applications do it, including Premiere, which have created hundreds of directories with their data there.

 

Only the LUTs folder is created incorrectly because it is obviously not created in the code with “%appdata%\Adobe\Common\LUTs\...”, but is placed “manually” under the same directory in which the respective user currently has their Documents folder - and today this can be anywhere.

Over 10 years ago, the Documents folder was still in the same directory as AppData by default. But it hasn't been for a long time now.

 

It's about time that this simple bug, which can be corrected in a matter of minutes, was finally fixed.

Ann Bens
Community Expert
Community Expert
March 4, 2025

Seeing the same thing. AppData in Documents and my Documents is on the D drive.

Dont use any OneDrive or simular.

Beta 25.3

Participant
March 3, 2025

Thanks for your answer.

 

I can definitely rule out that the problem lies with One Drive - this time it's not MS's fault.

The path is demonstrably created anew every time Premiere Pro is started, and it is simply incorrect.

 

Best regards

R Neil Haugen
Legend
March 3, 2025

OneDrive might be the problem there ... it is incredibly tough on getting to stop doing something ... I had to completely remove all traces of it at one point as it insisted on 1) setting up all User folders in it's own system and moving anything created outside it's own system within it and 2) refusing to allow Adobe apps write permissions.

 

So ... that would be something I would check.

Everyone's mileage always varies ...
Participant
March 3, 2025

It still does it: "C:\Users\username\OneDrive\AppData\Roaming\Adobe\Common\LUTs" recreated by Premiere Pro on every start-up for no reason nor purpose - just annoying.

This directory has no place in my OneDrive - it belongs to: "C:\Users\username\AppData\Roaming\Adobe\Common\LUTs".

 

Adobe, this path has been created incorrectly since January 2023 - please finally correct this easy-to-fix error.

 

Thanks and best regards

R Neil Haugen
Legend
February 13, 2025

Deni,

 

Do you have Dropbox, OneDrive, WeTransfer, or any other such sync/cloud service in operation?

Everyone's mileage always varies ...
Participating Frequently
February 13, 2025

Same problem here, can't believe it keeps happening

Kevin-Monahan
Community Manager
Community Manager
August 2, 2024

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

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio